Active Directory Event Errors

[stopfd]

I am getting some odd errors on two Domain Controllers in our environment of ten DC's, these are logged in EventViewer as 1311 and 1265 errors. There are a number of MS Technet articles and also a MS patch that I have applied, the errors still occur though. DNS is configured as AD Integrated.

I have submitted the results of DCDIAG on one of the troubled DC's.

Has anyone experienced anything similar?

-------------------------------------------
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: SITE1\SERVER1
Starting test: Connectivity
......................... SERVER1 passed test Connectivity

Doing primary tests

Testing server: SITE1\SERVER1
Starting test: Replications
......................... SERVER1 passed test Replications
Starting test: NCSecDesc
......................... SERVER1 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER1 passed test NetLogons
Starting test: Advertising
......................... SERVER1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER1 passed test RidManager
Starting test: MachineAccount
......................... SERVER1 passed test MachineAccount
Starting test: Services
......................... SERVER1 passed test Services
Starting test: ObjectsReplicated
......................... SERVER1 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... SERVER1 passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 01/05/2004 10:23:27
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 01/05/2004 10:23:27
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 01/05/2004 10:23:27
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 01/05/2004 10:23:27
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 01/05/2004 10:23:50
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 01/05/2004 10:24:13
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 01/05/2004 10:24:36
(Event String could not be retrieved)
......................... SERVER1 failed test kccevent
Starting test: systemlog
......................... SERVER1 passed test systemlog

Running enterprise tests on : DOMAIN
Starting test: Intersite
......................... DOMAIN passed test Intersite
Starting test: FsmoCheck
......................... DOMAIN passed test FsmoCheck

 

[intelwizrd]

looks like a problem with the kerberos tickets witch is probably being caused because the AD info is not being replicated correctly. From each of the domain controllers, open a command promt and type net share. Do you see the share sysvol on all of the domain controllers? If not the DC's are not replicating correctly.

go to the PDC and check for problems with the file replication service and other errors. the PDC should have slightly different errors than the rest of the DC's. I just got done fixing a similar problem, maybe i can help but it will be much later tonight before i get back to you. if someone else hasn't helped you by then, ill see what i can do.

do you have the tool domain monitor and see if the replication status is insync and everything is online.

Cheers

 

[stopfd]

Thanks Intelwizrd, been off site for a couple of days. I believe this issue is ok now, not down to 2000 but a good old fashioned routing problem. Not helped by having a complex network topology with multiple routes in place.

As functionality of the DC's did not seem to be effected whilst the Directory Service errors were being generated it would appear that AD traffic failed using one route, would generate the Directory Service errors then would succeed using an alternate route.

All white mans magic, thanks again.