Error messages are logged when you try to collect performance counters for Exchange (307613)

RESOLUTION

• Reinstall the Exchange Server software, and then reapply any service packs
  
  Note Use only the Reinstall option. This option will replace the missing files. A fresh install will overwrite all files.
• Use the Lodctr.exe and Unlodctr.exe Windows utilities
  
  The Microsoft Exchange Server Setup program uses these two utilities to add and to remove Performance Monitor objects and counters. These utilities are included with Windows NT, Windows 2000, and Windows Server 2003. These utilities can be run on a command prompt to restore the Performance Monitor objects and counters if the objects and counters become unavailable in the list of objects in Performance Monitor.
  
  Note Lodctr.exe adds objects and counters. Unlodctr.exe removes objects and counters.

How to use the Lodctr.exe and Unlodctr.exe utilities to restore the Performance Monitor counters in Windows

1. Use the following syntax to unload a performance driver, where driver is the name of the performance object driver that is located in Performance Monitor:
   
   Unlodctr.exe driver
   
   For example, to unload MSExchangeIS counter, type unlodctr.exe MSExchangeIS
2. Make sure that the .dll files, the .ini files, and the .h files for the performance counters are the same version. Additionally, make sure that the file version, size and date are correct.
   
   For example, the following four files are necessary for Performance Monitor to correctly display MSExchangeIS counters in Exchange Server 2003:
   • Mdbperf.dll
   • Mdbperfx.dll
   • Mdbperf.ini
   • Perfnm.h
   All four files must come from the same installation of Exchange Server. If the files do not come from the same installation, copy these files from the Exchange Server 2003 service pack CD to the server's \Exchsrvr\Bin directory.
   
   Notes Because .h files have no version tabs, the setup process depends on file dates to determine whether a file on the hard disk should be overwritten. Make sure to copy the symbol file together with the .dll file and the .ini file. This symbol file has an .h extension.
   
   To verify which symbol file is linked with the .dll file and the .ini file, edit the .ini file, view the [info] section, and then look for the Symbolfile= parameter.
   
   You can also verify the version the of the .h file that you are using by opening the Perfnm.h file in Notepad. For example, in Exchange Server 2003, the various versions display the following statements:
   • Original release version

     THIS FILE IS AUTOMATICALLY GENERATED FROM F:\TITANIUM\store\lang\usa\mdbperf.perf

   • SP1 version

     THIS FILE IS AUTOMATICALLY GENERATED FROM F:\TISP1\store\lang\usa\mdbperf.perf

   • SP2 version

     THIS FILE IS AUTOMATICALLY GENERATED FROM F:\TISP2\store\lang\usa\mdbperf.perf

3. Use the following syntax to reload the object and counter information, where Initialization file name is the name of the .ini file that corresponds to the object and counter information:
   
   Lodctr.exe Initialization file name
   
   For example, to load the MSExchangeIS counter, type lodctr.exe c:\program files\exchsrvr\bin\Mdbperf.ini
   
   If this command does not work from the default directory at the command line, you may have to run the lodctr command directly from the Bin directory. To do this, follow these steps:
   1. Click Start, click Run, type cmd in the Open box, and then click OK.
   2. At the command prompt, type cd \program files\exchsrvr\bin, and then press ENTER.
   3. At the c:\program files\exchsrvr\bin> prompt, type lodctr.exe Mdbperf.ini, and then press ENTER.
   Note Performance Monitor must be restarted after you use either of these utilities. On Windows NT 4.0, the computer must be restarted after you use the lodctr command.