+ 0 Votes Not really Tony Hopkinson 3 years ago It's just saying you can't do a back up with VSS. If it's just your databases you want to make sure of back them up with sql server. If you want the entire machine. Stop sqlservers services and image it with something else. Then you can apply the hotfix , knowing you can get back to now (given you've proved you can restore the backups !) Given the problem description, you could also drop your user databases recovery mode down to simple. VSS it, hotfix it, then reset the recovery modes and try VSS again to see if it worked and have a 'good' VSS backup. HtHs + 0 Votes changed to local system Jacques.Gordon 3 years ago I changed MSSQLSERVER and SQLSERVERAGENT to local system and did a check with replmon and dcdiag /a and the AD DB on that server is reported to be perferctly up to date. I also moved the servers to a completely unmanaged switch. But all to no avail, I still get exactly the same error. I ran a filter on my event logs for sqlserver but all the event logs were info logs about internal sql stuff. + 0 Votes Something else to try... MikeBlane 3 years ago See http://support.microsoft.com/kb/912414. Your server may not be able to verify the credentials of the username created for SQL Server. The questions that I have are: - What configurations or parameters were recently changed on this server? - Can the server ping the domain controller consistently? - Has a new managed switch been put into place between this server and the domain controller? - When you created the SQLSVR account, did you set the password to not expire? Try changing the user account to "LocalSystem" in the services "Logon" tab to see if the service starts operating correctly.