Troubleshooting Unable to Open or Edit Scheduled Jobs When Using the VDM Calendar File

Trouble Viewing Images? Right-click on any image and select "Open in new tab" to view a larger version. You can also zoom in using Ctrl + Mouse Wheel for easier readability.

Symptoms

You may experience one or more of the following issues when using the VDM Calendar File scheduler:

• Unable to open scheduled jobs
• Unable to edit existing scheduled jobs
• Unable to save scheduler changes
• Scheduler appears locked
• Error messages indicating the calendar file is in use
• Scheduler jobs do not update after changes are made

Overview

When using the VDM Calendar File scheduler method, VDM stores scheduling information in a calendar file located on the local system. Several factors can prevent VDM from accessing this file, including configuration mismatches, file locking, permission issues, or scheduler service conflicts.

This article outlines the most common causes and resolutions.

Verify the Calendar File Location

The calendar file location is configured under:

Settings → Scheduler → Calendar Location

Example:

C:\Temp\CalendarBackups\

The calendar file should be stored on a local drive accessible by both VDM and the BridgeWorks VDM Scheduler Service.

Important

Avoid storing the calendar file in folders synchronized by cloud backup applications such as:

• Microsoft OneDrive
• Dropbox
• Google Drive
• Other cloud synchronization utilities

These applications can temporarily lock the calendar file while synchronizing, preventing VDM from opening, editing, or saving scheduled jobs.

Verify Scheduler Settings Match

VDM contains three scheduler configuration areas:

User Options

Available when VDM is launched normally.

Global Options

Available only when VDM is launched as Administrator.

Service Options

Available only when VDM is launched as Administrator.

Important

When using the Calendar File scheduler, all three configuration areas must match.

Verify that the following settings are consistent across:

• User Options
• Global Options
• Service Options

Review:

• Calendar Location
• Use SQL Database setting
• SQL Connection settings
• Scheduler Service settings
• Any scheduler-related paths or configuration values

Mismatched settings can cause VDM and the Scheduler Service to access different scheduler configurations, resulting in file conflicts and locked schedules.

Verify the BridgeWorks VDM Scheduler Service

The Calendar File scheduler relies on the Windows service:

BridgeWorks VDM Scheduler Service

To verify the service:

1. Open Windows Services (services.msc).
2. Locate BridgeWorks VDM Scheduler Service.
3. Confirm the service is running.

If you have Windows Administrator permissions, you can:

• Start the service
• Stop the service
• Restart the service

A service restart will often resolve temporary communication or file access issues.

Managing the Scheduler Service from Within VDM

VDM can also control the Windows Scheduler Service directly from the application.

Using the Services menu within VDM, administrators can:

• Start Service
• Stop Service
• Restart Service

This eliminates the need to open Windows Services.

Note: This functionality must be configured before it becomes available. Refer to the article:

Scheduler Service Setup

Verify User Permissions

Users without Windows Administrator permissions may not be able to manage the scheduler service.

If users need the ability to start, stop, or restart the scheduler service without local administrator rights, refer to:

Controlling Scheduler Service Without Administrative Privileges

Check for Multiple VDM Sessions

The calendar file can only be controlled by a single active session.

Common causes include:

• Multiple VDM windows open
• Multiple VDM user sessions
• Hidden VDM processes running in the background
• A scheduler service that did not properly release the calendar file

When multiple sessions attempt to access the calendar file simultaneously, the file may appear locked.

Resolution

1. Close all VDM sessions.
2. Open Task Manager.
3. Verify no VDM processes remain running.
4. End any remaining VDM-related processes.
5. Stop the BridgeWorks VDM Scheduler Service.
6. Launch VDM.
7. Start the scheduler service.
8. Verify VDM can access the calendar file.
9. Test opening and editing scheduled jobs.

If the issue persists, restart the workstation or server to clear any remaining file locks.

Recommended Recovery Procedure

If scheduled jobs still cannot be opened or edited:

1. Close all VDM sessions.
2. Confirm no VDM processes remain running in Task Manager.
3. Stop the BridgeWorks VDM Scheduler Service.
4. Open VDM.
5. Start the scheduler service.
6. Test scheduler functionality.

If necessary:

1. Reboot the machine.
2. Repeat the steps above.

Review Scheduler Configuration for Conflicts

If the scheduler remains inaccessible after clearing locks and restarting services:

1. Review User Options.
2. Review Global Options.
3. Review Service Options.

Verify all scheduler settings match exactly.

Any mismatch can cause VDM and the scheduler service to compete for control of the calendar file.

Recommended Alternative: SQL Scheduler Database

While the Calendar File scheduler is supported, BridgeWorks recommends using the SQL Scheduler Database whenever possible.

Benefits

• Improved reliability
• Reduced file-locking issues
• Better multi-user support
• Improved scalability
• More consistent scheduler performance

Requirements

• Microsoft SQL Server
• Scheduler database configuration

For complete setup instructions, refer to:

VDM Scheduler Setup and Configuration Guide

Summary Checklist

Before escalating a scheduler issue, verify the following:

☐ Calendar file is stored locally

☐ Calendar file is not located in a OneDrive or cloud-synchronized folder

☐ User Options, Global Options, and Service Options match

☐ Only one VDM session is running

☐ No hidden VDM processes exist in Task Manager

☐ BridgeWorks VDM Scheduler Service is running

☐ Scheduler service has been restarted

☐ User permissions are sufficient

☐ System has been rebooted if necessary

☐ Scheduler configuration has been reviewed for conflicts

☐ Consider migrating to the SQL Scheduler Database for improved reliability

If all checks have been completed and the issue persists, gather screenshots of the scheduler configuration settings and contact BridgeWorks Support for further investigation.