With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Brooklyn98
- Application: Outlook - I received this event along with events 3003 and 3011 from the same source. The issue was Outlook 2003 on a 2003 server. Deleting the "HKLM\System\Current Control Set\Services\Outlook\Performance" registry key fixed the issue.
x
57

Anonymous
When using Citrix\Terminal Services, if you install Office 2003 you must login as an administrator to complete the configuration of the Performance Counters. An event ID 1000 will confirm the load\unload of performance counters. After that, all users should be able to launch Outlook without any errors being written to the event log.
x
38

Charlie Harris
In my case, the source of the problem ended up being with NTDS Performance counters. Once the procedure in ME300956 was followed and the counters rebuilt, the error disappeared.
x
27

John Narkis
This error appeared on a box loaded with Exchange 2000 with a direct application of Exchange SP3. Trying to un-register and register the “eseperf.dll” did not work. Pulling the following two files from Exchange 2000 SP2 seemed to fix the problem, “eseperf.hxx” (7K 5/21/2002) and “eseperf.ini” (380K 6/18/2002). These files reside in the “%exchange_install_dir%\BIN” directory. After replacing these two files, I ran the “unlodctr” and “lodctr” commands and the performance counter entries were properly populated in the registry.
x
28

EventID.Net
Application: ESE97. As per Microsoft's ME273177, this problem can occur when a registry setting associated with a Performance Monitor counter is damaged, causing the Exchange Server Setup program to incorrectly determine that the counters associated with the Exchange Database Engine have already been installed.
x
27

Jesse Cole
Application: DNS. As per ME304541 this is a current problem of Windows 2000. At the command prompt type the following commands:
CD %WINDIR% \SYSTEM32
UNLODCTR DNSPERF.INI
LODCTR DNSPERF.INI
NOTE: DNS service must be running for the performance counters to be available.
x
26

EventID.Net
One of the recommendations for this event was to use the UnLodCtr DNSperf.ini and LodCtr DNSperf.ini, which is partially correct (it is UnLodCtr "Performance Service Name", looks like Microsoft made a mistake in ME304541). Please note that the file DNSperf.ini is not available in the system and must be built or obtained. Adding a perf counter is not an easy job...
x
30

EventID.Net
Applications: "Inetinfo", "ASP, "MSFTPSVC", "W3SVC". The error can occur after Service Pack 3 (SP3) for Windows 2000 installation. To work around this problem, reinstall and then remove IIS. For details see ME325727 link below.
x
29