System State Backup Error

Your account that ahs started nsrexecd service does not have enough permissions.

Run the nsrexecd service under the administrator account.

Regards,
Anuj

Thanks.. But i have ran the service under the administartor account. It's still the same error. Could it be the open file/vss error?

I think we are not using VSS/OFM.

Does not seem to be. This seems more to be an issue where the nsrexecd service is not able to read the registry properly or perhaps the registry is corrupt.
Are you isng OFM/VSS?

Have you checked KB? There are few articles that might apply to you:
http://softwaresupport.emc.com/support/resolutions/dmfrmresolutionview.asp?id=69518
http://softwaresupport.emc.com/support/resolutions/dmfrmresolutionview.asp?id=66717

Permissions is something else to check, but as you said you did check that so I assume that should not be an issue then. Try it with NT backup and if it fails too talk to MS. You may also wish to apply latest set of patches and see if that changes anything. If not run backup in debug mode from client and if still without clue opet this with support - they should run analysis against debug output and pinpoint where the problem is.

Thank you so much for the info. I will check on it..

Had the same issue, support sent me this solution:

Disable one of the VSS provider service. Following are steps to disable OFM VSS provider service (Note, disabling this service does not reduce the functionality of OFM):

1) In SERVICES applet, right-click on the Open File Manager - VSS Provider Service and choose "Properties" from the pop-up menu.
2) Select the "Log On" tab in the Properties Dialog.
3) Click on the "Disable" button to disable the Open File Manager - VSS Provider Service in the active Profile (PROFILE1 by default).
4) Restart the Server.

And also add the following to your OFM ignore list:

*:\$Extend\$Quota\* recursive subdir=No
%SystemDrive%\Documents and Settings\ \Local
Settting\* recursive subdir=Yes
%SystemDrive%\DOCUME~1\UUUUUU~1\Local~1\* recursive subdir=Yes

I'm still waiting a window to boot the machines and see how things go.

Daniel, what you say makes sense if you use OFM, but according to Meng he is not using it.

Ops, I did not read that..

Meng, forget that...

I have been having the similar error message. I found rebooting the Server fixed it, but then it would return after a short peroid of time. All the Servers I am having problems with were Win2K3 SP1, my Win2K servers were fine.

I have since found out that it is a memory leak in Win2K3 and it is fixed by a Microsoft Hotfix. See the following Microsoft KB

http://support.microsoft.com/kb/909424/en-us

Hope this helps