DCDIAG passes everything except Starting test: systemlog

I have a 2 DC Windows 2003 network.

Central04 is a Windows 2003 R2 DC - NO DHCP Services
Central01 is a Windows 2003 DC + DHCP Services

dcdiag on central04 is clean.
dcdiag on central01 results in passing everything **except** the
systemlog test:

Starting test: kccevent
......................... CENTRAL01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000416
Time Generated: 11/27/2007 08:22:31
Event String: The DHCP/BINL service on the local machine,
......................... CENTRAL01 failed test systemlog
Starting test: VerifyReferences
......................... CENTRAL01 passed test
VerifyReferences

All fully qualified resolutions work.

I've tried de-authorizing the DHCP server and reauthorizing... no
difference.

I can't find any information about this error in the context of
everything else passing.

HELP!

To add,

THE DHCP server appears to work fine. Clients have no problem getting
IP addresses.

Hello SupportAV,

This entry states that there is an error in the system event. It is possible
that the error is solved and just an old entry. So delete the content from
system events and run the test again.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> I have a 2 DC Windows 2003 network.
>
> Central04 is a Windows 2003 R2 DC - NO DHCP Services Central01 is a
> Windows 2003 DC + DHCP Services
>
> dcdiag on central04 is clean.
> dcdiag on central01 results in passing everything **except** the
> systemlog test:
> Starting test: kccevent
> ......................... CENTRAL01 passed test kccevent
> Starting test: systemlog
> An Error Event occured. EventID: 0x00000416
> Time Generated: 11/27/2007 08:22:31
> Event String: The DHCP/BINL service on the local machine,
> ......................... CENTRAL01 failed test systemlog
> Starting test: VerifyReferences
> ......................... CENTRAL01 passed test
> VerifyReferences
> All fully qualified resolutions work.
>
> I've tried de-authorizing the DHCP server and reauthorizing... no
> difference.
>
> I can't find any information about this error in the context of
> everything else passing.
>
> HELP!
>

On Nov 27, 1:34 pm, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
> Hello SupportAV,
>
> This entry states that there is an error in the system event. It is possible
> that the error is solved and just an old entry. So delete the content from
> system events and run the test again.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!http://www.dts-l.org/goodpost.htm
>
>
>
> > I have a 2 DC Windows 2003 network.
>
> > Central04 is a Windows 2003 R2 DC - NODHCPServices Central01 is a
> > Windows 2003 DC +DHCPServices
>
> >dcdiagon central04 is clean.
> >dcdiagon central01 results in passing everything **except** the
> > systemlog test:
> > Starting test: kccevent
> > ......................... CENTRAL01 passed test kccevent
> > Starting test: systemlog
> > An Error Event occured. EventID: 0x00000416
> > Time Generated: 11/27/2007 08:22:31
> > Event String: TheDHCP/BINL service on the local machine,
> > ......................... CENTRAL01 failed test systemlog
> > Starting test: VerifyReferences
> > ......................... CENTRAL01 passed test
> > VerifyReferences
> > All fully qualified resolutions work.
>
> > I've tried de-authorizing theDHCPserver and reauthorizing... no
> > difference.
>
> > I can't find any information about this error in the context of
> > everything else passing.
>
> > HELP!- Hide quoted text -
>
> - Show quoted text -



Thanks for your reply. I tried your suggestion and the error kept
coming back so I finally rebooted both servers and waited a few
minutes before running DCDIAG again. Both are clean now but I can't
say I really "did" anything.

I'm sure this was said before, but MS could do a much better job of
incorporating an index of error codes to human-readable messages so
that people don't waste their time.

Hello SupportAV,

Have a look here about dcdiag, the switches and the output:
http://technet2.microsoft.com/window....mspx?mfr=true

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> On Nov 27, 1:34 pm, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
>
>> Hello SupportAV,
>>
>> This entry states that there is an error in the system event. It is
>> possible that the error is solved and just an old entry. So delete
>> the content from system events and run the test again.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!!http://www.dts-l.org/goodpost.htm
>>> I have a 2 DC Windows 2003 network.
>>>
>>> Central04 is a Windows 2003 R2 DC - NODHCPServices Central01 is a
>>> Windows 2003 DC +DHCPServices
>>>
>>> dcdiagon central04 is clean.
>>> dcdiagon central01 results in passing everything **except** the
>>> systemlog test:
>>> Starting test: kccevent
>>> ......................... CENTRAL01 passed test kccevent
>>> Starting test: systemlog
>>> An Error Event occured. EventID: 0x00000416
>>> Time Generated: 11/27/2007 08:22:31
>>> Event String: TheDHCP/BINL service on the local machine,
>>> ......................... CENTRAL01 failed test systemlog
>>> Starting test: VerifyReferences
>>> ......................... CENTRAL01 passed test
>>> VerifyReferences
>>> All fully qualified resolutions work.
>>> I've tried de-authorizing theDHCPserver and reauthorizing... no
>>> difference.
>>>
>>> I can't find any information about this error in the context of
>>> everything else passing.
>>>
>>> HELP!- Hide quoted text -
>>>
>> - Show quoted text -
>>
> Thanks for your reply. I tried your suggestion and the error kept
> coming back so I finally rebooted both servers and waited a few
> minutes before running DCDIAG again. Both are clean now but I can't
> say I really "did" anything.
>
> I'm sure this was said before, but MS could do a much better job of
> incorporating an index of error codes to human-readable messages so
> that people don't waste their time.
>