DVLS: SCHEDULER_NO_STANDBY_AVAILABLE

Hello Andreas,
Thank you for reaching out to our forum. The issue you're encountering with the Scheduler Service can stem from several possible causes, such as:

• The required .NET runtime is either missing or corrupted
• The service is running under an account that lacks the necessary permissions
• Security tools (like antivirus or firewall) are delaying or blocking the service
• The service path is broken or misconfigured

Here’s what I recommend checking next:

1. Open the Devolutions Console, go to the Support tab, and run the IIS Diagnostic tool to confirm that all prerequisites are in place.
2. In Windows Services, verify the account used to run the Scheduler Service. If issues persist, try changing it to Local Service and test again.
3. Check Event Viewer (Application and System logs) for recent errors related to .NET Runtime or other relevant services.
4. Confirm that no new security rules or antivirus updates are interfering with the service.

If neither helps try to go under companion Tab and unistall and reinstall the scheduler.

Additionally, here’s a helpful article that explains how to enable debug logging for the Scheduler Service:
https://docs.devolutions.net/server/kb/knowledge-base/scheduler-service-general-information/#enable-scheduler-logging
Let me know what you find, and I’ll be happy to assist further.

Hi Michel

After reinstall the whole service and changed also the service user to local system, i had again the same error this night:


Please check my gathered informations below.

• The required .NET runtime is either missing or corrupted

service is installed since 2021 and have never made problems before updating to dvls v2025. no dotnet errors available in eventlog so far.
only events i got are the those:

• The service is running under an account that lacks the necessary permissions

its a local admin

• Security tools (like antivirus or firewall) are delaying or blocking the service

no activity logs in the specific time range

• The service path is broken or misconfigured

i would be unable to restart the service if this is the case

1. Open the Devolutions Console, go to the Support tab, and run the IIS Diagnostic tool to confirm that all prerequisites are in place.

1. In Windows Services, verify the account used to run the Scheduler Service. If issues persist, try changing it to Local Service and test again.

i've reinstalled (uninstall and installed) the service. also tried it with system user and local path instead of unc paths which points to the same destination

1. Check Event Viewer (Application and System logs) for recent errors related to .NET Runtime or other relevant services.

no dotnet relevant events under application events in the given time range. dotnet is working good so far

1. Confirm that no new security rules or antivirus updates are interfering with the service.

There are no activities in av logs in this timespan

FYI: Other Services like Devolutions Gateway Service are working nonstop.
Ive also activated Debug Logs. But there are no better logs available, also not on Syslog Server.

Best Regards
Andreas

Hello Andreas,
Based on what’s shown in your Event Viewer, it looks like the scheduler is timing out. This can be caused by several factors. I’d like to share a link to our knowledge base that outlines all the tasks managed by the scheduler service account:
Scheduler Tasks – Devolutions KB
I recommend going through each scheduled task in your Devolutions Server Web UI and stopping them one by one to identify which one is causing the issue. In many cases, timeouts occur during log cleanup operations.
For more detailed insights, you can enable debug logging by going to Administration > Server Settings > Logging. Under Scheduler Log Path, assign a folder path where the logs will be written this will give you a clearer view of what's happening with the scheduler.

Best regards,