Skip to main content

Get 50% OFF QuickBooks for 3 months*

Buy now
Switch to QuickBooks and 70% off for 3 Months
December 8, 2025
Question

The certificate was revoked by its certification authority.

  • December 8, 2025
  • 1 reply
  • 9 views

The connection from our software to QuickBooks is failing.

QuickBooks 2018, 2020, 2022 and Enterprise v23 all have the same issue.

It worked without any problems about a year ago.

 

QuickBooks 2012 Pro works fine. There is no problem with the connection with our software.

When I looked up the forum article, I checked the contents that came due to the issue of the expiration of the Symantec certificate in 2023.

Our machine is applied up to the latest Windows 10 version update, QuickBooks is also updated to the latest version.

I checked the qbsdklog.txt and found that the log was recorded. I guess this issue is the cause.

I want help with this issue.

 

==================================================

 

20251206.050141  D  9716  CertVerifier  Found signature certificate.

20251206.050141  D  9716  CertVerifier   simple issuer: Thawte Code Signing CA

20251206.050141  D  9716  CertVerifier   simple subject: N Software Inc.

20251206.050141  D  9716  CertVerifier   version: 2

20251206.050141  D  9716  CertVerifier   issuer: C=ZA, O=Thawte Consulting (Pty) Ltd., CN=Thawte Code Signing CA

20251206.050141  D  9716  CertVerifier   subject: C=US, S=North Carolina, L=Research Triangle Park, O=N Software Inc., OU=SECURE APPLICATION DEVELOPMENT, CN=N Software Inc.

20251206.050141  D  9716  CertVerifier   serial number: 4E26FF402185B9525545E0564A41AE5D

20251206.050141  D  9716  CertVerifier   issueDate: 2009-03-04

20251206.050141  D  9716  CertVerifier   expirationDate: 2010-04-18T23:59:59+00:00

20251206.050141  D  9716  CertVerifier  Got the Opus Info.

20251206.050141  D  9716  CertVerifier   no description found.

20251206.050141  D  9716  CertVerifier   no description URL found.

20251206.050141  E  9716  CertVerifier  The certificate was revoked by its certification authority.

20251206.050141  D  9716  RequestProcessor  Begin Session started...

20251206.050141  I  9716  RequestProcessor  OS: Microsoft Enterprise Edition (build 9200), 64-bit

20251206.050141  D  9716  RequestProcessor  Current Process is not elevated

20251206.050141  I  9716  RequestProcessor  Current User is in AdminGroup

20251206.050141  D  9716  RequestProcessor  Current Process is not ran as Admin

20251206.050141  I  9716  RequestProcessor  Current Process Integrity Level : 2000

20251206.050141  V  9716  RequestProcessor  Checking for CoLocatorClient::SmartGetQuickBooks

20251206.050141  V  9716  RequestProcessor  Not in-proc request.

20251206.050141  D  9716  RequestProcessor  File info: no file provided.

20251206.050141  D  9716  RequestProcessor  Getting an instance of pRunningInfo using pRunningInstanceFinder 

20251206.050141  D  9716  RequestProcessor  GetmajorVersion

20251206.050141  D  9716  RequestProcessor  GetReleaseNumber

20251206.050141  D  9716  RequestProcessor  Getflavor

20251206.050141  D  9716  RequestProcessor  GetdataFileVersion

20251206.050141  D  9716  RequestProcessor  There is a running version of QuickBooks: v33.0R16 (3302), bel, bel_stratum

20251206.050141  D  9716  RequestProcessor  Starting QuickBooks (no launch)

20251206.050141  D  9716  RequestProcessor  Performing QB Launch Retries

20251206.050141  D  9716  RequestProcessor  Check QB process ID before calling instance finder to find it.

20251206.050141  V  9716  RequestProcessor  QBW32.exe Proc Id: 0

20251206.050141  I  9716  RequestProcessor  Getting the IUnknown COM instance of QB

20251206.050141  D  9716  RequestProcessor  Obtained the IUnknown COM instance of QB without an exception

20251206.050141  D  9716  RequestProcessor  QuickBooks launch succeeded.

20251206.050141  V  9716  RequestProcessor  Check for Verify Certificate

20251206.050141  V  9716  RequestProcessor  Invoking Verify Certificate

20251206.050141  V  9716  RequestProcessor   Verify Certificate Invokeds

20251206.050141  V  9716  RequestProcessor  Invoking CompanyFileIsOpen

20251206.050141  V  9716  RequestProcessor  Invoked CompanyFileIsOpen

20251206.050141  D  9716  RequestProcessor  get_CompanyFileIsOpen call successful

20251206.050141  V  9716  RequestProcessor  Check for IsOpen

20251206.050141  D  9716  RequestProcessor  Check if the requested company file is already open.

20251206.050141  D  9716  RequestProcessor  yes. It is open.

20251206.050141  V  9716  RequestProcessor  Opening file..

20251206.050141  I  9716  RequestProcessor  Opening the file in the DoNotCare mode.

20251206.050141  D  9716  RequestProcessor  Attempt getting the Request Processor interface

20251206.050141  D  9716  RequestProcessor  Got query interface pointer till pReqProc2

20251206.050141  D  9716  RequestProcessor  Got query interface pointer till pReqProc3

20251206.050141  D  9716  RequestProcessor  Got query interface pointer till pReqProc4

20251206.050141  D  9716  RequestProcessor  Got query interface pointer till pReqProc5

20251206.050141  D  9716  RequestProcessor  Calling raw_SDKOpenFile4

20251206.050141  E  9716  RequestProcessor  Begin Session error = 8004258f, The application trying to connect to QuickBooks does not support QuickBooks Enterprise. Please contact the manufacturer of your application for a version that does support QuickBooks Enterprise.

20251206.050141  I  9716  RequestProcessor  Connection closed by app named '[My QB Apps]'

 

===================================================

1 reply

QuickBooks Team
December 9, 2025

Hi, Jaehoon. I truly appreciate you for reaching out with the detailed information, and for your efforts in updating both your machine and QuickBooks to their latest versions.

 

To fix this, let's update your third-party app then sync with QuickBooks. If you still see a certificate error, kindly follow these steps:

 

  1. Download zip file.
  2. Find the zip file in your Downloads folder or the location where it was saved, and extract the certSync.bat file.
  3. Right-click on the certSync.bat file and select Run as Administrator.
  4. Let the process run and make sure not to close the Command Prompt window until you see the message "CertUtil: -verifyCTL command completed successfully."
  5. Once the process is finished, close the Command Prompt window and start using your third-party app with QuickBooks.

 

If the issue persists, I highly recommend you contact your third-party app developer for further assistance to ensure compatibility with QuickBooks.

 

For additional information, you can refer to this article: Fix error QuickBooks - Application with Revoked Certificate.
 

If you have any further concern, please feel free to reach out. We're always here to help!