We use the UrBackup client on a server, the server is Windows Server 2016 Version 1607.
This is a second instance of this happening on this server, I got a call from one of our members of staff today that their accounts software was failing to load as it was waiting for a lock to be released on a file (REMITIDX.DTA), when attempting to move the file Windows told me it could complete the operation because “the file is open in UrBackup Client Service for Backups”.
Edit: Forgot to state that the status of the backup was on the client side was “Idle.”
I stopped the Service under Services and exited the program from the Icon Tray, the service was showing as stopped.
The file was still locked however, and there was still a process called “UrBackupClientBackend.exe” running, although Windows was saying the service was stopped. After waiting 5 minutes the process was still active and the file still locked.
Trying to terminate the process from Task Manage returned “Access is Denied”, Trying to kill the process from taskkill returned “Process could not be terminated, There is no running instance of the task”
after another 10 minutes the process was still running, we had to force a restart of the server in order to release the file lock, before restarting the server I checked and the process was still running.
Does anyone know of any issues that may have caused this? it isn’t happening on any of our other servers.
Sorry the debug log is empty, its only occurred twice but with the same directory. I do have a memory dump of the process before the restart if that would help?, I’ll enable debug logging and attach the file if it reoccurs
If the server isn’t running on Hyper-V, please uninstall the Hyper-V integration – or make sure it is up to date. You’ll find more info if you google for Hyper-V IC Software Shadow Copy Provider. Backing up via snapshot should take care of the “file is locked” problems.
Unfortunately I could not open the memory dump. Did you make it like this? https://kb.sitecore.net/articles/758511 Assuming it is not a bug, a lingering connection could cause it, for example (it has a 1h timeout at places).