Here is a possible solution
Omninames Fails on Fresh Install Under Windows NT Service Pack 4
This problem can occur with fresh installs under Service Pack 4. The symptom is that the Server starts but
complains that Omninames cannot be found. No clients can connect, and Omninames does not appear in the list of
running processes.
Run a command shell, and enter the command
“echo %OMNINAMES_LOGDIR%”.
Normally, this should return something like
“C:\Program Files\Lucent\BCMS Vu\Common” (depending on where the installation is).
If this
problem is occurring, you will probably see
“%OMNINAMES_LOGDIR%” returned.
To fix the problem, go to the control panel. Choose the System Control Panel, and click on the Environment tab.
Go to the “System Variables” list box, and find the variable called OMNINAMES_LOGDIR. Click on it, so that it
appears in the edit boxes at the bottom. Click the Set button. Now start a new command shell, and enter the
command “echo %OMNINAMES_LOGDIR%” again. It should now work properly – restart the Server.
NB: If there is no OMNINAMES_LOGDIR variable in the System control panel, you will need to add one. It
should point to the “Common” directory in your installation.
This problem is caused by NT4’s handling of environment variables – we do not know how an environment
variable can appear in the appropriate control panel and not be active, nor what changes are caused by the Set
button.
Please let me know if the information that was provided is helpfull.
Edwin Plat
A.K.A. Europe