Error Fills Log

[kimble]

Does anyone know how to correct this error. It keeps getting logged ~ every second and it's filling up my log.



Event Type: Error
Event Source: Perflib
Event Category: None
Event ID: 1008
Date: 9/18/2001
Time: 8:20:37 AM
User: N/A
Computer: BTV-01
Description:
The Open Procedure for service "Nbf" in DLL "C:\WINNT\system32\perfctrs.dll" failed. Performance data for this service will not be available. Status code returned is data DWORD 0.
Data:
0000: 02 00 00 00 ....

 

[gbiello]

Check out Q247226. Did you uninstall something recently that may have had performance counters?

The 'ulodctr' program it references is in c:\winnt\system32. You can reload the counters with 'lodctr'.

 

[kimble]

Sorry for the dumb questions, but how do i get to Q247226? And should I run ulodctr and then lodctr from the run command, or just double click on them from windows explorer?
When I double click them nothing seems to happen and the error is still being reported.

I haven't uninstalled anything lately. I have only been making changes with exchange. I really don't remember though and I cleared the application log so I can't find out.

Thanks

 

[gbiello]

Not a problem, if you don't ask, how are you to find out?

http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q247226.

Here is another way to access it: Go to

http://search.support.microsoft.com,

that will allow you to search the microsoft database. Select an operating system, then type your question (or 'q247226') in the 'My question is:' field.

I would run ulodctr from the DOS prompt, then edit the registy, then reload.

-gbiello

 

[kimble]

The error looks to have come from adding NetBEUI Protocal to
the internal network card. Do you still recommend the regedit or should I just remove and reinstall the protocal?

 

[gbiello]

If you feel it's from NetBEUI, just remove that and see if that clears it up. If it doesn't then do the registry change. NetBEUI is rarely used now, and just clutters up networks, as it is a very chatty protocol.

Always save the branch of the registry you're editting before actually changing it!

 

[kimble]

I removed it and that error seems to have cleared up. Yet now I'm getting this Warning. You don't by chance how to fix this?


Event Type: Warning
Event Source: MSExchangeSA
Event Category: General
Event ID: 9157
Date: 9/18/2001
Time: 11:01:02 AM
User: N/A
Computer: BTV-01
Description:
Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. System attendant will try again in approximately one minute.

For more information, click

http://www.microsoft.com/contentredirect.asp.

 

[gbiello]

I would see what account your Exchange Services are logging in as, especially the System Attendant. Then check what sort of permissions that account has on the Sysvol directory. If that doesn't help, you will probably have to try some auditing to troubleshoot further.