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

Webgility Desktop: Resolving Scheduler Order Download and Connection Problems Post-Update

This article helps Webgility Desktop users in troubleshooting and resolving scheduler connection issues that arise after updating the Webgility Desktop software. These issues often result in the scheduler failing to connect or download orders and are typically caused by version incompatibilities, expired or invalid certificates, or server processes not being restarted to apply updates. The guide provides step-by-step instructions to identify the root cause and restore proper scheduler functionality.

Overview

This guide covers troubleshooting and resolution steps for scheduler connection issues encountered after updating Webgility software. Issues often manifest as the scheduler failing to connect or download orders, commonly following certificate or version mismatches.

Symptoms

  • Scheduler unable to download orders.
  • Errors referencing certificates or failed connection attempts in logs.

Root Causes

  • Outdated Webgility software is incompatible with scheduler requirements.
  • Expired or invalid certificates preventing secure communications.
  • Server processes not reloaded to apply new configurations or certificates.

Step-by-Step Resolution

1. Verify Software Version

  • Log in to the affected server.
  • Check the current Webgility software version:
    • Check Help > Terms and Privacy.
  • If outdated, proceed to update:
    • Download the latest installer from the vendor site.
    • Follow on-screen instructions to upgrade safely.

2. Regenerate Certificates

  • Open the QuickBooks Desktop Tool.
  • Locate the Certificates under Edit > Preferences > Integrated appications.
  • Choose Regenerate Certificates.
  • Follow prompts to complete generation. This updates SSL/TLS or client certificate pairs required for secure scheduler-server communication.

3. Restart the Server

  • After certificate regeneration, restart the Webgility server service:
    • Linux: sudo systemctl restart webdelivery
    • Windows: Restart the service from the Services console or run net stop webdelivery followed by net start webdelivery in Command Prompt.
  • Ensure that all dependent services are also restarted, if necessary.

4. Verify Scheduler Functionality

  • Open the Scheduler settings in Webgility.
  • Confirm that the settings are correctly saved in the scheduler.
  • Restart the scheduler:
    • Check logs for any errors; absence of errors indicates successful connection and download.