Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
18<strong>Troubleshooting</strong> on Windows<br />
• Section 18.1, “The <strong>eDirectory</strong> for Windows Server Won’t Start,” on page 95<br />
• Section 18.2, “The Windows Server Can’t Open the <strong>eDirectory</strong> Database Files,” on page 95<br />
• Section 18.3, “Restoring <strong>eDirectory</strong> on Windows after an Emergency Repair,” on page 96<br />
18.1 The <strong>eDirectory</strong> for Windows Server Won’t<br />
Start<br />
If the <strong>eDirectory</strong> server fails to start when you boot the Windows server, a message will notify you<br />
that the service failed to start.<br />
If there are no other <strong>eDirectory</strong> database replicas, users can't log in.<br />
If there are other replicas, logging in might be slow and you will see communication errors and<br />
synchronization errors on the servers holding those replicas.<br />
• The <strong>eDirectory</strong> server entries in the Windows Registry might have been edited, or the Windows<br />
Registry might be corrupt.<br />
• <strong>eDirectory</strong> database files might have been corrupted or deleted.<br />
• If the <strong>eDirectory</strong> server can’t start because another service didn’t start, you can get more<br />
information from Start > Programs > Administrative Tools > Event Viewer.<br />
You’ll need to resolve the related-service problem before starting the <strong>eDirectory</strong> server.<br />
• The Registry or <strong>eDirectory</strong> executable files are corrupted or lost. Run the SAMMIG utility in<br />
the system directory. Select Uninstall NDS on Windows NT and include new <strong>eDirectory</strong><br />
information in the NT domain. Continue with the Uninstall until completed. Then restart<br />
sammig.exe and proceed to install <strong>eDirectory</strong>.<br />
• Database files have been corrupted or deleted. If the <strong>eDirectory</strong> server comes up on the NT<br />
server but the service can’t open the <strong>eDirectory</strong> database files, see Section 18.2, “The Windows<br />
Server Can’t Open the <strong>eDirectory</strong> Database Files,” on page 95.<br />
• The <strong>eDirectory</strong> server is not connected to a hub or switch or directly to a workstation (using a<br />
crossover cable). Connect the server to a hub or switch.<br />
18.2 The Windows Server Can’t Open the<br />
<strong>eDirectory</strong> Database Files<br />
If the <strong>eDirectory</strong> server can’t open the database files, a message on the Windows server will notify<br />
you.<br />
If there are no other database replicas, users can't log in.<br />
18<br />
novdocx (en) 22 June 2009<br />
<strong>Troubleshooting</strong> on Windows<br />
95
Change language