Skip to content
  • There are no suggestions because the search field is empty.

Resolving Webgility Desktop Errors: Semaphore Timeout, Database Upgrade, and QuickBooks Disconnect

This article helps Webgility Desktop users troubleshoot common errors that may occur after a software update, such as semaphore timeout errors, database upgrade issues, and QuickBooks Desktop disconnects. It provides step-by-step instructions for checking service locations, moving services to the correct server, restarting the system, and reconnecting QuickBooks Desktop to restore normal operations.

Overview

After updating Webgility Desktop, you may occasionally run into a few common errors—like semaphore timeout, database upgrade issues, or QuickBooks disconnects. These are typically caused by service or connection changes during the update process. Here's a simple guide to help you get things back on track.

1. Start by Understanding the Error

Before jumping into fixes, gather a bit of context:

  • What error messages are showing?

  • Was there a recent update or system change?

  • Are you running Webgility on a local machine or across a network?

2. Fixing Semaphore Timeout and Database Upgrade Errors

These errors often point to service disruptions or misconfigured connections, especially in network setups.

Here’s what to do:

Check Where Services Are Running

  • Confirm if the Webgility Services (like the Webgility Service or database) are running locally or on a network server.

  • If they’re not on the intended machine, consider moving them to the correct server.

 Move Services to the Network Server

  • Stop all Webgility-related services on the machine they’re currently on.

  • Shift the services and/or database to the designated network server.

  • Use the Services Manager or Control Panel to start them on the correct machine.

 Restart the Server

  • Restart the server where the services now reside.

  • Make sure all Webgility services start automatically and are running without issues.

 Retry the Operation

  • Try the upgrade or the task that failed earlier.

  • Semaphore timeout and DB upgrade errors should no longer appear.

3. Reconnecting to QuickBooks

If QuickBooks becomes disconnected after an update, follow these steps:

 Check the QuickBooks Connection

  • Go to Connection > Accounting >Edit connection in Webgility.

  • Click test connection. If it fails, note down any error message.

4. Test Everything

Once everything’s reconnected and updated:

  • Run your regular Webgility workflows—like syncing orders, updating inventory, or generating reports.

  • Make sure everything is functioning smoothly.