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

How to Fix Scheduler Crashes When ‘Run at Startup’ Is Enabled in Webgility Desktop

This article helps Webgility Desktop users in resolving unexpected crashes of the scheduler application when the 'Run at Startup' option is enabled. These crashes are often caused by session-specific restrictions tied to user authentication settings. Based on a recently resolved case, the article provides structured steps to verify the root cause and implement a solution, ensuring stable scheduler performance on system startup.

Overview

When the scheduler application crashes unexpectedly with the 'Run at Startup' option enabled, it is often due to session-specific restrictions related to user authentication. This article provides structured steps to verify the root cause and solution based on a recent resolved case.

Incident Summary

  • Issue reported: Scheduler crashed after enabling 'Run at Startup'.
  • Troubleshooting revealed: Scheduler depends on user login for proper initialization.
  • Resolution: Scheduler started correctly once the user logged in to the user account and rebooted as instructed.

Step-by-Step Troubleshooting Guide

1. Confirm Scheduler Settings

  • Verify 'Run at Startup' is enabled in the scheduler UI.
  • Check if the application is set to launch under a specific user context.

2. Identify Crash Symptoms

  • Gather Webgility scheduler logs or event viewer entries.
  • Note timing of the crash (e.g., immediately after boot, during user login, etc.).

3. Determine User Login Behavior

  • Ask: Does the user account require a password or direct login at boot?
  • Confirm: Is the affected scheduler configured to run under a personal user profile or as a system service?

4. Advise Correct Startup Procedure

    • Scheduler requires the associated user session to be active for automatic start.
    • Automatic launch at system boot will only occur after logging in to the specified user account.
    • If running as a system service is required for unattended startup, verify appropriate configuration and permissions.

5. Validate the Resolution

  • Instruct the user to:
    1. Log off all accounts.
    2. Log in to the user account associated with the scheduler.
    3. Reboot the workstation.
    4. Confirm that scheduler starts without crashes.