NTFS Event 134 with Windows Server 2008 R2 SP1 Domain Controller


server windows standard edition 2008 r2 w/sp1 , critical updates date.   have symantec endpoint protection client v12.1 ru1 installed, ant-virus part.   machine domain controller , hosts fsmo roles.


there was issue 12.1 ru1 running on domain controller , windows backup told install 12.1 ru2.   did started receive capi2 errors opened ticket symantec.   symantec said capi2 errors result of corrupt installation of sep , should run repair.   tried run repair , failed sep still functioning.   @ point started getting ntfs events listed below.   symantec said reboot , rerun repair, did , solved capi2 errors not ntfs event following in system event log:


ntfs event 134


transaction resource manager on volume \device\harddiskvolumeshadowcopy20 encountered error during recovery.  resource manager continue recovery.


number of shadow copy changes each time.   vss writers stable , ok.   existing forum posts talk corruptions none of them talk 134 events similiar ones.   ran chkdsk on volume , there nothing repair.  volume raid1.  time error occurs when related vss kicked off.


help/suggestions great.   paying support last on solution list.


in advance!


- richard skurnick

  system administrator                                                        

i getting error. setup similar yours, except i'm not using symantec endpoint protection, symantec backup exec remote , exchange agents (backup exec 10.1 r3 patched). server running exchange 2010 sp3, opposed yours being dc.

my machine running windows standard edition 2008 r2 w/sp1 updates installed through 4/10. vss writers show no errors.

the error occurs whenever our backup exec jobs begin backing server.

have been able track else down error since initial post?



Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file