Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win 2003 AD system log error after DST fix 1

Status
Not open for further replies.

davess10

MIS
Mar 5, 2007
1
US
Hello,

We are using Windows 2003 Active Directory with 2 Domain controllers for more than two years. For the past two years, whenever we did the DCDIAG or NETDIAG test, both domain controllers passed with no errors.

After we applied the Microsoft patches this weekend for the DST, the Domain controller(DC01 - which is our main Domain controller) that we applied the patches to first has failed the DCDIAG test on systemlog with event-ID 0x00000457. The other Domain Controller (02) passed the DCDIAG test, and both of them passed the NETDIAG and REPADMIN test.

Here is the configuration for the domain controllers, hot fixes that have been applied to the system, and the error message.

Domain Controller:
HQADDC01 – with Schema master, Domain naming master, RID master, PDC Emulator, and Global Catalogs.
HQADDC01 – Global Catalogs and Infrastructure master.

Applied patches to HQADDC01 first and error message on Dcdiag:
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 03/05/2007 17:18:46
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/05/2007 17:18:46
(Event String could not be retrieved)
......................... HQADDC01 failed test systemlog

Patches applied to the server:
KB893756
KB896358
KB896424
KB896428
KB898715
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB904706
KB905414
KB908519
KB908531
KB910437
KB911280
KB911562
KB911564
KB911897
KB911927
KB912919
KB914388
KB914389
KB917344
KB917422
KB917734
KB917953
KB918118
KB918439
KB920213
KB920670
KB920683
KB920685
KB921883
KB922582
KB922819
KB923191
KB923414
KB923689
KB923694
KB923980
KB924191
KB924496
KB924667
KB925398_WMP64
KB926247
KB926436
KB928090
KB928255
KB928843
KB929969
KB931836
Q147222

Any ideas what may be causing this error and what we can do to fix it? If I've left out any information please let me know.

Thanks!

David
 
The failed dcdiag is only because you have an event in your event log. If you cleared the event, it would pass. As for the event, its hard to tell if the event is pretty much blank. Have you applied it to your clients yet? MS says the order is supposed to be DC/Servers and then clients.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top