This section includes information for troubleshooting eDirectory on Windows* NT* and Windows 2000 networks.
eDirectory offers the Novell robust directory service and the fault tolerance inherent in replication. Replication allows you to keep copies of the eDirectory database, or portions of it, on multiple servers at once.
You should always keep multiple replicas of eDirectory partitions. If you do so and one replica becomes corrupted or is lost because of a failed hard disk, you can delete that replica using ConsoleOneTM and replace it with a new one from the intact replica.
If the eDirectory server fails to start when you boot the NT/2000 server, a message will notify you that the service failed to start.
If there are no other eDirectory database replicas, users can't log in.
If there are other replicas, logging in might be slow and you will see communication errors and synchronization errors on the servers holding those replicas.
You'll need to resolve the related-service problem before starting the eDirectory server.
If the eDirectory server can't open the database files, a message on the NT/2000 server will notify you.
If there are no other database replicas, users can't log in.
If there are other replicas, logging in might be slow and you will see communication errors and synchronization errors on the servers holding those replicas.
If other replicas of the eDirectory database exist, complete the following steps:
Start ConsoleOne from an administrative workstation.
Select the corrupted replica and remove it from the replica ring.
Run the SAMMIG.EXE utility in the system directory (usually C:\WINNT\SYSTEM32) on the NT server or from the Start menu: Start > Programs > Administrative Tools (Common) > Migration Tool for NetWare®.
Select the option to create a new replica on the eDirectory server.
If this eDirectory server holds the only replica of the partition, complete the following steps:
Run the SAMMIG.EXE utility in the system directory (usually C:\WINNT\SYSTEM32) on the NT Server or from the Start menu: Start > Programs > Administrative Tools (Common) > Migration Tool for NetWare.
Select Uninstall NDS on Windows NT/2000 and revert to the previous NT/2000 domain state.
Continue with the Uninstall until it has completed.
Restart the Migration Tool for NetWare and proceed to install eDirectory on Windows NT/2000.
Move the User objects from the NT/2000 domain to the eDirectory tree.
When you are forced to do an emergency repair on an NT/2000 server, and there is no Emergency Repair disk, or the Emergency Repair disk was created before an eDirectory installation, the eDirectory client is removed and Registry settings are deleted. The NDS4NTER.EXE utility both restores the necessary Registry settings and reloads eDirectory files.
Run NDS4NTER.EXE from the \i386\GOODIES directory.
After an emergency repair is performed, run the Emergency Repair utility from the CD. The utility will first restore some of the Registry settings, then it will launch the eDirectory installation. The installation will copy the files and then you must select the reboot option. After rebooting, users will have access to the migrated domains.
The MODSCHEMA.LOG file contains the results of all schema extensions that are applied when an eDirectory server is installed into an existing tree. Each line of the log states which class/attribute is being added/modified and gives the status of the modification attempt.
This log is created or overwritten each time the install process is run, so it only represents the results of the last attempt. In addition to the eDirectory schema extensions, this log contains the results of any other schema extensions (such as LDAP or SAS) applied by the DSINSTALL front end prior to adding the new eDirectory server.
This log will not be generated when a standalone server is installed or if the version of the target server is NDS 7.01 or later.
The first part of the log lists environment variables that are set. The second part contains status messages documenting the eDirectory installation process.