DCDiag error

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Have two DC's, and in troubleshooting performance issues, found the following
error when running DCDiag for both domain controllers (W2K SP4):

======================================
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\MS-LB-DC1
Starting test: Connectivity
......................... MS-LB-DC1 passed test Connectivity

Testing server: Default-First-Site-Name\MS-LB-DC2
Starting test: Connectivity
......................... MS-LB-DC2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\MS-LB-DC1
Starting test: Replications
......................... MS-LB-DC1 passed test Replications
Starting test: NCSecDesc
......................... MS-LB-DC1 passed test NCSecDesc
Starting test: NetLogons
......................... MS-LB-DC1 passed test NetLogons
Starting test: Advertising
......................... MS-LB-DC1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... MS-LB-DC1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... MS-LB-DC1 passed test RidManager
Starting test: MachineAccount
......................... MS-LB-DC1 passed test MachineAccount
Starting test: Services
......................... MS-LB-DC1 passed test Services
Starting test: ObjectsReplicated
......................... MS-LB-DC1 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... MS-LB-DC1 passed test frssysvol
Starting test: kccevent
......................... MS-LB-DC1 passed test kccevent
Starting test: systemlog
......................... MS-LB-DC1 passed test systemlog

Testing server: Default-First-Site-Name\MS-LB-DC2
Starting test: Replications
......................... MS-LB-DC2 passed test Replications
Starting test: NCSecDesc
......................... MS-LB-DC2 passed test NCSecDesc
Starting test: NetLogons
......................... MS-LB-DC2 passed test NetLogons
Starting test: Advertising
......................... MS-LB-DC2 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... MS-LB-DC2 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... MS-LB-DC2 passed test RidManager
Starting test: MachineAccount
......................... MS-LB-DC2 passed test MachineAccount
Starting test: Services
......................... MS-LB-DC2 passed test Services
Starting test: ObjectsReplicated
......................... MS-LB-DC2 passed test ObjectsReplicated
Starting test: frssysvol
......................... MS-LB-DC2 passed test frssysvol
Starting test: kccevent
......................... MS-LB-DC2 passed test kccevent
Starting test: systemlog
......................... MS-LB-DC2 passed test systemlog

Running enterprise tests on : <domain name>
Starting test: Intersite
......................... <domain name> passed test Intersite
Starting test: FsmoCheck
......................... <domain name> passed test FsmoCheck
===========================================

I've seen two posts that the sysvol error is benign and can be ignored,
since it showed it passed anyway. This true? If not, anyone had this issue?

Any thoughts appreciated.

 

[Craig]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Look in the FRS event log to see what errors it is talking about.

"bclay" wrote:

> Have two DC's, and in troubleshooting performance issues, found the following
> error when running DCDiag for both domain controllers (W2K SP4):
>
> ======================================
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\MS-LB-DC1
> Starting test: Connectivity
> ......................... MS-LB-DC1 passed test Connectivity
>
> Testing server: Default-First-Site-Name\MS-LB-DC2
> Starting test: Connectivity
> ......................... MS-LB-DC2 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\MS-LB-DC1
> Starting test: Replications
> ......................... MS-LB-DC1 passed test Replications
> Starting test: NCSecDesc
> ......................... MS-LB-DC1 passed test NCSecDesc
> Starting test: NetLogons
> ......................... MS-LB-DC1 passed test NetLogons
> Starting test: Advertising
> ......................... MS-LB-DC1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... MS-LB-DC1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... MS-LB-DC1 passed test RidManager
> Starting test: MachineAccount
> ......................... MS-LB-DC1 passed test MachineAccount
> Starting test: Services
> ......................... MS-LB-DC1 passed test Services
> Starting test: ObjectsReplicated
> ......................... MS-LB-DC1 passed test ObjectsReplicated
> Starting test: frssysvol
> There are errors after the SYSVOL has been shared.
> The SYSVOL can prevent the AD from starting.
> ......................... MS-LB-DC1 passed test frssysvol
> Starting test: kccevent
> ......................... MS-LB-DC1 passed test kccevent
> Starting test: systemlog
> ......................... MS-LB-DC1 passed test systemlog
>
> Testing server: Default-First-Site-Name\MS-LB-DC2
> Starting test: Replications
> ......................... MS-LB-DC2 passed test Replications
> Starting test: NCSecDesc
> ......................... MS-LB-DC2 passed test NCSecDesc
> Starting test: NetLogons
> ......................... MS-LB-DC2 passed test NetLogons
> Starting test: Advertising
> ......................... MS-LB-DC2 passed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... MS-LB-DC2 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... MS-LB-DC2 passed test RidManager
> Starting test: MachineAccount
> ......................... MS-LB-DC2 passed test MachineAccount
> Starting test: Services
> ......................... MS-LB-DC2 passed test Services
> Starting test: ObjectsReplicated
> ......................... MS-LB-DC2 passed test ObjectsReplicated
> Starting test: frssysvol
> ......................... MS-LB-DC2 passed test frssysvol
> Starting test: kccevent
> ......................... MS-LB-DC2 passed test kccevent
> Starting test: systemlog
> ......................... MS-LB-DC2 passed test systemlog
>
> Running enterprise tests on : <domain name>
> Starting test: Intersite
> ......................... <domain name> passed test Intersite
> Starting test: FsmoCheck
> ......................... <domain name> passed test FsmoCheck
> ===========================================
>
> I've seen two posts that the sysvol error is benign and can be ignored,
> since it showed it passed anyway. This true? If not, anyone had this issue?
>
> Any thoughts appreciated.

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Hey,

I will chime in!

Take a look to see if the event id is 13508 ( IIRC ). And if that is the
case see if you have a 13509 immediately after the 13508. If that is the
case then you *should* be okay.

You might also want to take a look at FRSDiag. This is a basic FRS
troubleshooting utility. If there are problems then you might want to look
at the big boys of FRS troubleshooting: ultrasound and sonar.

FRS is very important. Half of your GPOs are replicated to other Domain
Controllers via FRS ( the GPT, or Group Policy Template ). Er, there are
other reasons that FRS is important as well.

--
Cary W. Shultz
Roanoke, VA 24014
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com



"bclay" <bclay@discussions.microsoft.com> wrote in message
news:683FAD41-E0FD-48AA-AE78-FCF7CB508B83@microsoft.com...
> Have two DC's, and in troubleshooting performance issues, found the
> following
> error when running DCDiag for both domain controllers (W2K SP4):
>
> ======================================
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\MS-LB-DC1
> Starting test: Connectivity
> ......................... MS-LB-DC1 passed test Connectivity
>
> Testing server: Default-First-Site-Name\MS-LB-DC2
> Starting test: Connectivity
> ......................... MS-LB-DC2 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\MS-LB-DC1
> Starting test: Replications
> ......................... MS-LB-DC1 passed test Replications
> Starting test: NCSecDesc
> ......................... MS-LB-DC1 passed test NCSecDesc
> Starting test: NetLogons
> ......................... MS-LB-DC1 passed test NetLogons
> Starting test: Advertising
> ......................... MS-LB-DC1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... MS-LB-DC1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... MS-LB-DC1 passed test RidManager
> Starting test: MachineAccount
> ......................... MS-LB-DC1 passed test MachineAccount
> Starting test: Services
> ......................... MS-LB-DC1 passed test Services
> Starting test: ObjectsReplicated
> ......................... MS-LB-DC1 passed test ObjectsReplicated
> Starting test: frssysvol
> There are errors after the SYSVOL has been shared.
> The SYSVOL can prevent the AD from starting.
> ......................... MS-LB-DC1 passed test frssysvol
> Starting test: kccevent
> ......................... MS-LB-DC1 passed test kccevent
> Starting test: systemlog
> ......................... MS-LB-DC1 passed test systemlog
>
> Testing server: Default-First-Site-Name\MS-LB-DC2
> Starting test: Replications
> ......................... MS-LB-DC2 passed test Replications
> Starting test: NCSecDesc
> ......................... MS-LB-DC2 passed test NCSecDesc
> Starting test: NetLogons
> ......................... MS-LB-DC2 passed test NetLogons
> Starting test: Advertising
> ......................... MS-LB-DC2 passed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... MS-LB-DC2 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... MS-LB-DC2 passed test RidManager
> Starting test: MachineAccount
> ......................... MS-LB-DC2 passed test MachineAccount
> Starting test: Services
> ......................... MS-LB-DC2 passed test Services
> Starting test: ObjectsReplicated
> ......................... MS-LB-DC2 passed test ObjectsReplicated
> Starting test: frssysvol
> ......................... MS-LB-DC2 passed test frssysvol
> Starting test: kccevent
> ......................... MS-LB-DC2 passed test kccevent
> Starting test: systemlog
> ......................... MS-LB-DC2 passed test systemlog
>
> Running enterprise tests on : <domain name>
> Starting test: Intersite
> ......................... <domain name> passed test Intersite
> Starting test: FsmoCheck
> ......................... <domain name> passed test FsmoCheck
> ===========================================
>
> I've seen two posts that the sysvol error is benign and can be ignored,
> since it showed it passed anyway. This true? If not, anyone had this
> issue?
>
> Any thoughts appreciated.

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

bclay wrote:
> Have two DC's, and in troubleshooting performance issues, found the following
> error when running DCDiag for both domain controllers (W2K SP4):
Check if SYSVOL is avilable on this DC, Check FRS event log (as Craig
sugessted) to see if any problems with replication for this host occured?



--
Tomasz Onyszko [MVP]
T.Onyszko@w2k.pl
http://www.w2k.pl

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Thanks for the replies.

Yes, sysvol is shared and accessible on both DC's..

Thee are several 13508's followed by 13509's. There are also a small handful
of 13508's NOT followed by 13509's. What's interesting is the times there are
not 13509's appear to be when we did reboots, of both servers, and maybe the
other DC was not accessible at that time?

I ran FRDDiag on both servers - DC2 had three errors - all 13508's with no
following 13509's.

DC1 is a different story - it has one 'no 13509' - but also multiple errors
in the 'debug logs': Here they are, no idea how they will wrap And sorry
for the long post. I'm researching and about to get sonar and ultrasound...

++++++++++++++++++++++++++++++++++++++++++++

Checking for errors in debug logs ...
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
1612: 895: S0: 21:10:28> :SR: Cmd 00238408, CxtG e0c6a463, WS
ERROR_ACCESS_DENIED, To ms-lb-dc2.mydomain.com Len: (376) [SndFail - Send
Penalty]
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
688: 868: S0: 21:10:28> :SR: Cmd 015a27e0, CxtG cf4a754b, WS
ERROR_ACCESS_DENIED, To ms-lb-dc2.mydomain.com Len: (544) [SndFail - rpc
call]
ERROR on NtFrs_0001.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
688: 895: S0: 21:10:28> :SR: Cmd 015a27e0, CxtG cf4a754b, WS
ERROR_ACCESS_DENIED, To ms-lb-dc2.mydomain.com Len: (544) [SndFail - Send
Penalty]
ERROR on NtFrs_0001.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS
returns the IP address of the wrong computer. Check DNS records being
returned, Check if FRS is currently running on the target server. Check if
Ntfrs is registered with the End-Point-Mapper on target server!)" :
<SndCsMain: 1612: 874: S0: 21:09:27> ++ ERROR -
EXCEPTION (000006d9) : WStatus: EPT_S_NOT_REGISTERED
ERROR on NtFrs_0001.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS
returns the IP address of the wrong computer. Check DNS records being
returned, Check if FRS is currently running on the target server. Check if
Ntfrs is registered with the End-Point-Mapper on target server!)" :
<SndCsMain: 1612: 875: S0: 21:09:27> :SR: Cmd 015af130,
CxtG cf4a754b, WS EPT_S_NOT_REGISTERED, To ms-lb-dc2.mydomain.com Len:
(376) [SndFail - rpc exception]
ERROR on NtFrs_0001.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS
returns the IP address of the wrong computer. Check DNS records being
returned, Check if FRS is currently running on the target server. Check if
Ntfrs is registered with the End-Point-Mapper on target server!)" :
<SndCsMain: 1612: 895: S0: 21:09:27> :SR: Cmd 015af130,
CxtG cf4a754b, WS EPT_S_NOT_REGISTERED, To ms-lb-dc2.mydomain.com Len:
(376) [SndFail - Send Penalty]

Found 4 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
Found 3 EPT_S_NOT_REGISTERED error(s)! Latest ones (up to 3) listed above

......... failed with 7 error entries

++++++++++++++++++++++++++++++++++++++++++++




"Cary Shultz [A.D. MVP]" wrote:

> Hey,
>
> I will chime in!
>
> Take a look to see if the event id is 13508 ( IIRC ). And if that is the
> case see if you have a 13509 immediately after the 13508. If that is the
> case then you *should* be okay.
>
> You might also want to take a look at FRSDiag. This is a basic FRS
> troubleshooting utility. If there are problems then you might want to look
> at the big boys of FRS troubleshooting: ultrasound and sonar.
>
> FRS is very important. Half of your GPOs are replicated to other Domain
> Controllers via FRS ( the GPT, or Group Policy Template ). Er, there are
> other reasons that FRS is important as well.
>
> --
> Cary W. Shultz
> Roanoke, VA 24014
> Microsoft Active Directory MVP
>
> http://www.activedirectory-win2000.com
> http://www.grouppolicy-win2000.com
>
>
>
> "bclay" <bclay@discussions.microsoft.com> wrote in message
> news:683FAD41-E0FD-48AA-AE78-FCF7CB508B83@microsoft.com...
> > Have two DC's, and in troubleshooting performance issues, found the
> > following
> > error when running DCDiag for both domain controllers (W2K SP4):
> >
> > ======================================
> > Domain Controller Diagnosis
> >
> > Performing initial setup:
> > Done gathering initial info.
> >
> > Doing initial required tests
> >
> > Testing server: Default-First-Site-Name\MS-LB-DC1
> > Starting test: Connectivity
> > ......................... MS-LB-DC1 passed test Connectivity
> >
> > Testing server: Default-First-Site-Name\MS-LB-DC2
> > Starting test: Connectivity
> > ......................... MS-LB-DC2 passed test Connectivity
> >
> > Doing primary tests
> >
> > Testing server: Default-First-Site-Name\MS-LB-DC1
> > Starting test: Replications
> > ......................... MS-LB-DC1 passed test Replications
> > Starting test: NCSecDesc
> > ......................... MS-LB-DC1 passed test NCSecDesc
> > Starting test: NetLogons
> > ......................... MS-LB-DC1 passed test NetLogons
> > Starting test: Advertising
> > ......................... MS-LB-DC1 passed test Advertising
> > Starting test: KnowsOfRoleHolders
> > ......................... MS-LB-DC1 passed test KnowsOfRoleHolders
> > Starting test: RidManager
> > ......................... MS-LB-DC1 passed test RidManager
> > Starting test: MachineAccount
> > ......................... MS-LB-DC1 passed test MachineAccount
> > Starting test: Services
> > ......................... MS-LB-DC1 passed test Services
> > Starting test: ObjectsReplicated
> > ......................... MS-LB-DC1 passed test ObjectsReplicated
> > Starting test: frssysvol
> > There are errors after the SYSVOL has been shared.
> > The SYSVOL can prevent the AD from starting.
> > ......................... MS-LB-DC1 passed test frssysvol
> > Starting test: kccevent
> > ......................... MS-LB-DC1 passed test kccevent
> > Starting test: systemlog
> > ......................... MS-LB-DC1 passed test systemlog
> >
> > Testing server: Default-First-Site-Name\MS-LB-DC2
> > Starting test: Replications
> > ......................... MS-LB-DC2 passed test Replications
> > Starting test: NCSecDesc
> > ......................... MS-LB-DC2 passed test NCSecDesc
> > Starting test: NetLogons
> > ......................... MS-LB-DC2 passed test NetLogons
> > Starting test: Advertising
> > ......................... MS-LB-DC2 passed test Advertising
> > Starting test: KnowsOfRoleHolders
> > ......................... MS-LB-DC2 passed test KnowsOfRoleHolders
> > Starting test: RidManager
> > ......................... MS-LB-DC2 passed test RidManager
> > Starting test: MachineAccount
> > ......................... MS-LB-DC2 passed test MachineAccount
> > Starting test: Services
> > ......................... MS-LB-DC2 passed test Services
> > Starting test: ObjectsReplicated
> > ......................... MS-LB-DC2 passed test ObjectsReplicated
> > Starting test: frssysvol
> > ......................... MS-LB-DC2 passed test frssysvol
> > Starting test: kccevent
> > ......................... MS-LB-DC2 passed test kccevent
> > Starting test: systemlog
> > ......................... MS-LB-DC2 passed test systemlog
> >
> > Running enterprise tests on : <domain name>
> > Starting test: Intersite
> > ......................... <domain name> passed test Intersite
> > Starting test: FsmoCheck
> > ......................... <domain name> passed test FsmoCheck
> > ===========================================
> >
> > I've seen two posts that the sysvol error is benign and can be ignored,
> > since it showed it passed anyway. This true? If not, anyone had this
> > issue?
> >
> > Any thoughts appreciated.
>
>
>