Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Err Msg: The Command LODCTR DSACTRS.INI Failed


View products that this article applies to.

Symptoms

You might receive the following error while updating Microsoft Exchange Server version 4.0:
The command lodctr dsactrs.ini failed, returning an error code of <112>.

Processing file 'server.ins', at or near line 122
An internal component has failed.
Microsoft Exchange Server Setup
ID no: c103264c
When upgrading to Microsoft Exchange Server version 5.0, you might receive the following error:
The command lodctr dsactrs.ini failed, returning an error code of <112>.

Processing file 'server.ins', at or near line 138
An internal component has failed.
Microsoft Exchange Server Setup
ID no: c103798a

↑ Back to the top


Cause

The following two files in the <WINNT>\SYSTEM32 directory are either missing, corrupt or you do not have permission to access them:
Perfc009.dat
Perfh009.dat

↑ Back to the top


Resolution

If the files are there, check to make sure that you have the correct permissions to access and write to those files. If you have the correct permissions, then you may need to rename the files and expand them from the Windows NT Server compact disk.

If the files are missing or need to be replaced, expand them off the Windows NT Server compact disk and into the <WINNT>\SYSTEM32 directory. The following command-line command demonstrates how this can be done:
expand <CD drive>:\i386\perfc009.da_ c:\winnt35\system32\perfc009.dat
NOTE: Renaming, replacing, or deleting these DAT files will cause the counters for any installed applications to be removed, and you will have to reinstall other applications if you replace these two files.

↑ Back to the top


More information

The Lodctr utility adds performance monitor counter information to these two DAT files. If the files are missing or you do not have access to them, the above errors will occur.
These errors can also be cause by a corruption in the performance counter descriptions in the registry. For more information, please see the following article in the Microsoft Knowledge Base:

189943 Performance Counters Become Corrupted After BackOffice 4.0 Setup

↑ Back to the top


Properties

↑ Back to the top


Article Info
Article ID : 161791
Revision : 5
Created on : 1/1/0001
Published on : 1/1/0001
Exists online : False
Views : 452