QuickBooks Data Damaged Error

QuickBooks data damaged error is a common occurrence that is usually encountered when formatting one or more pages becomes damaged, or when there are performance difficulties, disc failures, power surges, and so on. One of the most common problems you may encounter is a damaged QuickBooks company file. In simple terms, Data Damage means your company file can’t be read correctly by QuickBooks. This can be caused by internal (within QuickBooks) or external (file location) factors.

Majority of data damage issues including LVL errors in the QBWin.log can be repaired within QuickBooks. In this post, we’ll learn more about Common QuickBooks Data Damaged Errors and how to fix them, as well as the possible factors that cause it. Let us now buckle up and explore more about repairing the QB company file data damaged issues.

Different types of data damage in QuickBooks 

• List Damage- lists (Chart of accounts, items, customers, vendors, employees, etc.).
• Transaction Damage- One or more transactions have been damaged.
• Link Damage- It refers to the damage caused by linkages between transactions or by the transactions themselves.
• It’s worth noting that determining the extent of this type of damage might be difficult. It’s possible that you’ll need to open the transaction to figure out where the problem is. A damaged link could potentially be the reason for mismatched reports.
• Structural Damage- Table/s or the table’s header have structural damage.

What triggers the data damage error in QuickBooks

There are certain causes that may result in data loss or damage in the QB company file. The below highlighted are few of the most prevalent factors that could lead to common QuickBooks Data Damaged Errors:

• If the database is kept on a hard drive that has been infected with a virus, an error like this is likely to occur.
• If the size of the data file has exceeded the set limit.
• If there is a rapid power surge or drop, the entire hard drive could be destroyed, resulting in common QuickBooks data damaged errors.
• Furthermore, if the system is missing certain resources such as RAM, virtual memory, network interface cards, routers, network cables, and so on.
• A system shutdown that isn’t done properly could also cause problems.

How to identify Common QuickBooks Data Damaged Errors

Once you’ve gone over the indicators below, identifying the data damage problem in a QuickBooks company file becomes simple.

Let’s have a look at them one by one:

• Errors in the verify data utility or verify target: minor values do not match major on the screen or in the Qbwin.log file, such as “A data error stops QuickBooks from proceeding”
• If the transaction history shows a negative balance
• In addition, if any transactions or entries are missing from the lists
• In the event that paid bills or invoices appear to be unpaid
• If the software is sluggish to begin with
• Balance sheets that are incorrect
• If the software unexpectedly shuts down while attempting to save or remove a transaction
• You notice the HTML code in the window when you open “submit feedback online” and move to the Bug report window
• In this situation, an asterisk (*) precedes the account name. This suggests that these accounts were generated by software because the original accounts were missing,
• And so on. 

Preventative measures

Before diving into the quick remedies for data damaged in QuickBooks company files, users should have a look at some preventative actions.

The following are some of the preventative measures:

• Using QuickBooks to create a backup:
  QuickBooks frequently backs up the files automatically, which is quite helpful. However, when the log file grows in size, speed suffers, and the risk of data damage rises unless the data is backed up. Intuit will then utilise this backup file to retrieve your data. As a result, it’s a good idea to perform a monthly backup of your QuickBooks accounting software.
• Choosing a wired network over a wireless network:
  This is recommended since using a wireless network increases the possibility of dropped connections, which can lead to problems with the data file. By choosing a hard-wired network, you can prevent these problems.
• Make sure to verify the size of the file:
  The 250 MB file is available to QuickBooks pro and premium users. When a file grows to 500 MB in size, however, performance may suffer. QuickBooks corporate users, on the other hand, have the option of upgrading to 500 MB. However, if the file grows to 750MB in size, it may cause problems. As a result, it is advised that the file be kept under the specified size limit to avoid any problems. You can also compress the file to make it smaller.
• Size of the monitoring list:
  In QuickBooks pro and premier, you’ll have to keep an eye on the list limits. The most crucial thing to remember is that if you exceed the top limit, there will be no warning signs. Furthermore, the items on the inactive list are not included in this list.
• Patches to be updated:
  The release number can be found in the first line of the product information window. Using the most recent patch may not cause such a problem in the future.
• Monitoring database file fragments on a monthly basis:
  If the system becomes overburdened with data over time, fragmentation may occur. Also, if you are putting the data in without cleaning it up beforehand. In order to function properly, you must maintain the number below 10,100.

List of Common QuickBooks Data Damaged Errors

Well, when you experience data-damaged issues in your QuickBooks software, then the first step is to find out the actual reasons or you can also identify through signs and symptoms which are discussed in the above section. Next step is to attempt preventative measures as your instant remedy in order to avoid common QuickBooks Data Damaged Errors.

Let’s check out quick list of Common QuickBooks Data Damaged Errors: 

#1. Error -6000, -301: An error occurred when QuickBooks tried to access the company file

The problem occurs when a user tries to open a QuickBooks company file with the extension (.qbw), and the primary error is a lack of disc space. This issue appears on your screen,

Warning: An error occurred when QuickBooks Desktop tried to access the company file. Please try again. If the issue pertains, contact the Intuit Technical Support & endow them with the following QB error codes: (-6000,-301).

This makes QuickBooks difficult to manage and use. One of the most apparent reasons behind this error occurrence is one or more of the QuickBooks desktop files getting damaged.

Here are the easy steps to remove Error -6000, -301,

Step 1: Repairing your QB Desktop 

• Open the “Control Panel” panel => click on the “Programs” tab => click on the “Programs and Features” tab from the “Start” or “Windows” menu
• Select QuickBooks and then click the “Uninstall” button
• When the QuickBooks installation window displays, click the “Next” tab
• Next to the “Repair” icon, select the “radio” button. Then select the “Next” tab, followed by the “Repair” tab
• Select “Finish” from the drop-down menu.

Step 2: Renaming the QuickBooks .ND files 

• The company file is opened by opening the folder that contains it
• Simply save the file(s) with the same name as QuickBooks but the extensions .tlg, .nd, and/or.dsu
• Select Rename from the right-click menu for each file
• To each of them, you have to add the word called “old”
• This prevents the use of a default database by rebuilding your company’s data files.

You can also make use of the QuickBooks File Doctor in order to remove such QuickBooks Data Damaged Errors. 

#2. QuickBooks Error -6150, -1006

QuickBooks error -6150, -1006 is one of the commonly encountered errors that could be seen when the user finds that users are unable to open the company file. It happens when there is a damaged or corrupted company file or system infected with CryptoWall virus can also end up with this type of error. The following error messages may appear on your desktop screen when error code -6150, -1006 occurs:

An error occurred when QuickBooks tried to create, open, or use the company file. Please try again.

Or 

If the problem persists, contact Intuit Technical Support and provide them with the following error codes: (-6150 and -1006).

Or

We are sorry. QuickBooks couldn’t open your company file. We’ll try to fix the problem. Click start to begin. If the problem continues, contact support for assistance and report error code: (-6150, -1006).

Follow the steps to fix the error with ease

Step 1: Check for CryptoWall

The CryptoWall virus and other malicious software might occasionally produce Error -6150, -1006 and prohibit you from accessing QuickBooks. Perform the following quick check before move to the next step:

• Launch the Start Menu in Windows
• Launch File Explorer by typing “File Explorer” into the search box
• Open the QuickBooks folder by searching for it and it is usually on your C: drive
• Look for words like “decrypt” or “instructions” in the files you’re looking for (.txt or .html)

If you don’t see any files that fit this description, your computer is fine then move on to Step 2. If you come across files that match this description, contact your anti-virus provider for assistance in eliminating the CryptoWall virus. Don’t move on to the next step until you’ve resolved this.

Step 2: Restore a backup of the Company file 

By restoring the company file backup, the user will be able to fix QuickBooks Error -6150, -1006.

It’s worth noting that once a user converts a company file to a later version of QB, he or she won’t be able to open it in an earlier version. If a user wants to utilise an earlier version of QuickBooks, he or she must restore a backup file produced with that version.

Steps to be performed to restore the company file:

• Go to the QuickBooks File menu and select Open or Restore Company
• Pick “Open or Restore a Backup Copy” followed by hitting “Next”
• Select Local Backup and Next from the drop-down menu
• After that, select the backup file’s location from the drop-down menu
• Once done with that, you have to select the backup file
• Here, you’ll need to select Open and then “Next”
• Now, the user must choose the location where the file should be restored from the save in drop-down menu
• In the file name section, type a new file name, and then in the save as type field, select QuickBooks files (*.QBW)
• QuickBooks files (*.QBW) should be populated by the as type field
• When you get close to the conclusion, hit Save and respond to all of the prompts that appear before the restoration begins
• Finally, click Save, then read and reply to any messages that appear before the restoration process begins.

If the error code -6150, -1006 persists, the user can try to recover the lost data using QuickBooks Auto Data Recovery, or create a QB Desktop company file, etc.

#3. Error: QBWin.log: LVL_SEVERE_ERROR–GetDecryptedCreditCardNumber The decryption has failed

The error happens when the Verify Data Utility fails due to damage in the encryption of sensitive fields such as credit card numbers, social security or Social Security, and bank accounts. When the error occurs, it gives you the following error messages:

LVL_SEVERE_ERROR–GetDecryptedCreditCardNumber Failed: The decryption has failed. CHECKPOINT: Failed to decrypt customer’s credit card number. Customer ID: nnnn

Or

LVL_ERROR–Unable to decrypt social security number/Social Security number

To overcome the error, perform the below suggested troubleshooting methods

Method 1: Verify the QuickBooks Admin user for damage 

• As the Admin, log in to your company’s file
• Admin password should be changed
• The data in your file will be re-encrypted by QuickBooks (Please keep in mind that this could take several minutes)
• Sign out of your company’s file and then close QuickBooks by going to the File menu then selecting Close Company or Logoff
• To finish the re-encryption procedure, reopen QuickBooks and sign in as the administrator.

Check to see if the re-encryption worked

• Use the Verify Data Utility to check your data
• Examine the log file’s most recent entry
• If any of the following error messages appears on your screen
  • LVL_SEVERE_ERROR–GetMasterKey Failed: The decryption has failed.
  • LVL_SEVERE_ERROR–GetDataAccessKey Failed: The decryption has failed.

Then you’re supposed to send your file to Intuit’s Data Services to repair it. If not, move to the next method.

Important Note: If the Admin user receives the Masterkey error, only send your file to Data Services. If the problem just affects non-admin users, you'll need to delete and recreate them.

Method 2: Repair the damaged encrypted fields 

Step 1: Run the Verify Data Utility

Using the Verify Data Utility, you can check for any possible data damage:

• Select Rebuild Data from the File menu, then hover over Utilities
• Select “Ok” on the QuickBooks Information window
• To save a backup, follow the onscreen instructions
• Allow the program to repair your file (It might take a while)
• QuickBooks may appear to be frozen, but it is still functional as long as you can move your mouse
• Select “Ok” when the tool is finished
• Select File from the File menu and then pick Verify Data from the Utilities menu
• Allow the tool to do a data check on your file
• Select “Ok” if QuickBooks does not detect any issues
• You may continue to use your company file (You haven’t suffered any data loss)
• Select Rebuild Now if QuickBooks detects a problem with your company file. 

Step 2: Locate the error message in QBWin.log 

• To determine what is affected, look at the error message in QBWin.log
• Locate the QBWin.log file and store it to a convenient area, such as your desktop
• Select the QBWin.log file with the right-click menu
• Choose Notepad as your Open with option
• In the QBWin.log, take note of the Customer names and IDs.

Step 3: Edit the credit card number of affected user

• Choose the Customer Center from the Customers menu
• Select All Customers from the small arrow symbol above the search bar
• Look up the names of the Customers or Jobs you wrote down
• To edit a Customer or Job, double-click it, then go to the Payment Settings tab
• Select OK after entering a 16-digit dummy credit card number and expiration date
• Go back to the Payments Settings tab
• Select OK after entering the right credit card number and expiration date.

Step 4: Finally, verify if data no longer has errors 

• Restart the Verify Data utility. This will indicate whether or not the problem has been resolved.
• If no problems are found, the issue is resolved.
• If the Verification fails, look for any issues in the QBwin.log that caused the verification to fail. If Customers continue to appear, repeat Step 3.

#4. QBWin.log: Verify list. Duplicate name encountered

If two or more names in your lists are identical, you’ll get the duplicate name error. This problem can occur when importing lists or transactions into QuickBooks from a different company file, Excel, or other integrated or third-party software. The Duplicate name problem will also appear after you Rebuild and Verify or you can look for it in the QBWIN.LOG file. Rebuilding of QuickBooks can assist you in resolving the damaged list elements, however if the error still remains after rebuild, find and edit the duplicate names.

The steps are as follows:

Step 1: Find the duplicate names

• To discover duplicates, use the QBWin.log file.
  • Locate the files QBWin.log and QuickBooks.log
  • To go to the bottom of the file, press the Ctrl + End keys together from your keyboard
  • To open the Find window, press the Ctrl + F and search the log for the word “duplicate”
  • Find the name, account, customer message, and other information mentioned in the error notification.
• To discover duplicate names, use the Primary Name List.
  • Select Write Checks from the Banking menu
  • To open the Primary Name List, select in the Pay to the Order of field followed by pressing the Ctrl + L keys together from your keyboard
  • To see both active and inactive names, tick the Include inactive checkbox
  • To alphabetize the names, select the Name heading, regardless of type
  • Look for names that are spelled the same way.
• To find accounts, items, templates, and other items, use your standard lists.
• Select the Lists menu, then the relevant list from the drop-down menu
• List of Memorized Reports: Select Reports >>> Memorized Reports >>> Memorized Report List from the drop-down menu
• To order the names alphabetically, click the Name heading
• Look for names that are spelled the same way

Step 2: Change the spelling of one of the duplicate names

• Make a change to one of the names:
  • Open the list where the name appears (For example, a customer list or a vendor list)
  • To edit a name in the list, double-click it
  • To distinguish it from its clone, change at least one character in the name
  • Click the Ok button
• Step 1 should be repeated for all duplicate names in the QBWin.log
• To be sure there are no more duplicate names, use the Verify Data Utility.

Decide whether you need to keep the updated names isolated once you’ve modified the duplicates. You can try to delete them if they don’t have any transactions attached to them. You’ll have to merge the names if you don’t want to do that.

#5. QBWin.log: LVL_ERROR–Error: Verify item history target quantity on order mismatch error

When the ItemHistUpdateEngine fails to update item information, a mismatch between your item history and some items on orders can occur. While backing up your file, you’ll get the message A data problem stops QuickBooks from continuing, and your QBWin.log will indicate the following error:

LVL_ERROR–Error: Verify item history Target quantity on order mismatch error

The issue can be resolved simply by rebuilding the company file; however it may be required to change the items listed in the log.

Solution 1: Rebuild and Verify 

Step 1: Rebuild data 

• Select Utilities >> Rebuild Data from the File menu
• Select Ok when prompted to back up the file
• When the message Rebuild has finished appears, select Ok.

Step 2: Verify data 

• Select Utilities >> Verify Data from the File menu
• Select “Ok” when QuickBooks reports that there are no problems with your data then you can now use the file as usual
• If QuickBooks still detects an issue after checking, proceed to the next solution.

Solution 2: Edit the transaction shown in QBWIN.log manually 

1. Open the QBWin.log file 

• Press F2 to open the Product Information window while QuickBooks is open
• To launch the Tech Help window, press F3 and then select the Open File tab
• Look for QBWIN.log on the Open File menu, then select Open.

2. Using the QBWin.log, locate the damaged item(s)

• To launch the Find window, press Ctrl + F after opening the QBWin.log
• Press Enter once you’ve typed the error
• Make a note of the order, item, and quantity specified.

3. Recreate the damaged item.

• Go back to QuickBooks and open the order that was stated in the log
• Select Save & Close after deleting the item (not the full order) shown in the log
• Return to the order and re-enter the deleted item’s quantity and description
• Click on the “Save & Close” button

4. Re-verify your file.

#6. QBWin.log: Orphan payee found in Online cache

QBWin.log: Orphan payee found in online cache error message appears frequently when QuickBooks closes unexpectedly due to an error, power outage, or surge, or even server failure. Backing up data on a regular basis can be a great help when dealing with this problem because it simplifies the process. 

Apart from that, Intuit suggests you to perform basic data damage troubleshooting before you perform the solutions as discussed below:

Solution 1: Make sure your Online Payee’s must be in sync

• If a previously used payee for online payment has been changed, undo the changes and create a new payee with the updated information. For example, editing an online payee frequently generates a new payee identity on the bank’s system can no longer link to the former payee, resulting in an orphan payee.
  • Intuit recommends not editing or updating any payee previously used for online payment to avoid difficulties with online payees (name, address, account numbers, etc.).
  • Create a new payee (with a slightly different name) and deactivate the previous one, according to Intuit.
• Rebuild the data file if necessary.

Solution 2: If you don’t already use “QuickBooks Bill Pay New!” to pay bills online, you should start now.

1. Deactivate any online banking accounts you may have

• Select the Chart of Accounts option from QuickBooks’ Lists menu
• Select Edit Account from the drop-down menu when you right-click the account you’re using for online banking
• Select Bank Feed Settings from the drop-down menu
• Choose the option to turn off all online services
• After that, press Ok
• Finally, run the Rebuild Data Utility. 

2. Reactivate the account if it has been inactive for an extended period of time.

• Go back to the Chart of Accounts and select Edit Account from the drop-down menu
• Once again, set up your online banking by clicking Set Up Bank Feeds
• Run the Verify Data program to double-check that the problem has been resolved.

Solution 3:  If you’re having trouble with “QuickBooks Bill Pay New!” in QuickBooks, or if the remedy above doesn’t work.

Important Note: Repeat this process for all orphaned payees in the QBWin.log

1. Using the Write Checks screen, try re-associating your online payees

• Select Write Checks from the Banking menu
• From the PAY TO THE ORDER OF drop down, choose the Payee’s name
• To designate this check as an online payment, click the Pay Online box
• Clear the screen by clicking the button

2. Use the Rebuild Data Utility to rebuild your data
3. Re-verify your file, and then look for errors in the QBWin.log.

#7. QBWin.log: LVL_ERROR – Error: Verify Item History: Build txn target bad pending state. Item = nnnnn

It is also a data damage issue of QB while backing up your company file. This data damage issue prevents QuickBooks from continuing. One or both of the following error messages may also show in your QBWin.log after verifying data:

LVL_ERROR–Error: Verify Item History: Build txn target bad pending state. Item = nnnnn

Or

LVL_ERROR–DB error -185 ErrorMessage:’SELECT returns more than one row’ from file:’.\.\src\DMEDLSQLContactEditElement.cpp’ at line 2679 from function:’DMEDLContactEditElement:LoadAdditional.

Important Note: Before you begin troubleshooting, make sure your QuickBooks Desktop is up to date.

The issue should be resolved after rebuilding the company file, however manual modification of the items listed in the log may still be required.

Try the below troubleshooting to sort the error out with ease

Method 1: Rebuild and Verify 

Rebuild data 

• Go to the File >>> Utilities >>> Rebuild Data to accomplish this
• Click “Ok” when prompted to save a backup of the file
• Click “Ok” to continue to the next step after the message Rebuild has completed display on your screen

Verify data 

• Verify Data can be found under File >>> Utilities
• Click Ok when QuickBooks says there’s no problem with your data
• The file can now be used again
• If QuickBooks still detects an issue after verification, proceed to the next step.

Method 2: Identify and edit the damaged item manually 

Step 1: Identify the item number using the QBWin.log 

• Press F2 to bring up the Product Information window while QuickBooks is open
• To launch the Tech Help window, press the F3 key followed by selecting the Open File tab
• Look for the QBWin.log under the Open File tab and then click “Open”
• Press CTRL + F keys together from your keyboard to bring up the Find window and look for the error once QBWin.log is open
• Take note of the error message’s item number.

Step 2: Export your item list and identify the damaged item 

• To export a list to IIF files, go to File >> Utilities >> Export >> Lists to IIF Files >> Item List
• Select a preferred location and save your changes
• Do a right-click on the file once it has been saved and select Open with Excel from the drop-down menu
• (Alternatively, you can open Excel and drag the file into the spreadsheet)
• Note the REFNUM, which corresponds to the item number in the error notification. 

Step 3: Correct the item’s quantity on hand (QOH)

• Select Inventory Valuation Detail from the Reports menu, under Inventory tab
• Choose All as your date range
• Find the item and the date when the quantity became negative for the first time
• You have the option of deleting the “build assembly” that is associated with the negative on hand OR, you can delete the “build assembly” that is associated with the negative on hand
• To raise the quantity of an item, you can conduct an Inventory Adjustment.

Step 4: Verify the file once again

To confirm that the data issue is fixed, make sure your verify the company file once again by

• Moving to the File menu >> Utilities >> Verify Data 
• Your file is ready to be backed up if the Verify Utility gives the message “QuickBooks found no errors.”
• Continue with method 2 if the Verify Utility provides the message “A data problem prevents QuickBooks from continuing”.

#8. QBWin.log: LVL_ERROR — Error: Verify Online Account Information: Invalid Customer ID number

It is caused by an invalid Customer ID for an account set up with online services such as Bank Feeds. Intuit suggested to troubleshoot QuickBooks Online services if rebuilding or verifying data process does not complete successfully and the QBWIN.log gives you an error message stating:

LVL_ERROR–Error: Verify Online Account Information: Invalid Customer ID number–> Record = XXX.

Two possible ways to get rid of the QBWin.log: LVL_ERROR — Error

Way 01: In the Chart of Accounts, correct the Customer IDs on accounts set up for online services (applies to US only).

• Select Company >>> Chart of Accounts from the drop-down menu
• Select Edit Account from the context menu of the affected online-enabled bank account

Note: A highlighted lightning bolt in your Chart of Accounts indicates accounts that are online-enabled

• Select the Bank Feed Settings option from the drop-down menu
• Select Save & Close after correcting the Customer ID
• Run the same data utility again to confirm that the changes to the customer IDs have allowed the procedure to finish.

Way 02: Reconnect to your banking institution after verifying the online bank details in QuickBooks.

• Select the Chart of Accounts from the Lists menu
• Select Edit Account from the right-click menu of the account that was being used when the issue occurred
• Check the information in the Customer ID section in Bank Feed Settings to make sure it matches the customer ID provided in the online account access documents you received from your financial institution
• If required, make changes to the number before clicking Save & Close
• Please keep in mind that
  • This issue can be caused by an additional or misplaced dash, period, or other character in the ID field.
  • It’s possible that the ID you’re using is accurate, but the PIN you’re using is incorrect or formatted incorrectly.
  • Both the customer ID and PIN fields can have alpha and numeric characters, depending on the banking institution. They could be case-sensitive, so try other customer IDs and PINs with upper and lower case letters.
  • When you achieve a certain number of failed login attempts in a certain amount of time, certain financial institutions lock your account. When logging in for Bank Feeds if you’re locked out, you can see the error OL-334. To have your PIN reset, you may need to contact your financial institution.
• To retry the connection, go back to your Bank Feeds Centre and click Send Items.

#9. QBWin.log: LVL_ERROR-error: Verify Account List Item ###: View out of sequence

Users receive an error message says “LVL_ERROR-error: Verify Account List Item ###: View out of sequence. Verify Account List Item XXXX: Invalid sublevel X, valid range is X to X” if the Verify Data Utility fails to complete the process. It is usually caused due to damage in the Chart of Accounts that creates certain accounts issues to appear in an incorrect sequence. However, you can fix it by rebuilding and verifying your file, the steps should be the same as discussed in the above error section. If it doesn’t work out then you can try to 

Re-sort the List 

• Select Chart of Accounts from the Lists menu
• Choose Re-sort List from the Account drop-down menu on the bottom-left
• Select “Yes” when the prompt comes
• This will re-sort the original order of your accounts
• Check to see that all of the major account types are properly organised (i.e., all the income accounts are listed consecutively, etc)
• Proceed to the next step to manually adjust the accounts if the account types are not correctly grouped (for example, Other Current Asset appears as a subaccount of an Income account) or if subaccounts appear as main accounts.

Or manually fix the damaged accounts 

• To fix the accounts, right-click the account name and select Edit Account from the drop-down menu
• To convert a subaccount to a main account or to convert a main account to a subaccount, make sure the Subaccount checkbox should be marked
• If the Subaccount box is checked, select the relevant account type from the drop-down next to the checkbox followed by hitting the “Ok” button
• Steps 1 through 3 should be repeated for each account that is affected
• To check that the damage has been repaired, rebuild and verify your data once more. 

#10. QBWin.log: LVL_Error–Error: Verify Item: Invalid tax agency

The Verify Data Utility detects “QBWin.log: LVL_Error–Error: Verify Item: Invalid tax agency”, if your Item List contains damaged items, and the Tax Agency field for one or more non-sales tax products contains incorrect information. It also possibly occurs in the Preferred Vendor section of damaged items, non-vendor names, such as customer names, appear.

Troubleshooting tips to avoid the QBWin.log: LVL_Error–Error: Verify Item: Invalid tax agency

Remove the invalid information from each of the damaged entries in the QBWin.log file. Other sorts of things are not accessible in the Tax Agency field, which is restricted for sales tax items. Changing the item in any way and then saving it, on the other hand, removes the invalid Tax Agency data. Moreover, you can also identify the damaged item using the QBWin.log and edit the damaged items as well. The steps to identify the damaged item using the QBWin.log will be the same as discussed in the method 2’s step 1 in the “QBWin.log: LVL_ERROR – Error: Verify Item History: Build txn target bad pending state. Item = nnnnn” error section.  

Steps should be performed to to edit the damaged items 

• Go back in QuickBooks, select Item List from the List menu
• Double-click the damaged items in the QBWin.log to edit them
• In the Preferred Vendor field, check the following:
• If the Preferred Vendor field is correct, or if the item does not have a Preferred Vendor field, update the item by adding or removing a character from the item name or description, followed by clicking Ok
• Remove or give the right name to the Preferred Vendor field if it is wrong, and then click “Ok”
• Optional: To modify the item, double-click it again and undo any changes you made to the name or description fields, then click Ok
• If none of the above methods work, you can try merging the item into a new one.

#11. QBWin.log: Verify Target: Invalid Open Balance

At times, data damage can also cause a transaction to reflect an incorrect open balance. This type of transaction damage is detected by the Verify Data program, which logs one of the following errors in the QBWIN.log file: 

Error: Verify Target: Invalid Open Balance.

Or

Error: Verify Item: Item history Item Quantity on Hand mismatch error.

To fix the error QBWin.log: Verify Target: Invalid Open Balance

You can remove this error message by rebuilding and verifying your company file, the procedure for the same is already discussed in the above article. In any case, this solution doesn’t work out, you can try 

Identifying and fixing the damaged transactions manually 

1. Using the QBWIN.log, get the item number

• To open the Product Information window when QuickBooks is open, use F2 or Ctrl + 1 keys
• To access the Tech Help window, press F3 or Ctrl + 2, then select the Open File tab
• Look for QBWIN.log under the Open File menu, then select “Open”
• Press Ctrl + F to bring up the Find window and look for the error once QBWIN.log is open
• Take note of the error’s specifics, such as the record number, transaction type, and date
• The whole error messages will display as follows:
  • Error: Verify Target: Invalid Open Balance. Rcrd = [XXXX] Type: [transaction type] txn # [XXXX] Date: [XX/XX/XXXX] Doc# [XXXX] Source Account: [AccountName]
  • Error: Verify Item: Item history Item Quantity on Hand mismatch error. Item ID [XXXXX] expected value: [XXXXX] found value: [XXXXX]

2. Manually repair a transaction that has been damaged 

• A damaged transaction link or a date 
  • Open the transaction from the QBWIN.log file
  • Change the transaction date by 20 years (from 1/6/2018 to 1/6/2038)
  • Click on the “Save & Close” button
• Transaction out of balance 
  • Open the transaction from the QBWIN.log file
  • Go to the bottom of the transaction’s items
  • Add whatever you want, then hit the “Save and Close” button
  • Remove the new item from the edited transaction by reopening it
  • At last, “save & Close” is the option to click.

Conclusion

By the end of this post, it is hoped that you’ll have a good understanding of how to overcome Common QuickBooks Data Damaged Errors. On the other hand, if the error keeps bothering you, it is recommended that you can consult our Team of Experts via Live Chat. Team is available 24/7 to assist you for any doubts or queries related to QuickBooks accounting software. Meanwhile, you can also visit our official website www.accountingerrors.co to explore more about accounting software and its related issues or resolutions.