Hello everyone,
We are excited to release the beta version of Devolutions Server 2023.1.0. Please make a backup before performing the upgrade, and we strongly recommend you install it in a test environment first.
Console download(.exe):
https://cdn.devolutions.net/download/Setup.DVLS.Console.2023.1.0.0.exe
Offline package (.zip):
https://cdn.devolutions.net/download/RDMS/DVLS.2023.1.0.0.zip
Upgrade procedure: https://helpserver.devolutions.net/upgrade_rdms.html
The 2023.1.1 Gateway is also available from the console.
Database upgrade required
DVLS Console 2023.1 is required
RDM 2023.1 is required if you use RDM: https://forum.devolutions.net/topics/38980/remote-desktop-manager-20231--beta
NEW FEATURES
IMPROVEMENTS
FIXES
####
Console Release Notes
NEW FEATURES
IMPROVEMENTS
FIXES
Richard Boisvert
Attempted to install DVLS 2023.1.0.0 but am unable to access the DVLS site after the update. Site gives a "HTTP Error 500.37 - ASP.NET Core app failed to start within startup time limit" error. DVLS Console says everything is running and No errors in the DVLS logs or IIS logs.
Hello Stephen,
Was this a brand-new installation or an upgrade from an existing version? If it is the latter, what version was it previously? Could you also confirm what type of authentication are prefestn (O365/Microsoft, AD, Okta)?
Could you also try the following: https://kb.devolutions.net/http-error-500_30.html - just change the valut to 500 seconds instead.
Best regards,
Richard Boisvert
This was an upgrade from 2022.3.13.0. After following the steps to increase timeout to 500 we seem to be good. However I am seeing this error appear in the DVLS console error logsSchedulerId is empty. Please restart the scheduler with a Console 2023.1.0.0 or greater.
Hello Stephen,
Glad increasing the startup time fixed the issue, there is a migration that is performed in the inital launch of the Devolutions Server after the upgrade.
For the error, could you go to the web interface, under the (new!) System Dashboard, does it report that the scheduler is installed?
After restarting the scheduler from the console, do you still have the error?
Best regards,
Richard Boisvert
The new system Dashboard shows the schedule of being down. Reinstalling or stop\starting the scheduler just causes another down notification.
The console does show that the scheduler is running though.
Hello Stephen,
The engineering team is currently looking at the System dashboard and the Scheduler service, there seems to be an issue with it. The error you received is most likely related as well.
For now, you can ignore that issue, it should still perform normally, but thank you for reporting it!
Best regards,
Richard Boisvert