How to Restore Your Webgility and QuickBooks Connection After a Power Outage
This article helps Webgility Desktop users restore connectivity with QuickBooks Desktop Enterprise after a power outage. Power interruptions can corrupt active connections, invalidate cached credentials, or disrupt certificates—leading to failed integration. The guide focuses on resolving issues where the QuickBooks Desktop certificate is no longer recognized by Webgility Desktop.
In rare situations, businesses may experience power outages that result in unexpected shutdowns of applications. One common consequence is the loss of connectivity between Webgility and QuickBooks Desktop.
Power interruptions can corrupt active connections, invalidate cached credentials, or disrupt certificates and tokens used for integration. In this scenario, the QuickBooks certificate used by Webgility was no longer recognized, causing a communication failure between the two systems.
Steps to Restore Connection
1. Restart Applications
Close QuickBooks Desktop Completely:
-
Exit QuickBooks Desktop.
-
Open Task Manager (Ctrl + Shift + Esc).
-
End any running QuickBooks processes (e.g.,
QBW32.exe,QBUpdate.exe).
Exit Webgility:
-
Ensure Webgility is fully closed
2. Restart Applications in Order
-
First, launch QuickBooks Desktop and open the company file.
-
Next, open Webgility.
3. Regenerate the QuickBooks Certificate
If the connection is still not restored, the issue likely lies in a corrupted or invalid certificate.
To regenerate the certificate:
🔗 Follow this official guide:
How to Regenerate the QuickBooks Certificate
This process will generate a new integration certificate, re-establishing secure communication between Webgility and QuickBooks.
Following the above steps typically resolves the connectivity issue caused by a power outage, restoring full integration between Webgility and QuickBooks.