Http 500 Errors; Error Messages - Novell IMANAGER 2.7.3 - ADMINISTRATION Administration Manual

8.1.2 HTTP 500 Errors

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:
Tomcat has not fully initialized after a reboot.
Tomcat has failed to start.
Wait a few minutes and try again to access iManager. If you still receive the same errors, verify the
status of Tomcat.
Checking the Status of Tomcat
1 Restart Tomcat.
For information about restarting Tomcat, see
2 Check the Tomcat logs for any errors.
The log file is located in the
Windows platforms. On UNIX and Linux, the logs are named
localhost_log.date.txt
On NetWare, errors appear on the logger screen.

8.1.3 601 Error Messages

The object name entered could not be found in the context specified.
Some possible causes:
Contextless login might be disabled.
Your User object might not be in the configured search containers list. Either ask your
administrator to add your user location to the contextless login search containers or log in with
a full context.
8.1.4 622 Error Messages
The NDS password has been disabled in the Universal Password policy. This may also manifest
itself with a 222 Error Message.
You can avoid this error with iManager Workstation by installing the NMAS client, which allows
iManager to utilize the Universal Password authentication mechanism rather than eDirectory's
legacy authentication process.
8.1.5 632 Error Messages
This error is a system failure with several
nwec/nwec_enu/nwec_ids_t_err_system_failure.html).
8.1.6 634 Error Messages
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.
"Starting and Stopping Tomcat" on page
$tomcat_home$/logs
; on Windows, the log files are named
possible causes (http://www.novell.com/documentation/
directory on the UNIX, Linux, and
catalina.out
and
stderr
94.
or
.
stdout
Troubleshooting 89