Environment
Novell eDirectory 8.7.3 for Windows 2003
Novell eDirectory 8.8.x for Windows 2003
Situation
NOTE!!!!
MOVING THE DATABASE OF EDIRECTORY IS NOT SUPPORTED ON EDIRECTORY 8.7.X
This TID is still being published so that upgrade problems with later versions of eDirectory can be resolved after carrying out this procedure!
Upgrade from eDirectory 8.7.3.x to eDirectory 8.8.5 fails if DibPath is customized.
Error: A fatal error has occurred. eDirectory upgrade cannot continue due to lack of free disk space in the file system where DIB resides.
Resolution
The only version of eDirectory 8.8.x that a server can successfully be upgraded to when the database has been manually moved on the Windows platform is eDirectory 8.8.5.
Further, as the eDirectory database pointers are incorrect the upgrade may fail if the C: drive does not contain twice the database size in free space even though the actually drive holding the database has plenty. To resolve this condition so the upgrade may proceed:
1. Create an empty 'DIBFiles' folder under the installed eDirectory location then retry the upgrade.
Example: If the installed eDirectory location is C:\Novell\NDS and if DibPath is customized (such as E:\Novell\Dib\DIBFiles) then create a 'DIBFiles' folder under "C:\Novell\NDS" for the upgrade to be successful. After the upgrade is successful the 'DIBFiles' directory temporarily created under "C:\Novell\NDS" can be deleted.
Example: If the installed eDirectory location is C:\Novell\NDS and if DibPath is customized (such as E:\Novell\Dib\DIBFiles) then create a 'DIBFiles' folder under "C:\Novell\NDS" for the upgrade to be successful. After the upgrade is successful the 'DIBFiles' directory temporarily created under "C:\Novell\NDS" can be deleted.
Additional Information
Formerly known as TID# 10061028
Formerly known as TID# NOVL42312
Original TID contents are below. Do not attempt to relocate the eDirectory database unless you are eDirectory 8.8.5 or above!
Begin the process by making a good backup. Use the NDS Install Utility in the NDS Services Console to backup your NDS database.
Shutdown the NDS Server from "Control Panel | NDS Services".
Proceed by opening a command prompt and use "netstat -na | more" to make sure all NDS connections are closed. To see what ports your NDS server is running on, Open the "NDS Services" icon in Control Panel and select the "Transports" tab. The NDS server usually runs on TCP/UDP port 524.
Next, copy the NDS database directory structure to the new location (i.e. C:\NOVELL\NDS to D:\NOVELL\NDS) You can copy only the DIBFiles directory if desired, yet, it is recommended to keep all NDS related files together in the same directory structure.
Continue by opening the Registry Editor (REGEDT32.EXE or REGEDIT.EXE) and go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDS Server0\
Edit the string value from:
ImagePath="C:\NOVELL\NDS\ndsserv.exe" /DataDir="C:\NOVELL\NDS\DIBFiles" ds
To:
ImagePath="D:\NOVELL\NDS\ndsserv.exe" /DataDir="D:\NOVELL\NDS\DIBFiles" ds
Now verify that the NDS server path has been changed correctly. Open "Control Panel | Services | NDS Server" and verify the path to the executable.
Start the NDS Server from "Control Panel | NDS Services".
Finally, verify that ds.dlm and dsloader.dlm are in a "Running" status in the NDS Services console. You may also verify NDS Server activity by running "netstat -na | more" from a command prompt and look for activity on TCP/UDP port 524.
You may want to run a local repair of the NDS database and select "Validate stream syntax files" and "Perform database structure and index check" to make sure NDS has no errors.
Shutdown the NDS Server from "Control Panel | NDS Services".
Proceed by opening a command prompt and use "netstat -na | more" to make sure all NDS connections are closed. To see what ports your NDS server is running on, Open the "NDS Services" icon in Control Panel and select the "Transports" tab. The NDS server usually runs on TCP/UDP port 524.
Next, copy the NDS database directory structure to the new location (i.e. C:\NOVELL\NDS to D:\NOVELL\NDS) You can copy only the DIBFiles directory if desired, yet, it is recommended to keep all NDS related files together in the same directory structure.
Continue by opening the Registry Editor (REGEDT32.EXE or REGEDIT.EXE) and go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDS Server0\
Edit the string value from:
ImagePath="C:\NOVELL\NDS\ndsserv.exe" /DataDir="C:\NOVELL\NDS\DIBFiles" ds
To:
ImagePath="D:\NOVELL\NDS\ndsserv.exe" /DataDir="D:\NOVELL\NDS\DIBFiles" ds
Now verify that the NDS server path has been changed correctly. Open "Control Panel | Services | NDS Server" and verify the path to the executable.
Start the NDS Server from "Control Panel | NDS Services".
Finally, verify that ds.dlm and dsloader.dlm are in a "Running" status in the NDS Services console. You may also verify NDS Server activity by running "netstat -na | more" from a command prompt and look for activity on TCP/UDP port 524.
You may want to run a local repair of the NDS database and select "Validate stream syntax files" and "Perform database structure and index check" to make sure NDS has no errors.