Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
I was just on the phone with Right Networks, they are testing a fix now and if all goes well they will have the update to RN users asap. If you go to https://status.rightnetworks.com/ you can sign up for the updates and see the status
Guys,
I think the issue is happening because the signature of the webconnector.exe itself is expired, so if you replace the webconnectore.exe with the correct version that matches your QuickBooks version, the case will be resolved.
Check the instructions in the link below. Works for us.
How to fix the error QuickBooks - Application with Revoked Certificate (intuit.com)
I managed to get it to work. I have ZERO I.T. experience, but i did it! At first it didn't work, because I wasn't on the ADMIN side of Quickbooks. You have to be logged into that one, to grant the permission. I'm so thankful this worked. This really stressed me out. I've seen others having more important reasons to get this up and running (like payroll etc) so I hope they too can get this up and running asap. Good luck everyone!!
Did all these steps.
The certificate is now valid, but this webconnector app does not open at all. Double clicking on it does absolutely nothing.
This did not fix it for me.
That likely means you don't have the fixed webconnector.
The fixed webconnector.exe DOES has a valid certificate. Our problem is that this program doesn't start at all.
I am getting same thing. Replaced web connector file as per instructions. Web connector will not even launch now.
What is the error? Did you try to run the webConnector as Admin?
Also, you can check the Windows event viewer for both application and system for extra error log on execution
We have run the fix. Still getting the error message. I cannot run the webconnector as Admin because the program I link to only allows one user to connect and it is not set up as the admin.
There is no error message. It just doesn't run. Tried as admin, nothing. Double click on the application, absolutely nothing happens. Normal behavior is that the program window should open.
Here's the Windows event log. Anyway it looks like it's still NOT fixed on the Intuit side.
Log Name: Application
Source: .NET Runtime
Date: 8/23/2023 10:55:08 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ns575229
Description:
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()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x[removed]0000</Keywords>
<TimeCreated SystemTime="2023-08-23T17:55:08.900780400Z" />
<EventRecordID>735126</EventRecordID>
<Channel>Application</Channel>
<Computer>ns575229</Computer>
<Security />
</System>
<EventData>
<Data>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()
</Data>
</EventData>
</Event>
---------
and this
---------
Log Name: Application
Source: Application Error
Date: 8/23/2023 10:55:08 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ns575229
Description:
Faulting application name: QBWebConnector.exe, version: 2.3.0.240, time stamp: 0x6299dc64
Faulting module name: KERNELBASE.dll, version: 10.0.[removed], time stamp: 0x160cb2f6
Exception code: 0xe0434352
Fault offset: 0x00125432
Faulting process id: 0x4a14
Faulting application start time: 0x01d9d5eaf4b1d6d0
Faulting application path: C:\Program Files (x86)\Common Files\Intuit\QuickBooks\QBWebConnector\QBWebConnector.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 24cb7d6b-4ead-4b73-8e76-e1fa2875c1d5
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x[removed]0000</Keywords>
<TimeCreated SystemTime="2023-08-23T17:55:08.960676200Z" />
<EventRecordID>735127</EventRecordID>
<Channel>Application</Channel>
<Computer>ns575229</Computer>
<Security />
</System>
<EventData>
<Data>QBWebConnector.exe</Data>
<Data>2.3.0.240</Data>
<Data>6299dc64</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.[removed]</Data>
<Data>160cb2f6</Data>
<Data>e0434352</Data>
<Data>00125432</Data>
<Data>4a14</Data>
<Data>01d9d5eaf4b1d6d0</Data>
<Data>C:\Program Files (x86)\Common Files\Intuit\QuickBooks\QBWebConnector\QBWebConnector.exe</Data>
<Data>C:\Windows\System32\KERNELBASE.dll</Data>
<Data>24cb7d6b-4ead-4b73-8e76-e1fa2875c1d5</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Your instructions on how to contact you and report that I am having the same issue appear to be for online versions. Can you please post instructions for desktop versions.
Thanks
looks like the app can not open a file either because the file does not exist or there is no permission. Did you copy the file to the directory with the original WebConnector.exe? If yes, I would
1. Uninstall the application,
2. Then install the latest version of the web connector from 2.3.0.215 from https://static.developer.intuit.com/resources/quickbooksWebconnector/QBWebConnector2_3R0_00215.zip
3. Then, depending on the version of your QB, follow this How to fix the error QuickBooks - Application with Revoked Certificate (intuit.com)
After downloading the new exe file, Remember you need to copy the new webconnector.exe in either
I hope this can help you. We were there with a few of our clients using our warehouse application with QB and know how stressful this can be.
I just called Quickbooks and your technician said it was the 3rd party field service application's fault using an outdated certficate. He said it wasn't Quickbooks and couldn't help me. He then hung up on me. Who's fault is it? How do we correct - through the 3rd party or Quickbooks? I took all the steps in your "Quickbooks - Application with Revoked Certificate" and it isn't work. Please advise.
Thank you for reaching out to the Community for help with this issue, everyone.
We are here for you and want to help get you back to business quickly.
The issue usually occurs because the QuickBooks Web Connector digital certificate has expired. Not to worry, I've listed the steps below to resolve this:
You can also visit our QuickBooks Status page to monitor the progress. There will also be an option to subscribe to get notifications automatically.
Additionally, I've added an article that'll help you review your bank transactions in QuickBooks Desktop to ensure you add them to the correct accounts: Add and Match Bank Feed Transactions.
I appreciate all your patience in this matter. Please know that we're doing our best to resolve this issue. Keep us posted if you need help integrating applications or managing your books.
My IT people said that they did these steps. It is still not working for any of our integrated applications.
What version should the WebConnector be if it is fully updated?
I did everything from the original corrections to uninstalling and reinstalling Web Connector but nothing works yet!!
I have tried the fix as well....does not work. QB keeps saying they are working on it but still no fix. Can someone from QB give us something other than "here is how to tell us you are having a problem and we care about fixing it....but, we can't fix it"!!!!!!!
These steps do not work for me. After completing these steps, the QBWebConnector.exe still doesn't work. When I check the Windows Event Viewer in the Application folder, I see this error:
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()
Did ALL that multiple times, very carefully. The new version of webconnector V.240 does have a valid certificate. But the executable FAILS TO RUN. NOTHING happens when you try to run it. I've posted the Windows event log earlier. The issue is NOT resolved.
Hello everyone.
I can see the urgency of getting your concerns rectified with revoked certificates in QuickBooks Desktop (QBDT). I have details to share about the functionality and why the said problem is occurring.
Currently, we have an ongoing investigation about the Revoked Certificate warning when trying to use QuickBooks Web Connector. The issue is caused by an expired certificate for the Web Connector application. Thus, our engineering team is working on getting the certificates updated in a new Web Connector installer to fix what our customers are experiencing.
In this, I recommend contacting our Technical Support Team. This way, they can add your company file to the list of affected users and provide this investigation number for easy tracking: INV-91854.
Here’s how:
On the other hand, you can refer to this link and click the Contact Us button. This will route you to fill out some information about the product you are using and enter a brief description of your concern. Then, please choose a way to connect with us: Contact QuickBooks Desktop support.
We appreciate your patience while we’re working on this one. Stay safe!
I finally got this resolved. The most recent version of WebConnector on Quickbooks site is 2.3.0.215.
However, I had a folder on my computer with version 2.3.0.240. I don't even know how that got there. It must have been automatically updated.
But the new replacement version of QBWebConnector.exe only works with version 2.3.0.240.
Again, I don't even know where to get version 2.3.0.240, but that is required to make the new .exe file work.
I missed the last part of "COPY" Web Connector to the same folder you renamed it to OLD. Once we did that, then opened quickbooks and it asked for sync settings again and worked fine
Same issue. Instructions in the Link do not work.
A. Using the cut'n'paste C:\Program Files (x86)\Common Files\Intuit\QuickBooks\QBWebConnector\ provided in the instructions doesn't work. Couldn't find the application. Went to the download folder as recommended by my 2nd QB tech support rep. Found QBWebConnector.exe.config but not QBWebConnector.exe. Went to programs and followed the trail in the link, no such fiile.
B. In the instructions c.) uses the extension ese not exe - please proof read!!
Initially went to chat and was told to provide all this file information (some about needing payroll), gave them my info. told them I am a ProAdvisor and was told I wasn't authorized to work with the file??
The rep I spoke to when I called tried to walk me through updating but she agreed the file I found was not the correct one. She said to try back at 5pm (LOL). Meanwhile this is a client file and they need the sync information to do their job.
Seriously, why am I a ProAdvisor?
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