Error: QBwin.log: LVL_SEVERE_ERROR--GetDecryptedCreditCardNumber The decryption has failed

Error: QBwin.log: LVL_SEVERE_ERROR--GetDecryptedCreditCardNumber The decryption has failed



The Verify Data Utility fails and the Qbwin.log file displays the error:
  • LVL_SEVERE_ERROR--GetDecryptedCreditCardNumber Failed: The decryption has failed. CHECKPOINT: Failed to decrypt customer's credit card number. Customer ID: nnnn.

  • LVL_ERROR--Unable to decrypt social security number/social insurance number



This may be happening due to damage to the encryption of sensitive fields such as credit card numbers, social security/social insurance, and bank accounts.



Resolve GetDecryptedCreditCardNumber The decryption has failed error

Ensure that QuickBooks Desktop is up to date. It is also recommended to create a backup or a portable copy of your company file before you proceed with the following troubleshooting.

  1. Log in to your company file as the Admin user. If you do not have the Admin login, contact whoever the QuickBooks Admin is to have them log in.
  2. Go to the Users List:
    • QuickBooks Pro and Premier Desktop: Select the Company menu, Set Up Users and Passwords, and then Set Up User.
    • QuickBooks Enterprise Solutions: Select the Company menu > Users > Set Up Users and Roles.
  3. Select the Admin user (built in) and click Edit User.
  4. Change the password to a temporary password. For example, Intuit123.
  5. Click Next and then Finish.
  6. QuickBooks will re encrypt data in your file; this could take several minutes.
    • If QuickBooks crashes while encrypting, you will need to send your file to Data Services for recovery. Fees may apply.
    • If the encryption process completes (you may see a "working" window while the encryption process is working).
  7. This step is very important: Close out of the company file (File- Close Company/Log off), then close the program completely, then log back in as the Admin user. This will finish the re-encryption process.
  8. At this point, the Admin users encryption should be fixed, and you can log in with the new password you created in step 6 above. To be sure the encryption was fixed, you can check the QBWinlog as described below:
          Run the Verify Data Utility. See steps from: Resolve data damage issues (basic troubleshooting) (to verify if the encryption process completed successfully).
Look for anything in the recent entries of the Verify log (QBWin.log) such as:
  • LVL_SEVERE_ERROR--GetMasterKey Failed: The decryption has failed or
  • LVL_SEVERE_ERROR--GetDataAccessKey Failed: The decryption has failed.

(It worked): If you do not see any of these errors above for the admin user in the latest entries of the log (date/time stamp are after you performed the steps above), you can change your password back to what it was by repeating steps 3-8 above).

(It did not work): If the verify detects these errors in the latest entries (the date/time stamp are after you performed the steps above) of the log, you will need to send your file to Data Services for recovery (fees may apply). Only send your file to Data Services for repair if the Masterkey error is for your Admin user. If it is for a non-admin user (such as Frank-FrontOffice, Susan-Reporting, etc), you will need to delete those users and re-create them. Only the Admin user encryption is able to be sent to Data Services for repair.
Solution 2. Repair damaged encrypted fields

For QuickBooks 2014 and later, the Verify Data Utility records the errors and shows the Customers, Vendors, or Employees you need to repair. Please follow the steps in Error: QuickBooks found a problem with the Acct # / Card #/ Note field for other asset if you are in QuickBooks 2013 Desktop or later.

The following example is for damaged Customer Credit Card numbers. You will need to use similar procedures for damaged Vendor Tax ID's or damaged Employee SSN's

Repairing Customer Credit Card Encrypted Fields:

  1. Run the Verify Data Utility. See: Resolve data damage issues (basic troubleshooting).
  2. Find QBWIN.log files and save the Verify Log (QBWin.log) to your desktop. The log file displays the error messages and includes Customer Names.
  3. Open the Verify Log in a text editor such as Notepad.
  4. Open the Customer Center.
  5. Set the Center to show All Customers since corrupted records could be inactive.
  6. Find the Customer or Job in the Verify Log.
    If you don't see the name of the customer in the log file:
    1. Note the CustomerID number that appeared with the error in the QBWIN.LOG file, such as 4982.
    2. Select the File menu and select Utilities > Export > Lists to IIF Files.
    3. Select Customer List and click OK.
    4. Click the Save in drop-down arrow and select Desktop.
    5. Enter CustomerList.IIF in the File name field and click Save.
    6. Open the CustomerList.IIF file in Microsoft Excel or another text editor.
    7. Search the REFNUM column to find the number you noted in step 1 above and note the corresponding customer name in the NAME field.
    8. Close the CustomerList.IIF file.
    9. Repeat Steps 1 – 8 above for each customerID in the log file then proceed below to fix the customers.
      • Find the same Customer Name in Customer Center.
      • Double-click to open the Edit Customer or Edit Job window.
      • Click the Payment Info Tab.
      • Enter a 16 digit dummy credit card number, e.g., 1111222233334444 or 4444555566667777 and a new expiration date.
      • Click OK.
      • Reopen the Payment Info tab.
      • Enter the correct credit card number and expiration date for this customer and click OK.
      • Repeat Steps 6 through 13 for all customers listed in the Verify Data Log.
      • Run the Verify utility again.
      • If Verify returns QuickBooks detected no problems with your data, you are finished.
      • If Verify fails, check the Qbwin.log (see: Find QBWIN.log files) for customers that you missed or for other errors that are causing Verify to fail.

    • Related Articles

    • QuickBooks Error 3100

      QuickBooks software is one of the most sophisticated accounting software that has garnered popularity amongst bookkeepers and accountants all across the world. However, despite being so professionally sound and catering high level of businesses, the ...
    • QuickBooks Error 3371

      When we register or open QuickBooks, we see one of these error messages: Could not initialize license properties. Error 3371: QuickBooks could not load the license data. This may be caused by missing or damaged files. Could not initialize license ...
    • Error 1646 when installing QuickBooks

      When installing QuickBooks Premier on a computer where QuickBooks Pro of the same year is installed, or when installing QuickBooks Accountant on a computer that already has a Premier installation of the same year, you may receive this error: Error ...
    • Intuit Payment Services Link Error

      Symptom: You are trying to link the Intuit Payment Service to your QuickBooks company file, and you are receiving an error message saying "Oops, something went wrong." when trying to log into your merchant services account. Cause: This issue is ...
    • Bank error codes for downloaded transactions

      link for your bank error below for more information: Banking Error 102 Error 102 usually means your bank’s website is experiencing technical difficulties, undergoing maintenance or there is a server issue with the data transfer between the bank’s ...