You might encounter the following error messages when authenticating to iManager. Each error message section discusses possible causes.
If you receive a 404 error the first time you attempt to access iManager, you need to verify the ports that Apache is running on. Depending on how you installed iManager and whether you chose to use Apache or IIS, the configuration file locations will vary. Apache uses either the httpd.conf file or the ssl.conf file. Refer to Microsoft’s documentation for information on IIS port settings.
If you receive an internal server error or servlet container error (either unavailable or being upgraded), iManager is having one of two problems with Tomcat:
Wait a few minutes and try again to access iManager. If you still receive the same errors, you need to verify the status of Tomcat and, if the error persists, the status of Apache.
Restart Tomcat.
Check the Tomcat logs for any errors.
The log file is located in the $tomcat_home$/logs directory on the UNIX, Linux, and Windows platforms. On UNIX and Linux, the logs are named catalina.out or localhost_log.date.txt; on Windows, the log files are named stderr and stdout.
On NetWare®, errors appear on the logger screen.
Restart Apache.
Check the Apache log files for errors.
The files are located in the $apache_home$/logs directory.
The target server does not have a copy of what the source server is requesting, or the source server has no objects that match the request and has no referrals on which to search for the object.
Some possible causes:
If the tree name fails, use the IP address.
This error is a system failure having any of several possible causes.
The object name entered could not be found in the context specified.
Some possible causes:
An invalid password was used, authentication failed, one server tried to synchronize with another one but the target server’s database was locked, or a problem exists with the remote ID or public key.
Some possible causes: