11 Common QuickBooks Desktop Errors And How to Solve Them | TheSoftwareBlogs

QuickBooks is an industry-leading accounting software. Small business owners and professional accountants mostly use it. However, QuickBooks offers various products, and each of these products/plans fulfils the needs of particular industries. For large scale organizations, QuickBooks Online Plus is the best option. But individual contractors and freelancers don’t need those extra options. Here comes the QuickBooks Self Employed, which is the individual-centred business management software. No matter who you are or what business you do, there is a QuickBook plan for you. Today, we’ll look at the 11 most common errors faced by QuickBooks Desktop users. We will not only share these errors with you, but we will also provide solutions for them. These errors are mostly caused by wrong entries or broken setups caused by users or the internet. Here is the list of all the errors, followed by their solutions for the QuickBooks Desktop plan. Error -6000, -301: “An error occurred when QuickBooks tried to access the company file” The error -6000, -301 is caused by when the network or users damage QuickBooks Desktop Support Files. These files include the TLG(The Transaction Log), Company file, DSN(The Data Source Name), ND(The Network Descriptor) and Encryption software files. To solve this issue, follow the steps given below. The first steps for troubleshooting the -6000, -301 error is updating your QuickBooks Desktop to the latest version. Click here to download the latest QuickBooks Desktop version for your PC. Now, open Windows File Explorer, and go to the QuickBooks Desktop file directory. Now search for files with the tlg, .nd and/or .dsn extensions. Right-click on each of these files and rename them by adding “.OLD” in their name. Alternatively, you can opt for QuickBooks File Doctor to repair these files automatically. Error -6150, -1006 The error -6150, -1006 is caused by CryptoWall viruses or irregularities in the company file. In rare cases, you need a specialist to solve this issue; however, with a little knowledge and the right tools, you can fix this issue by yourself. The Error -6150, -1006 halts you from opening QuickBooks but don’t worry because the solution is straightforward. To check if you need external support from the QuickBooks tech support team, open your Windows>Start button>My Computer> Local Disk (C:), and search for decrypt” or “instructions” (.txt or .html). If you see these files, contact the QuickBooks tech support team or your antivirus provider to help you remove the CryptoWall viruses. In case you cannot find such files, move to the next step. Now, backup your current company file to a safe location(a folder you don’t usually use). If you have recently backed up your company file (QBB), use it to restore your company to that timeline. If you are not getting the -6150, -1006 error, it means your problem is solved, and you can make the new changes from the previously stored backup. In case you still see the error, use QuickBooks QuickBooks Auto Data Recovery software. Error: QBWin.log: LVL_SEVERE_ERROR--GetDecryptedCreditCardNumber The decryption has failed The LVL_SEVERE_ERROR can put your business on a halt, and it’s better to solve this issue as soon as possible. This error is mainly caused by encryption damage of private files like banking information, credit card numbers, or social security numbers. Below are the steps for fixing the “QBWin.log: LVL_SEVERE_ERROR--GetDecryptedCreditCardNumber The decryption has failed” error. Sign in as Administrator and change Admin password. Sign Out from your company file, and go to File>Close Company/Logoff>Close QuickBooks. Finally, open QuickBooks again and Sign In to your company file to start the re-encryption process. If this method doesn’t work, open the QuickBooks Verify Data utility. Alternatively, you can manually edit the damage parts by checking the error messages in the QBWin.log. If the error persists, contact QuickBooks’ tech support team. QBWin.log: Verify list. Duplicate name encountered The “QBWin.log: Verify list. Duplicate name encountered” error is caused when there are two or more identical names in your list. This error is pretty common, and it occurs when you are importing data from different company files or from a 3rd party Excel sheet. To solve this error, carefully follow the steps given below. Open your QuickBooks company file, and search for a duplicate name using Ctrl + F>Duplicate. Now, select entries with duplicate names and edit them by double-clicking on each cell. Make sure to add only one character to separate names from their counterparts duplicates. The rest of the data will stay the name. Finally, click OK to complete the procedure. QBWin.log: LVL_ERROR--Error: Verify item history target quantity on order mismatch error If the ItemHistUpdateEngine fails to update item history and order, you can face the QBWin.log: LVL_ERROR--Error: Verify item history target quantity on order mismatch error. A message with the text “A Data Problem Prevents QuickBooks from Continuing” will appear whenever you back up your files. To troubleshoot this error, follow the steps given below. Note: Before rebuilding your data, make sure you create a backup for your company files and other transactions files to avoid future inconveniences. Go to File>Utilities > Rebuild Data. When you see the prompt for backing up your data, select OK. Once you see the text that says “Rebuild has completed”, click OK and complete the process. QBWin.log: Orphan payee found in Online cache Suppose you are using two or more bank accounts with the same username. In that case, there is a possibility that some of the items received will accidentally include information from other accounts and files. Sorting out your information will reduce the chances of bigger clashes in the future. However, the QuickBooks Desktop doesn’t provide the ability to use the same bank account for multiple company files. If you want to use QuickBooks efficiently, it is better to add separate profiles/bank accounts for each company. To troubleshoot this error, make sure not to update the payee’s previous information. If payee information has changed recently, restore the previous version or create a new payee with new information. Try updating the payee information by creating a new account rather than deleting the former one. You can use one extra character to create a new payee for transactions. Suppose you don’t want to use this method. In that case, you can select accounts used for banking and deactivate them via Edit Account>Bank Feed Settings>Deactivate All Online Services>OK, and finally run the QuickBooks Rebuild Data Utility. Once you have completed the procedure, go to Chart of Accounts>Edit Account>Set Up Bank Feeds, and set up your online banking again. QBWin.log: LVL_ERROR - Error: Verify Item History: Build txn target bad pending state. Item = nnnnn Irregularities in the company file cause this error. Sometimes, after updating the transaction files, names, and other data records, you need to rebuild the company file again for the new settings to take place. However, only rebuilding the company file is not the only thing you can do to solve this issue. Manual editing items in the log is still necessary for properly troubleshooting the “QBWin.log: LVL_ERROR - Error: Verify Item History: Build txn target bad pending state. Item = nnnnn” error. Follow the steps given below for rebuilding and verify data for making changes to the company files. Go to File, and click on Utilities followed by Rebuild Data. Back up the File and click OK. Now, if you see the message “Rebuild has completed”, click on OK and carry on with the verification part. From your dashboard, go to File>Utilities>Verify Data. Finally, click on OK after seeing the message “QuickBooks detected no problem with your data”. QBWin.log: LVL_ERROR -- Error: Verify Online Account Information: Invalid Customer ID number This is yet again the same error as the previous one. You can follow the same methods for troubleshooting the QBWin.log: LVL_ERROR -- Error: Verify Online Account Information: Invalid Customer ID number as you have used in the QBWin.log: LVL_ERROR - Error: Verify Item History: Build txn target bad pending state. Item = nnnnn error. If you face any other issues, you can visit QuickBooks official guides to get better clarification for these errors. QBWin.log: LVL_ERROR-error: Verify Account List Item ###: View out of sequence Whenever you see accounts in incorrect sequences, there is a possibility that the error occurs by damage to the Charts of Accounts. There are two ways you can solve this error; the first one is by rebuilding the File. The second is manually editing the accounts inside your main File. Follow the steps given below for both approaches. Rebuilding the File Open the File menu and go to Utilities>Rebuild Data. Back up the File from the prompt. Once you see the message “Rebuild has completed”, click OK and verify the data via Utilities > Verify Data. Manually editing Find the fault account and right-click>Edit Account. Go to Sub Account to revert it to the original File or vice-a-versa. When you see the ‘subaccount’ is marked, choose the account type from the drop-down menu. After making the appropriate changes to the File, rebuild and verify to complete the process. QBWin.log: LVL_Error--Error: Verify Item: Invalid tax agency This error is caused due to damaged items inside the Tax Agency Field. It also occurs when you have entered invalid data in your Tax Agency Fields. To solve this issue, verify each of the damaged items in the QBWin.log file and remove them. To solve the QBWin.log: LVL_Error--Error: Verify Item: Invalid tax agency error, follow the steps given below. Press F2 on the QuickBooks window, and open the product information page. Now, press F3 and open QuickBooks Tech Help window. On the Tech Help window, open the File tab. Now, Look for the QBWin.log and open it. In QBWin.log, open the find window with CTRL+F and search for errors. Now, find and note down the errors for each item name and proceed to the next step. Go to List Menu and select the Item List. Now, search for the damaged items and edit them accordingly. Finally, click OK and rebuild and verify again. Note: QuickBooks highly recommends not exporting, editing, and manipulating your data and item list to solve this error. If you need professional help from QuickBooks, contact the tech support team. QBWin.log: Verify Target: Invalid Open Balance This error occurs by a transaction that reflects an available balance as incorrect. As hard as it sounds, you can quickly fix this error by following the steps given below. First, follow the same steps to Rebuild and Verify Data inside the dashboard. If that doesn’t work, move towards the next step. Open the Tech Help window on the QuickBooks dashboard and go to the Open File tab. Now, search for QBWIN.log and open it. Now press CTRL+F to search for the error. Now, take notes of the errors indicated in the logs, like date and numbers. Now open the transaction you quoted from the QBWIN.log. Change the transaction date to 20 years into the future. Click Save & Close. Go to the bottom of transactions and add an item, then select Save & Close. Finally, reopen the new transaction and remove the added items following by Save & Close. Final thoughts These errors were not only limited to QuickBooks Desktop. A lot of QuickBooks products use the same architect designs and algorithms to manage data. However, these 11 errors occur by irregularities in data entered into the fields. You can make sure not to enter, alter, or delete data without the admin’s approval and keeping the data safe is the key for doing business in 2021. Most of these errors were easy fixes, and even if you face a problem out of your knowledge, you can always contact QuickBooks for a solution. You can get an on-demand training session for you and your employees. To sum up, QuickBooks is a fantastic program that caters to small businesses and large organizations, and there is hardly anything you cannot do with QuickBooks because it is a comprehensive solution for all your company management worries. Source: TheSoftwareBlogs