Chapter 3 Troubleshooting Your Installation

This chapter contains information on troubleshooting NT and Unix installations of Enterprise Server. It contains the following sections:

• Troubleshooting All Platforms
• Troubleshooting Windows NT
• Troubleshooting Unix

Clients can't locate the server. First, try using the hostname. If that doesn't work, use the fully qualified name (such as www.domain.com), and make sure the server is listed in DNS. If that doesn't work, use the IP address.

The port is in use. Most likely, you didn't shut down a server before you migrated the settings from a previous version. Shut down the old server, then manually start the new one.

I've forgotten the administration user name and password. In the https-adminserv/config directory in your server root directory, edit the admpw text file, which contains a line of text similar to the following:

The text before the colon is the administration user name (in this case, admin); the text following the colon is the password, which is encrypted.

I've installed Enterprise Server, but the configuration pages do not have all the tabs and configuration pages shown in the documentation. If you did not choose to install an Enterprise Server component, it will not appear in your Server Manger forms. For example, if you did not choose to install the Web Publishing component, the Web Publishing tab will not appear on the Server Manager page. If you did not install all the components you wanted during your initial installation, you can rerun the installer, choosing any components you didn't install already.

After installing Enterprise Server, I tried to create a new Netscape Enterprise Server instance but got the following error message:
"File System Error: InitTree /conf_bk/backups.conf failed (unknown early startup error)". The problem may be caused by an attempt to create an instance of Enterprise Server in an NFS (Network File System) mounted partition. Try a new installation in a non NFS mounted partition.

I installed Java Server Support, but I do not have a JDK or JRE installed. In order for Java support to work, you must have a JRE or JDK installed. If not, your server may not start, or may start but generate errors when you try to run Java. To correct this problem, run the Enterprise Server installation program again, and choose to install the JRE, or install a JDK and point your server to it using the Configure JRE/JDK Paths page on the Servlets tab.For more information on JRE and JDK, see Installing a Java Developer's Kit.

The installation could not proceed.
Error: Can't open file for writing.
Can't write to file filename. The error was error code 32. Make sure you don't already have a web server running on your system.

The following message appeared when installing Enterprise Server:
confhttp: LODCTR returned error code 112. The LODCTR utility is used to set up performance monitoring-related keys in your Windows NT registry. Error 112 means that it ran out of space either on your hard disk or in the registry. You should first make sure you have plenty of free space on your hard disk; if you do, then Windows NT may have filled up its registry. You can check this by going to your control panels, opening System, clicking the Performance tab, and clicking Change in the Virtual Memory section. The window that comes up shows the current registry size and the maximum registry size; if current is near maximum, then raise the maximum setting, reboot, and try installing Enterprise Server again.

Then close REGEDT32.EXE and start the installation over; it should work fine this time.

I couldn't access the server after installing it and restarting. You need to have a static IP address for Enterprise Server to work properly. If you are using DHCP, the installation process writes the IP address used by your system at the time of installation to magnus.conf. If your IP address changes, you will not be able to access your server. To get your server to work temporarily, edit magnus.conf so that the address specified is your current IP address. To find your IP address, type ipconfig at the command line. The permanent fix is to get a static IP address.

I couldn't enable Web Publishing or create search collections after migrating from Enterprise Server 3.x to 4.x.. Check if there is a vdk200.dll file in your winnt/system32 directory. If there is, rename it or delete it.

The server is slow and transfers take too long. If you log accesses through SYSLOG, you might encounter reduced performance. Switch to using the server's error log files instead.

I have Enterprise Server and Netscape Application Server installed. After I migrated my Enterprise Server, my new Enterprise Server instance wouldn't start. Because migration does not migrate changes made to the start script, you will need to edit your start script to restore the Application Server information. Edit the LD_LIBRARY_PATH in your migrated server's start script to correctly to pick up all the Application Server libraries.