Question : System Writer Dissappeared

I'm using Backup Exec 12.5 on SBS 2008 to backup a server remotely. This doesn't use the AOFO at the moment. The remote server environment is a TS with 2008 R2 bit.

I believe the source if this issue is that the System Writer doesn't appear when using VSSadmin List writers.

A Capi2 error is also produced:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:
AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed.

System Error:
0xC0000039 (unresolvable).

I've included the fix I've applied with no avail. I've also uninstalled and reinstalled BE.

I've tried many variations of the included script. I've lodge a PSS case with Microsoft and Symantec. I've installed and remove then re-installed Backup Exec Remote agent. Below is the error I get from Backup Exec:

Backup- TS.Client.com.auV-79-57344-65225 - A failure occurred accessing the Writer metadata.

And further down:
AOFO: Started for resource: "\\TS.Client.au\E:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot provider used by VSS for volume E: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between [FE80::168B:ADB4:2494:6459%11]:20753 <--> [FE80::2D5E:8B0:A081:EC46%11]:10000
Network data connection is established between [FE80::168B:ADB4:2494:6459%11]:20758 <--> [FE80::2D5E:8B0:A081:EC46]:51086
V-79-57344-65225 - A failure occurred accessing the Writer metadata.

Code Snippet:

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:

           
           
             net stop "System Event Notification Service"
net stop "Background Intelligent Transfer Service"
net stop "COM+ Event System"
net stop "Microsoft Software Shadow Copy Provider "
net stop "Volume Shadow Copy"
cd /d c:\windows\system32 
net stop vss 
net stop swprv 
regsvr32 /s ATL.DLL
regsvr32 /s comsvcs.DLL
regsvr32 /s credui.DLL
regsvr32 /s CRYPTNET.DLL
regsvr32 /s CRYPTUI.DLL
regsvr32 /s dhcpqec.DLL
regsvr32 /s dssenh.DLL
regsvr32 /s eapqec.DLL
regsvr32 /s esscli.DLL
regsvr32 /s FastProx.DLL
regsvr32 /s FirewallAPI.DLL
regsvr32 /s kmsvc.DLL
regsvr32 /s lsmproxy.DLL
regsvr32 /s MSCTF.DLL
regsvr32 /s msi.DLL
regsvr32 /s msxml3.DLL
regsvr32 /s ncprov.DLL
regsvr32 /s ole32.DLL
regsvr32 /s OLEACC.DLL
regsvr32 /s OLEAUT32.DLL
regsvr32 /s PROPSYS.DLL
regsvr32 /s QAgent.DLL
regsvr32 /s qagentrt.DLL
regsvr32 /s QUtil.DLL
regsvr32 /s raschap.DLL
regsvr32 /s RASQEC.DLL
regsvr32 /s rastls.DLL
regsvr32 /s repdrvfs.DLL
regsvr32 /s RPCRT4.DLL
regsvr32 /s rsaenh.DLL
regsvr32 /s SHELL32.DLL
regsvr32 /s shsvcs.DLL
regsvr32 /s /i swprv.DLL
regsvr32 /s tschannel.DLL
regsvr32 /s USERENV.DLL
regsvr32 /s vss_ps.DLL
regsvr32 /s wbemcons.DLL
regsvr32 /s wbemcore.DLL
regsvr32 /s wbemess.DLL
regsvr32 /s wbemsvc.DLL
regsvr32 /s WINHTTP.DLL
regsvr32 /s WINTRUST.DLL
regsvr32 /s wmiprvsd.DLL
regsvr32 /s wmisvc.DLL
regsvr32 /s wmiutils.DLL
regsvr32 /s wuaueng.DLL
sfc /SCANFILE=c:\windows\system32\catsrv.DLL
sfc /SCANFILE=c:\windows\system32\catsrvut.DLL
sfc /SCANFILE=c:\windows\system32\CLBCatQ.DLL
net start "COM+ Event System"


Takeown /f c:\windows\winsxs\filemaps\* /a
icacls c:\windows\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls c:\windows\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls c:\windows\winsxs\filemaps\*.* /grant "BUILTIN\Users: (RX)"
icacls c:\windows\winsxs\filemaps\*.* /grant "NT SERVICE\TrustedInstaller:(OI)(CI)(F)" "BUILTIN\Administrators:(OI)(CI)(RX)" "NT AUTHORITY\SYSTEM:(OI)(CI)(RX)" "BUILTIN\Users:(OI)(CI)(RX)"

net start SENS
net start BITS
net start EventSystem
net start swprv
net start VSS

           
         

Open in New Window

Select All

Answer : System Writer Dissappeared

To be honest, what with the specific OS type of SBS 2008, I would never have re-registered all those DLL's. Microsoft do not seem to support this repair method on Vista, 2008 or higher in any case.
Not any help I know - but the best bet really is Microsoft looking into it via PSS - unless someone else has an idea that won't affect the functionality of SBS.