Remote Desktop Services could not disconnect a user disk for the user account with a SID of <SID>. The error code is 0x80070005.0

Users are complaining about blank desktops when they log on.
There are no policy's configured for automatic log off, ...
Users disconnect their session when they go home and leave everything open. When they log on again the day after they get a blank desktop and start menu. The only solution is to log off and log on again.

They only error related to this event I can found in the log is this one:
Log Name:      Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin
Source:        Microsoft-Windows-TerminalServices-RemoteConnectionManager
Date:          15/01/2015 9:51:47
Event ID:      20491
Task Category: None
Level:         Error
User:          SYSTEM
Computer:      WOUSRD01.woutersfruit.local
Remote Desktop Services could not disconnect a user disk for the user account with a SID of S-1-5-21-2734725699-4262487074-1331432658-1140. The error code is 0x80070005.0

We are using profile disks stored on the file server.
All servers are running Server 2012 (NOT R2 unfortunately)
We have one physical server running ESXi

I can't seem to find any solution and hope to find it here.
Who is Participating?
FlipTripConnect With a Mentor Author Commented:
I have advised them to log off before going home. I'll post back here when I get some feedback from my customer.

This could happen due to a backup application running at night fiddling with the user profile, system restore is another culprit of this, as is AVG (use MSE instead).

Another reason could be another form of connectivity loss at the network level.
FlipTripAuthor Commented:
We have Veeam backup running.
vhdx (UPD are stored on our file server) and offcourse stay mounted on the RDS server.

So what can I do to prevent this?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

So what can I do to prevent this?

Force logoff the open sessions before Veeam starts running is worth the try/experiment I'd say. Even if you do it for just one day like that you'll be able to determine for sure if Veeam is the cause of the issue.
Hi Flip,

So did you look at the other possible causes I listed? Backup software was only one of the possible causes. Bottomline is that 0x80070005.0 equals a sharing violation (in use) or an access denied.

With regards to access denied, does the system user have full control on the user profile directories and files? Cross check the rights on the profile directory; 

With regards to the sharing violation (in use) you'll need to evaluate applications accessing the folders at said time.

If you are going to rely on users logging off themselves, then start enforcing that by logging off disconnected sessions. If you don't you'll still end up encountering the issue every once in a while due to the nature of users.
FlipTripAuthor Commented:
It wasn't caused by the backup.
Users are now logging off before going home.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.