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.

You receive a WMI error message when you access the "NIS Servers" node in the Identity Management for Unix MMC snap-in on a computer that is running Windows Server 2003 R2


View products that this article applies to.

Symptoms

When you access the NIS Servers node in the Microsoft Identity Management for UNIX Microsoft Management Console (MMC) snap-in, you receive the following WMI error message:
A WMI error has occurred
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index.
Please refer help for more details
Note You receive this error message if the computer is running Microsoft Windows Server 2003 R2.

↑ Back to the top


Cause

This problem occurs when the serverReference attribute has a value of <Not Set> for a particular Server for NIS network in the Active Directory Configuration container.

↑ Back to the top


Resolution

To resolve this problem, populate the serverReference attribute value by using the distinguished name of the server object. You can locate this distinguished name under the following domain partition:
CN=<ServerName>,OU=Domain Controllers, DC=<YourDomain>,DC=<DomainSuffix>
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

To populate the serverReference attribute value, follow these steps:
  1. Click Start, click Run, type adsiedit.msc, and then click OK.
  2. Expand Configuration [<ServerName>.<YourDomain>.<DomainSuffix>].
  3. Expand CN=Configuration,DC=<YourDomain>,DC=<DomainSuffix>.
  4. Expand CN=Sites.
  5. Expand CN=Default-First-Site-Name.
  6. Expand CN=Servers.
  7. Right-click CN=<ServerName>, and then click Properties.
  8. In the Attributes list, click serverReference, and then click Edit.
  9. In the Value text box, type the following, and then click OK:
    CN=<ServerName>,OU=Domain Controllers, DC=<YourDomain>,DC=<DomainSuffix>
  10. Click OK to close the CN=<ServerName> Properties dialog box.

↑ Back to the top


Workaround

To work around this problem, use the Nisadmin.exe command line utility to perform all Server for NIS tasks instead of the Identity Management for UNIX MMC snap-in.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

This problem only occurs if the following conditions are true:
  • The computer is running Windows Server R2.
  • The computer is configured as a domain controller.
  • The computer has Identity Management for UNIX installed.
For more information about Identity Management for UNIX: Server for NIS, visit the following Microsoft TechNet Web site:

↑ Back to the top


Keywords: kberrmsg, kbtshoot, kbprb, KB923515

↑ Back to the top

Article Info
Article ID : 923515
Revision : 4
Created on : 8/15/2007
Published on : 8/15/2007
Exists online : False
Views : 158