DIAGNOSEDIR
Function
 WarningThe Directory entries are a key part of a user's account. Be sure to have a current backup before starting a Directory repair. We recommend you contact FirstClass Customer Support before beginning this process.
Performs Directory diagnostics on a live server. Replaces functionality previous performed by FirstClass Tools. A diagnosis of Directory items should be performed when there seems to be damage to user records, specifically if users or conferences can't be accessed through the Directory when you know they exist.
To isolate a Directory issue, you should begin by searching for the address in three different ways. Using Admin > List Directory, search by name, user ID, and CID. For Example, Susan Bram cannot log into the server even though her name appears in the Directory. To confirm a Directory issue, you would set the "Search" field to Name and search for Susan Bram. Then set the "Search" field to User ID, and search for sbram. Lastly, you would search for Susan's CID 1707. Only if one of the searches fail do you have a directory issue.
The Directory is made of three redundant databases. The DIAGNOSEDIR command is used to find a valid entry in one of the three databases. Once located, the valid entry is copied to the other two indices with REPAIRDIR.
The REPLY command is required. The User Directory Diagnostics message form in the Administration help provides a script to aid in Directory diagnosis and repair.
Syntax
REPLY
DIAGNOSEDIR dirdesc pattern CID option
Parameters
dirdesc |
Index, Client, User, Gateway, Conference, Calendar, MailList, Remote, Group, or Route. |
pattern |
The string you want to search for. Optional. |
CID |
Required when using the Client dirdesc. Optional when using any other dirdesc. |
+n |
Treats the specified pattern as a name and will search the Name index. |
Examples
To isolate a Directory that has a valid entry for Susan Bram, submit the following commands:
REPLY
//Checks the UserID index
DIAGNOSEDIR USER sbram
//Checks the CID index
DIAGNOSEDIR CLIENT 1707
//Checks the Name index, the CID is included to ensure the correct user named Bram is examined, +n is required
DIAGNOSEDIR USER "bram" 1707 +n
The server will return the following:
Diagnostic report for parameters: USER sbram
[1] (1707) "sbram" Susan Bram
SUMMARY:
1 entries were diagnosed.
0 problems found.
If one of the three parameters reports a problem, you can fix it using the REPAIRDIR command.
If advised to do so by FirstClass Customer Support, you can run diagnostics for an entire index.
To diagnose the Name index, enter:
REPLY
DIAGNOSEDIR index name
To diagnose the Client ID index, enter:
REPLY
DIAGNOSEDIR index cid
To diagnose the Name index, enter:
REPLY
DIAGNOSEDIR index userid
| 