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

How to Fix Mutex Errors When Starting the Webgility Scheduler

This article helps Webgility Desktop users troubleshoot mutex errors encountered when starting the Webgility Scheduler. It explains that such errors typically occur because a previous scheduler session (unifyscheduler.exe) is still running or didn’t shut down properly, preventing a new instance from launching.

Overview

A mutex error during the launch of the Webgility Scheduler usually indicates that a previous instance of the scheduler process (unifyscheduler.exe) is still active or was not properly closed. This prevents new instances from starting successfully.

Root Cause

Webgility Scheduler uses a mutex (mutual exclusion object) to ensure that only one instance runs at a time.
If the unifyscheduler.exe process does not terminate properly, the system blocks additional attempts to launch it, resulting in a mutex error.

Resolution Steps

Step 1: Terminate Any Existing Scheduler Processes

  1. Open Task Manager (Ctrl + Shift + Esc or right-click the taskbar and select Task Manager).

  2. Go to the Processes tab.

  3. Locate all instances of unifyscheduler.exe.

  4. Select each instance and click End Task to close them.

Step 2: Restart the Scheduler via Webgility

  1. Launch the Webgility Desktop application.

  2. Navigate to Scheduler Settings (location may vary depending on your version).

  3. Click Start Scheduler or the relevant option to restart the process.

Step 3: Confirm the Issue is Resolved

  • Ensure the scheduler starts without any error messages.

  • Verify that your scheduled tasks are now running as expected.