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

Troubleshooting Scheduler Startup Issues on Add-On Computers: Firewall and Permissions

This article helps Webgility Desktop users in resolving issues with the Scheduler failing to start on add-on (secondary) computer. Common causes include Windows Firewall blocking essential application components and insufficient application permissions. The article provides a step-by-step approach to diagnose and fix these problems, ensuring the Scheduler runs smoothly across all connected machines.

Overview

When deploying the Scheduler on an add-on (secondary) computer, it may fail to start properly even though it works on the primary server. One common cause is Windows Firewall blocking the necessary application components, compounded by insufficient application permissions. Follow the steps below to systematically diagnose and resolve these issues.

Common Causes

  • Windows Firewall Restrictions: Blocked inbound or outbound connections needed by the Scheduler or associated automation tasks.
  • Application Permissions: The Scheduler or the automation app (e.g., WebDisplay) must have sufficient privileges (often administrator-level) to function correctly.

Step-by-Step Troubleshooting

1. Confirm Error Symptoms

  • Verify that the Scheduler starts normally on the main server.
  • Attempt to start the Scheduler on the add-on computer and note any error messages (such as connection or access denied).

2. Check Windows Firewall Settings

  • On the add-on computer, open Windows Defender Firewall from the Control Panel.
  • Select Allow an app or feature through Windows Defender Firewall.
  • Locate your Scheduler or WebDisplay application in the list. If not present:
    • Click Allow another app..., browse, and add the executable.
  • Ensure both Private and Public network boxes are checked.
  • Click OK to save changes.

Alternative: Open Specific Ports

  • If directed by documentation, create inbound/outbound rules for the Scheduler’s port:
    • Open Windows Defender Firewall with Advanced Security.
    • Select Inbound Rules > New Rule.
    • Choose Port, specify the required port, then Allow the connection.
    • Repeat for Outbound Rules if needed.

3. Verify Application Permissions

  • Right-click the Scheduler or WebDisplay shortcut.
  • Choose Run as administrator. This step is critical for automation modules that require elevated access.
  • If success is confirmed, set the shortcut to always run as administrator:
    • Right-click the shortcut and select Properties > Compatibility tab.
    • Check Run this program as an administrator, then click OK.

4. Confirm Resolution

  • After making these changes, attempt to start the scheduler again on the add-on computer.
  • If it launches successfully and automation functions as expected, the issue is resolved.