Unsolved
This post is more than 5 years old
9 Posts
0
5740
unable to take system state and ASR backup
HI all,
I have a Windows 2003 client that seems to be having problems doing a VSS
ASR: and VSS SYSTEM BOOT: backup.
* VSS SYSTEM BOOT:\ 1 retry attempted
* VSS SYSTEM BOOT:\ AsrCreateStateFile failed - 0x1
* :VSS SYSTEM BOOT:\ Failed to create the ASR state files
* :VSS SYSTEM BOOT:\ ASR System Files - Error saving writer ASR
System Files
* VSS SYSTEM BOOT:\ ASR System Files - ERROR: Aborting backup
of saveset VSS SYSTEM BOOT: because of the error with writer ASR System
Files.
* VSS SYSTEM BOOT:\ ASR System Files - Error saving
* VSS SYSTEM BOOT:\ 39078:save: RPC error: RPC cannot encode
arguments
* VSS SYSTEM BOOT:\
VSSADMIN LIST WRITERS shows all writers in a stable state. The VSS rollup
has been applied. No errors show in event log. The EMC error guides say to
recreate the %systemroot%\repair\nsr directory. I don't have that
directory - on any client, including ones that this is working on.
Creating one did nothing to resolve this issue.Permissions on
%systemroot%\repair are the same as they are on clients that are working.
Plenty of space on both client and server.
CarlosRojas
1.7K Posts
0
May 10th, 2012 04:00
Hi Sandeep,
Thah failure could be caoused for many different reasons.
Some points to check:
Always for VSS related issues look through Application and system event logs, you will definitely find more information in there.
Also try to set some debug options and run save manually from the client using save command and only for that failed saveset.
Also take a look at the following KB, it could help you:
https://solutions.emc.com/emcsolutionview.asp?id=esg102399
This could be also a problem related to some MS update, after some patch or update applied, there is a chance that the permissions for VSS are changed and in that case you will need to reapply those permissions but, as that is a bit intrusive let's first see the outcome of the KB
Thank you.
Carlos.
Bebo2k
544 Posts
0
May 11th, 2012 18:00
Hi Sandeep Kumar,
Please check the following fix from Microsoft, implement it firstly and re-check the backup status:
http://support.microsoft.com/kb/940349
Otherwise if the problem still occuring, Check the following steps to re-register the VSS dlls on that machine:
http://support.microsoft.com/kb/940032
Waiting your updates.
Thanks,
Ahmed Bahaa