I have this microsoft volume shadow copy service error that pops out when I RDP to my exchange server. I need to click Don't Send button multipe times before the dialog box disappears. How do i remove this error message permanently ?

Unfortunately, these screenshots are quite generic in nature and don't tell us much about your particular error. Are you able to take a look at the Application and System event logs and look for VSS-related errors there? If you find something in either of these locations, that would be the kind of information you can share here with the community and get feedback on. There is one other command you can run from an elevated command prompt, the output for which could also be posted here: vssadmin list writers This will inform you if one of the writers is still experiencing an issue, but again, the event logs will capture historic events that vssadmin might not allude to. Cheers, Lain

this is the VSS errors from the application logs

Okay, that's more meaningful. Could you post the output from the following two commands as well? vssadmin list volumes vssadmin list shadows You might want to remove your server details from the output of the second command (or change them to bogus ones - using Notepad is a quick way to do this before posting). On the surface of things, it looks like either a corrupt shadow copy or a volume is legitimately missing at times - even if it's sporadic in nature. Cheers, Lain

i m getting error for the 2nd command Error: Unexpected failure: The remote procedure call failed. C:\>vssadmin list volumes vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Volume path: C:\ Volume name: \\?\Volume{7876bb41-879b-11dc-be68-806e6f6e6963}\ Volume path: D:\ Volume name: \\?\Volume{c284d57a-875b-11dc-bb9c-001cc49703f6}\ Volume path: E:\ Volume name: \\?\Volume{f8fe06f2-28af-45f3-859d-abb4d15206e1}\ Volume path: F:\ Volume name: \\?\Volume{03e92519-03dd-473f-a517-b7024ead1181}\ Volume path: H:\ Volume name: \\?\Volume{6eac18e5-4c66-444a-84aa-c21051d43e53}\ C:\>vssadmin list shadows vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Error: Unexpected failure: The remote procedure call failed. C:\>

Okay, that's interesting. Perhaps just to check the obvious, is the "Remote Procedure Call (RPC)" service started? Cheers, Lain

RPC is started but RPC locator is not started

So long as we're dealing with Server 2008 and later, then you don't need to worry about the RPC Locator, so that's all good. The next command checks the system's permissions on the "System Volume Information" directory. Check when you run it that you get the following output. Command: icacls "%systemdrive%\System Volume Information" Expected output: NT AUTHORITY\SYSTEM:(OI)(CI)(F) Cheers, Lain

we are using windows 2003 enterprise, not windows 2008. i m getting the following for icacls C:\>icacls %systemdrive%\System Volume Information Invalid parameter "Volume" C:\>icacls "%systemdrive%\System Volume Information" C:\System Volume Information: Access is denied. Successfully processed 0 files; Failed processing 1 files

I've forgotten more than I remember with Server 2003, but so long as the Locator is set to manual that should be fine. The system starts it when requested. The icacls result is a little concerning through as you should have at least been able to produce a result from the top level directory (though you wouldn't be able to see the structure within). First, check that the Volume Shadow Copy service is running under the local system account - it should be, but it's still worth checking. Secondly, take ownership of the System Volume Information folder and then reapply the "NT AUTHORITY\SYSTEM" permissions with the following two commands: takeown /a /r /f "%systemdrive%\System Volume Information" icacls "%systemdrive%\System Volume Information" /t /c /grant "NT AUTHORITY\SYSTEM:(OI)(CI)(F)" Make sure you include the double quotes as they're required when directory names contain spaces (as demonstrated by your output above). Each of those commands is one line, by the way. Be wary of word wrapping in these forum posts. Keep an eye out for errors. If you're familiar with piping output to a file, then you might want to do that, though there shouldn't be a lot of content below this directory anyway. Cheers, Lain

I should have pointed out that after running the takeown and icacls you will want to re-run the same "vssadmin list shadows" command from earlier. If the problem was indeed permissions-based, then the above two commands ought to have fixed the issue. Going right back to the start, the number of windows you would have had to click through most likely correlates to how many Windows backups had been attempted, as they appear to be failing. Cheers, Lain

Hello, The quesiton is more related to a Windows Server issue, please also post a new thread to our Windows Forum via: http://social.technet.microsoft.com/Forums/en/category/windowsserver/ Thanks, Simon

Hello, The quesiton is more related to a Windows Server issue, please also post a new thread to our Windows Forum via: http://social.technet.microsoft.com/Forums/en/category/windowsserver/ Thanks, Simon