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

Troubleshooting Webgility Desktop Performance Issues

This article helps Webgility Desktop users in addressing issues where SQL log processing becomes stuck or significantly delayed. Such delays can negatively impact Webgility Desktop’s performance if not addressed promptly.

Overview

This guide outlines step-by-step instructions to troubleshoot and resolve issues where SQL log processing becomes stuck or significantly delayed. These delays can impact Webgility Desktop's performance if not addressed promptly.

Common Symptoms

  • SQL logs remain in a "Processing" state without progress.

  • Processing duration exceeds expected time (typically more than 1 hour).

  • You are unable to delete logs due to insufficient access rights on the server.

Immediate Troubleshooting Steps

Step 1: Advise a Full System Restart

Try rebooting the system that hosts Webgility.

Why?
Restarting the system helps clear any locked resources or orphaned processes that may be interfering with SQL log processing.

Step 2: Ensure Applications Are Fully Closed

Before restarting SQL log processing:

  • Confirm that both Webgility and the Webgility Scheduler are fully closed.

  • Instruct the user to use Task Manager to end any residual Webgility-related processes.

Step 3: Attempt SQL Log Reprocessing

After reboot:

  • Relaunch Webgility and check again