When using the VDM Calendar File scheduler, you may be unable to open, edit, or save scheduled jobs if the calendar file becomes unavailable or locked.
This article applies specifically to the Calendar File scheduler. BridgeWorks recommends using the SQL Scheduler Database when possible because it does not rely on a shared calendar file.
Symptoms
You may experience one or more of the following:
- Unable to open scheduled jobs
- Unable to edit existing scheduled jobs
- Unable to save scheduler changes
- Scheduler appears locked or read-only
- An error indicates that the calendar file is in use
- Changes to scheduled jobs do not appear as expected
Verify the Calendar File Location
The Calendar File location is configured under:
Settings → Scheduler → Calendar Location
Confirm that the configured location is accessible to both VDM and the BridgeWorks VDM Scheduler Service.
Avoid storing the Calendar File in folders synchronized by applications such as:
- Microsoft OneDrive
- Dropbox
- Google Drive
- Other cloud synchronization applications
Cloud synchronization can temporarily lock the Calendar File and prevent VDM from opening, editing, or saving scheduled jobs.
Verify the Scheduler Settings
When using the Calendar File scheduler, review the scheduler configuration in:
- User Options
- Global Options
- Service Options
Global Options and Service Options require VDM to be opened as an Administrator.
Verify that the scheduler settings are consistent, including:
- Calendar Location
- Use SQL Database setting
- SQL connection settings
- Scheduler Service settings
- Other scheduler-related paths or configuration values
Configuration differences can cause VDM and the Scheduler Service to use different scheduler settings.
Check for Calendar File Locking
Multiple VDM sessions or processes can contribute to the Calendar File becoming locked.
Check for:
- Multiple VDM windows
- Multiple Windows user sessions running VDM
- VDM processes still running in the background
- The Scheduler Service retaining access to the Calendar File
To clear a possible file lock:
- Close all open VDM sessions.
- Open Task Manager.
- Confirm that no VDM processes remain running.
- Close any remaining VDM-related processes if necessary.
- Stop the BridgeWorks VDM Scheduler Service.
- Open VDM.
- Start the Scheduler Service again.
- Test opening or editing a scheduled job.
If the Calendar File remains locked, restart the workstation or server and test again.
Verify the Scheduler Service
The Calendar File scheduler uses the Windows Scheduler Service.
Depending on your installation, the service may appear as:
- BridgeWorks VDM Scheduler Service
- Analytics Scheduler Service
- Ontario Reports Scheduler Service
To check the service:
- Open Windows Services.
- Locate the Scheduler Service for your installed product.
- Confirm that the service is running.
- Restart the service if necessary.
- Return to VDM and test the Scheduler again.
Administrators may also be able to start, stop, or restart the Scheduler Service from within VDM if service control has been configured.
Recommended Alternative: SQL Scheduler Database
Although the Calendar File scheduler is supported, BridgeWorks recommends using the SQL Scheduler Database whenever possible.
The SQL-backed scheduler provides:
- Reduced Calendar File locking issues
- Better support for multiple users
- Improved reliability
- Improved scalability
- More consistent Scheduler access
Unlike the Calendar File scheduler, the SQL-backed scheduler does not depend on a shared Calendar File that can become locked.
For configuration instructions, see:
VDM Scheduler Setup and Configuration Guide
If the Problem Continues
If scheduled jobs still cannot be opened or edited:
- Confirm the Calendar File location is accessible.
- Confirm the Calendar File is not stored in a cloud-synchronized folder.
- Verify the scheduler configuration in User Options, Global Options, and Service Options.
- Close additional VDM sessions and background processes.
- Restart the Scheduler Service.
- Restart the workstation or server if necessary.
- Test the Scheduler again.
If the issue continues, gather screenshots of the scheduler configuration and relevant VDM logs before contacting BridgeWorks Support.
Comments
0 comments
Please sign in to leave a comment.