Not the usual VSS SYSTEM FILESET error

These writers give errors:

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {e10fb4a9-9a7b-42d6-8351-7b1ed8335041}
   State: [7] Failed
   Last error: Non-retryable error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {fba54c1c-3be6-443d-b11b-c942ab91687a}
   State: [7] Failed
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {acdaccea-2cdb-4a3d-b49a-2635d9908075}
   State: [7] Failed
   Last error: No error

when the backup is started this error comes in application log on the client:

Log Name:      Application
Source:        Microsoft-Windows-CAPI2
Date:          6.7.2011 12:17:42
Event ID:      513
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      servername.domain.not
Description:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:
AddCoreCsiFiles : BeginFileEnumeration() failed.

System Error:
Access is denied.
.
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">
 
   
    513
    0
    2
    0
    0
    0x80000000000000
   
    50659
   
   
    Application
    TYRI.vordur.root
   
 
 
   

Details:
AddCoreCsiFiles : BeginFileEnumeration() failed.

System Error:
Access is denied.

 

Becuase it says access denied, do you run service as local system account or something else?  It's obviously an error for Windows admins to figure out, but are you aware of anything different for this box when compared to the others?

The install of the client is using the same script as any other client in the datazone.

And no, the NetWorker service is not running as a user, it's running as system. Nothing about the networker client has been customized.

joka wrote: The install of the client is using the same script as any other client in the datazone.

Script?

Can you try to re-register VSS dlls on that box?

yes, it's just a bat file that executes setup with silent parameter. We have never had any problem with it.

How can I re-register the VSS dll's?

Check this: http://www.gfi.com/blog/vss-troubleshooting/

joka wrote: How can I re-register the VSS dll's?

Check the link above by unexpected.  I assume same dlls are at least used with win2k8 (but this might need so verification).  In short:

- stop vss service

- go to system32

regsvr32 ole32.dll
regsvr32 vss_ps.dll
vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32  msxml3.dll
regsvr32 msxml4.dll

- start vss service

Hi Joka,

Can you please check the output of the following command?:

vssadmin list writers

The error message you provided looks to me as if the System Writer is not working correctly, which should be fixed re-registering the VSS dll's, as Hrove suggested, although some times it can be a permissions issue and in that case you should re-apply the correct permissions as described below (Please note that this is a suggestion; Microsoft should be engaged for these kind of issues if there is any writer missing):

Takeown /f %windir%\winsxs\filemaps /a

icacls %windir%\winsxs\filemaps  /grant "NT AUTHORITY\SYSTEM:(RX)"

icacls %windir%\winsxs\filemaps  /grant "NT Service\trustedinstaller:(F)"

icacls %windir%\winsxs\filemaps  /grant "BUILTIN\Users:(RX)"

icacls %windir%\winsxs\filemaps  /grant "Administratoren:(RX)"

Takeown /f %windir%\winsxs\filemaps\* /a

icacls %windir%\winsxs\filemaps\*.*  /grant "NT AUTHORITY\SYSTEM:(RX)"

icacls %windir%\winsxs\filemaps\*.*  /grant "NT Service\trustedinstaller:(F)"

icacls %windir%\winsxs\filemaps\*.*  /grant "BUILTIN\Users:(RX)"

icacls %windir%\winsxs\filemaps\*.*  /grant "Administrators:(RX)"

Takeown /f %windir%\winsxs\temp\PendingRenames /a

icacls %windir%\winsxs\temp\PendingRenames  /grant "Administrators:(RX)"

icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"

icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"

icacls %windir%\winsxs\temp\PendingRenames /grant "BUILTIN\Users:(RX)"

Takeown /f %windir%\winsxs\temp\PendingRenames\*.* /a

icacls %windir%\winsxs\temp\PendingRenames\*.*  /grant "Administrators:(RX)"

icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"

icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "NT Service\trustedinstaller:(F)"

icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "BUILTIN\Users:(RX)"

Thank you.

Carlos.

Interesting enough, I have seen this issue today on 2 boxes (different countries, different datazones).  One common thing is that both were win2k3 machines and on one at least I could see System Writer missing from the list of the vssadmin list writers.  Further, reboot didn't make it reappear.  On that box starting crypto service made it reappear. On second box, by the time I logged I could not see this and backup worked fine after - event log doesn't show anything related between time of failure and second re-run. Not sure why this happened, but I'm sure that at the time when this happens vssadmin list writers would show no System Writer (though I could not confirm that in second case).

Hi Hrvoje,

It would take some time for me to write down the explanation , but I'm sure you will be happy by reading this:

Missing System Writer Case Explained - Ntdebugging Blog - Site Home - MSDN Blogs

Thank you,

Carlos

Thanks Carlos.  I believe article mostly reflects win2k8 (and win2k12) world while I have observed this on win2k3, but I might use some of the steps in troubleshooting too if they will be applicable to win2k3 (this morning I could not see the issue any longer).