"Invalid Name" Error Message When You Log On to MMS Server with Compass (251245)

RESOLUTION

To resolve the problem, use the following troubleshooting steps:

1. Determine if a specific user can log on to the MMS server using their SMTP e-mail address. If the problem is isolated to only one user, refer to the "Logon Name (SMTP E-Mail Address) Is Invalid" section of this article. If the problem is not isolated to just one user, continue to step 2.
2. Determine if a specific user can log on to the MMS server using their distinguished name. If not, refer to the "User Does Not Exist in the Database" section of this article.
3. Determine if any users can log on anonymously to the MMS server. If not, refer to the "Problems with the X500.db Database File" section of this article. (For more information about anonymous logon, refer to the "More Information" section of this article.)
4. Determine if any users can log on (authenticated) to the MMS server (using either their distinguished name or SMTP e-mail address). If not, refer to the "Hashing Function in the Database Is Not Working Properly" section of this article. (For more information about authenticated logon, refer to the "More Information" section of this article.)

Logon Name (SMTP E-Mail Address) Is Invalid

To verify that the logon name is correct, use the following steps:

1. Log on to Compass anonymously or as another user (this works unless the default Access Controls have been changed).
2. In the Action panel, click Search.
3. In the Search box, type the user's name, and then press ENTER.
4. The default search method is for Match Attribute is Any, or any hashed attribute. At least one match should be displayed in the panel beneath the Search dialog box. Click the correct match and then double-click the user's name to display the user properties.
5. On the General tab, click to select the Email check box. The name must be identical to the name you are typing to log on to Compass.
   
   NOTE: To confirm that you use the exact string, it is recommended that you copy the value from the Email box and paste it into the logon dialog box.

User Does Not Exist in the Database

To verify that the user exists in the database, use the following steps:

1. Attempt to log on anonymously through Compass.
2. Click Known Universe.
3. In the left-hand panel, click Search.
4. Type administrator, and then press ENTER.
5. If no Administrator entries are displayed below the Search dialog box, refer to the "Problems with the X500.db Database File" section of this article.
6. If you find the Administrator entry, double-click the icon to display the entry's properties.

If you are unable to search anonymously,there may be a security restriction in place. If you are unable to log on as an administrator to check security access controls, contact Microsoft Product Support Services.

Problems with the X500.db Database File

If the database is deleted or renamed, the Zoomit Server service creates a new database when the service starts. To verify the size of the X500.db file, use the following steps:

1. Go to the Zoomserv\Data\Db folder.
2. Locate the x500.db file.
3. Right-click the file, and then click Properties.
4. On the General tab, note the size of the file.
   
   NOTE: File sizes vary. A zero-byte file indicates a severe problem (there is no data in the Asn.1 database and the entire database must be recovered from backup).
5. If the size of the file is normal, refer to the "Hashing Function in the Database Is Not Working Properly" section of this article.

Hashing Function in the Database Is Not Working Properly

Make sure you have ruled out all preceding scenarios. In this situation, you are unable to log on to the database as any user, although the X500.db file size is greater than 0 bytes. If you confirm this, use either of the following methods to attempt to resolve the issue:

• Run Viahashtool.exe with the server online and regenerate only the hash tables (for additional information, refer to the "More Information" section of this article).
• Run Viacompact.exe with the server offline and regenerate the entire database. (For additional information about the Viacompact tool, refer to the "More Information" section of this article.)
  
  NOTE: This is the most radical and costly option because the process can take many hours. In addition, the server must remain offline for the entire process and the process cannot be stopped.

If you are still unable to resolve the invalid name issue, contact Microsoft Product Support Services.