Backup Exec, Shadow Copy, DFSR, system state

"Could the problem on one of this server affect the system state backup on the other one?" - Generally speaking, no.  Normally when I see an issue like this there was a change to both servers at roughly the same time that caused the problem.

Hello,

Reregistering the some of the DLL's sometimes does resolves the issue please follow the symantec Document ID: 312068
http://support.veritas.com/docs/312068 or microsoft article http://support.microsoft.com/kb/940032 and reregister the DLL's

To resolve this problem, follow these steps:

Click Start, click Run, type Regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
Exit Registry Editor.
Click Start, click Run, type services.msc, and then click OK.
Right-click the following services one at a time. For each service, click Restart:
COM+ Event System
COM+ System Application
Microsoft Software Shadow Copy Provider
Volume Shadow Copy
Click Start, click Run, type cmd, and then click OK.
At the command prompt, type vssadmin list writers, and then press ENTER.
If the VSS writers are now listed, close the Command Prompt window. You do not have to complete the remaining steps.

If the VSS writers are not listed, type the following commands at the command prompt. Press ENTER after each command.
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 /i eventcls.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
Note The last command may not run successfully.
At the command prompt, type vssadmin list writers, and then press ENTER.
Confirm that the VSS writers are now listed.

We allready went trough this. Case open with Microsoft and the first guy told us he doesn't know what to do anymore. Hes trying to escelate the case.
It's not jsut that the system writer is missing. I get an eventlog entry from CAPI2 that says somewhere in it: "access denies" and there are files inside windows\winsxs\filemaps which have wrong NTFS settings. I can correct them manually. System writer is back error messages dissapears. Till nex Windows Update and the error comes back in an other form (but again missing the system writer) or in the same form (exatly same error in event viewer, same file with wrong NTFS settings).

I just opened this thread cause the server with this error is a NBL-Cluster Member with a Web DFS and it looks like backup up the other servers (cluster member) gives us problems too.
We are loosing the connecting to them while making a backup. But I can't find any Problems, error messages or anything leading me to somwhere on the other member servers.
So I was wondering if that error (missing system writer, wrong NTFS right in Windows Folders) could somehow cause the error (V-79-57344-65072 0xe000fe30) on the other member server.

On the other hand there would be the possibility, that we are missing some special configuration that's needed inside backup exec for clustered systems. This is actually the first time we are trying to backup clustered servers.

As a side note the dll registration for vssadmin list writer problems are not the same on windows Server 2003 and 2008. I once tried MS KBs regarding such problems on 2003 servers cause I couldn't find anything for 2008. Caused quit some error messages. For 2008 I got an email from Microsoft telling me to do the following:

net stop SENS
net stop bits
net stop Event System
net stop vss
net stop swprv
cd /d %windir%\system32
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 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=%windir%\system32\catsrv.DLL
sfc /SCANFILE=%windir%\system32\catsrvut.DLL
sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL
net start Event System
Reboot Server

Also deleting that registry didn't look like a good idea on 2008. Also gave some errors back and didn't get rebuilt. I imported the backup I made of that tree again ^^'

Install Sp2 for windows 2008

SP2 is installed.
Again: This is not really about that problem. We are looking with Microsoft into that. We have a Case open with Microsoft for that System. If it would be that easy to solve it would be over long ago ;)
The Problem I'm asking about is the connection loss we have on the other systems which are NLB-cluster Members with that server.
I can't seem to find an error there. So I'm wondering if this could be connected (witch the System-Writer error on the other member server) adn I should wait with further analysis of this connection problems, or for what else should I look there. Cause I can't seem to find anything that causes this connection problems. And again, we never before had clustered systems. So it could also be a generall configuration problem. Is there anything special to configure in backup exec for clustered systems?

This is wierd. I just found an other system that doesn't give back the system writer if I use vssadmin list writers. But Backup Exec doesn't complain about that system. It tells us everything is fine. How's that possible?
Windows internal backup software fails cause of this. So how come Backup Exec tells us every thing is fine? This will be quit a pain in the ass to check all the systems.
Any way to check if the system state is backed up? Would it be possible that the AD-Agent somehow takes the system state cause it is a DC?