CAPI2 - 513 : Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Created: 14 Jul 2010 | 3 comments
Hi,
I am running BE12.5 SP4 on a W2003 Server to backup a W2008 file server. On that W2008 file server I got a multiple error in Windows application log:
CAPI2 - 513 : Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
I have checked Symantec doc id 327192 (http://seer.entsupport.symantec.com/docs/327192.htm), but all security settings are ok and the SystemWriter *is shown* in vssadmin and the buckup job does not fail.
Anyone any idea how to fix that?
Cheers
Dirk
Discussion Filed Under:
Comments 3 Comments • Jump to latest comment
Try the following a) and/or b) solution(s). If none of the solutions can solve the issue, please contact Microsoft support for further assistance about why System Writer is missing.
a) Refer to http://technet.microsoft.com/en-us/library/cc734021(WS.10).aspx and make appropriate changes to access control list on the %systemdrive%\Windows\registration folder if the situation matches the document.
b) Try to list permissions for the files in %windir%\winsxs\filemaps from a command prompt run as administrator. If access was denied to every file, run the following sequence of commands to reset the permissions and restore the state of System Writer:
cd c:\windows\system32
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)"
If this response answers your concern, please mark it as a "solution"
H RahulG,
like I wrote in my post:
- I have allreday done all theses steps
- System writer IS PRESENT, (is NOT missing)
Nevertheless I get this error: CAPI2 - 513 : Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
cheers
Dirk
Hi all
As well as the information Rahul G posted there is another Microsoft Article with a few more commands in it that should perhaps be reviewed against this issue:
http://support.microsoft.com/kb/2009272
Would you like to reply?
Login or Register to post your comment.