Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Doesn't work
Not fixed.
I was told to try again at 5pm, they would not contact me. Great service. The price goes up and the service goes down.
I just want the dam thing fixed!!
This did the trick! We had previously noticed that Intuit was offering an older version during this event. We had saved 2.3.0.240 in a backup folder before we installed the older version. Based on your comment, went back to the latest version, and now, using the updated exe with the fixed certificate is finally working.
Here is a step by step video to help walk you through the process! Hope this helps someone!
I just added a video guide to walk you through the process to correct the issue.
Our business is using QB Enterprise 2019, and we have a critical app that is not working now because of this revoked signature. Please fix for 2019 and prior versions too, thanks!
Welcome to the QuickBooks Community, HCice. Please know QuickBooks Desktop 2019 software was already discontinued. With this, let me provide further details about this and troubleshooting steps to resolve the certificate error. This is to ensure that you can organize your connected apps in QBDT smoothly.
The discontinuation includes all 2019 versions of QuickBooks Desktop Pro, Premier, for Mac, and Enterprise Solutions v19. Furthermore, you no longer have access to live technical support once you run into problems and are unable to receive the latest critical security patches and updates. You can open this article to see extra details: QuickBooks Desktop 2020 service discontinuation policy.
Then, I suggest following the steps below to remove the revoked signature or a certificate error on your end.
Once done, close the window and start using your third-party app with QuickBooks.
Furthermore, to continue working on your QuickBooks data and to always have the latest features and fixes, I suggest upgrading your QBDT to a newer version. You can open this article to see the steps on how to perform the process: Upgrade QuickBooks Desktop Pro, Premier, or Enterprise.
Lastly, refer to this article if you need to see different details on what features are included in the QBDT 2023 release and how you can use them to benefit your business: What’s new in QuickBooks Desktop 2023.
You can always post back if you need additional assistance in managing your QuickBooks account. I'm always here, HCice.
I tried this and it didn't work. Any other ideas?
Where is that version as it does not appear on the QB site anywhere. can you please post link to it. much appreciated!!
Hi there Scott, and Jonesee. Thanks for following up on this thread.
If you're experiencing a revoked certificate issue with a third-party integration in QuickBooks Desktop (QBDT), we can help you fix it by updating your QBDT to the newest version. You can utilize this link for accurate information: Update all versions of QuickBooks Desktop to the latest release.
Then, follow these next steps:
For the detailed process, check out this link: How to fix the error QuickBooks - Application with Revoked Certificate.
To get updates about the status of this issue, please check here. There will also be an option to subscribe to get updates automatically.
If you're done performing these steps but the same thing happens, I recommend reaching out to our QuickBooks Support Team. They have all the necessary tools to pull up your account securely and further investigate the issue.
Here’s how you can reach out to them:
I've added this article helpful article for future reference if you want to integrate your QBDT with QB Time: Setup and use QuickBooks Desktop for Windows and QuickBooks Time integration.
Don't hesitate to leave your reply if you have other QuickBooks concerns. We'd be glad to help. Take care.
I am having the same problem. Went through the steps yesterday. Even tried some other steps I looked up and restarted the computer a couple of times. It still isn't working.
RIGHT NETWOKS USERS - Looks like they have a fix, you will just need to remove your applications from the webconnector and re-install them. We are on QB 2022 with Right Networks and this fix worked.
From Right Networks:
Monitoring - Our team has finished updating QuickBooks to address the “certificate revoked” error when using 3rd party integrations. Depending on the application you utilize, you may need to remove and re-add the certificate.
To remove the application, please follow the steps below:
1) Log in to the QuickBooks company file as the QB Admin and in single user mode.
2) Click Edit and select Preferences.
3) From Integrated Applications, select Company Preferences.
4) In the application list, select the application and click Remove.
5) Exit the Preferences window.
6) Close QuickBooks
To re-add the integration please follow our KB below:
https://helpdesk.rightnetworks.com/s/article/Integrating-Third-Party-Applications-into-your-QuickBoo...
Aug 24, 2023 - 07:41 EDT
I would try that but now I can't even get QB to open. Keep getting a pop up that says the file is already open. Beyond frustrating because I can't even open a ticket with QB support.
I just got off of the phone with support. This is NOT solved.
Once upon a time... there was a small business owner. It was hard to send out invoices, pay bills, do banking and keep track of financial statements manually. Then a fairy godmother said "go to Staples and buy Quickbooks -- it will make your life easier". And it did -- for many, many years. That software was always stable and prepared to do AR/AP and anything that the business owner wished for. When the business owner wanted to take advantage of an upgrade, they went back to Staples, got a new CD, and upgraded to the latest version, which would also serve the business owner well.
Then one day, someone at Intuit said "Wait -- we can make more money if we force everyone to a subscription model! They can pay us every year, and they get the latest update -- whether they want it or not". Well, the revenue stream probably increased at Intuit, but the poor small business owners are frustrated. Every 8 weeks, their businesses are severely disrupted by some new "known problem" that rears its ugly head. The software that we have grown to depend on to make our lives easier, is now making our lives stressful. Can't do payroll -- there is a problem!! Can't sent out invoices -- there is a problem! They've expired my software -- can't do anything! It is unbearable.
How can the small business owner live happily ever after? Perhaps it is time to find new accounting software. I wonder if whomever thought a subscription model would increase revenue, factored in long-time users who banished this software to the trash bin, never to use it again!
I have tried all of these steps and its still not working! QB Enterprise 2022
I've been having the cert issue since yesterday, and I get the same company file in use message after I get out and try to get back in. A reboot fixes that part of the problem.
If I am in QB as the administrator, it is unusable -- popup message about the cert just loops. If I get in as a non-administrator, I can get other work done.
Tried the fix: Does not work for me! QuickBooks POS 11 & QuickBooks Desktop 2023. Worked fine Monday but not on Tuesday or since.
To be clear, if I have an older version of QBDT, the issue will not be fixed?
The critical 3rd party software that I use is stable and is not configured to work with a new version of QB. I have no guarantee that upgrading to a newer version of QB will resolve the problem. If I am forced to buy a new version of software that previously worked fine, I might as well put the effort into another accounting software product entirely.
After following these steps, the QBWebConnector.exe errors out with the following exception:
Application: QBWebConnector.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
at QBWebConnector.App.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at QBWebConnector.App.Main()
Faulting application name: QBWebConnector.exe, version: 2.3.0.240, time stamp: 0x6299dc64
Faulting module name: KERNELBASE.dll, version: 10.0.[removed], time stamp: 0xd343834f
Exception code: 0xe0434352
Fault offset: 0x00125a12
Faulting process id: 0x1690
Faulting application start time: 0x01d9d69735dff32d
Faulting application path: C:\Program Files (x86)\Common Files\Intuit\QuickBooks\QBWebConnector\QBWebConnector.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 8646744e-cf89-4cc9-b395-d8a64b6f68ef
Faulting package full name:
Faulting package-relative application ID:
The problem is definitely QBWebConnector.exe. Call Intuit back.
Following this "Fix" I was not able to open QB Web Connector. Still sitting on non functional (non-) integrated app.
To be clear...If I am running a version of QBDT older than 2021, it will never be fixed?
I run a very specific 3rd party application that is critical to my company. It is stable, and will not be updated. It may not connect to a newer version of QB. There is no guarantee that upgrading QB will solve the issue.
This is beyond frustrating. Intuit broke the connection. They should fix it. If I am forced to put time and money in to upgrading, it will be with another product that does not treat it's customers like this.
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.
For more information visit our Security Center or to report suspicious websites you can contact us here