Upgrade from 2023.2.11 to 2023.3.13 failed with access denied

Hello Lars,

This usually occurs when the file is locked, for example if multiple users are logged to the machine. Simply rebooting the server should fix the issue.

As for your question, the console will use the context of your user, unless you did a run as when opening the console.

Best regards,

I tried to reboot the server and made sure I was the only one logged in. I alto tried to exclude the C:\inetpub\wwwroot\dvls folder from Defender. Still god the same error.
I also checked the Resource Monitor/Disk Activity. Nothing seem to be reading the Devolutions.dll.
Just to check my Access and if the file was locked I tried to rename the Devolutions.dll. That worked fine. So I'm not sure the error is caused by someone using the file.

Anything else I can try?

Hello,

You can try the following:

• Verify that the Devolutions Scheduler service (services.msc) is stopped - most common issue
• If it was stopped already, close IIS in an elevated cmd with - iisreset /stop
• If the upgrade still fails, verify what is locking the file with https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Please note that if you did the second step, you will need to do an issreset /start after the upgrade.

Best regards,

I made a clone of the server to be able to troubleshoot. I tried all your suggestions, changes rights, excluded processes and folders from the Antivirus. I think I finally found the solution. Going to update the production server during the weekend.

Is seems that if the Scheduler server was started once, you can forget all about updating. Even stopping the service did not help.

The solution was :

• Set scheduler service to "manual".
• Reboot the server.
• Start the upgrade job.
• Change Scheduler server back to "Auto"

@larsbjerringjensen: Thanks for the tip. Just ran into the same issue trying to upgrade from 2024.2.6.0 to 2024.2.8.0. None of the suggestions worked except for yours.

Tried the following:
- Give allow all permissions to dll (didn't work, so in use)
- Stop IIS website (didn't work)
- Stop DVLS server (didn't work)
- Stop DVLS scheduler (didn't work)
- Reboot (didn't work)
- Set DVLS scheduler to manual + reboot = magic fix (probably in combination with some of the above steps but still, this was needed)

Hello,

Thank you for bringing us that information to our attention. We will try to see why you got that issue. We will try to reproduce and keep you posted if we can find something. Meanwhile, I'm glad to know that you have a workaround, but will try to figure out why you have this issue.

Best regards,

Could also just be something on our end to be honest. Our servers do have some hardening and generally run several agents/tools (Rapid7, SentinelOne, Guardicore) that could interfere.

Just glad I bumped into this thread because it was a bit of a head-scratcher. ;-)

Hello,

Our QA tried to reproduce without success. When you have the issue, maybe you could try to figure out who is locking the file by using Handle available here : https://learn.microsoft.com/en-ca/sysinternals/downloads/handle Let me know if that could help.

Best regards

Had the same issue so glad I found this. For me the locked file was "azure.core.dll" or "derconverter.dll". Handle.exe showed the scheduler service account had the file locked despite being stopped. Mathieu's solution worked for me.