Basic troubleshooting of an iManager 2.5 upgrade on NetWare 6.5.

  • 7006145
  • 27-May-2010
  • 26-Apr-2012

Environment

Novell NetWare 6.5 SP2
Novell eDirectory 8.7.3 for NetWare 6.5
Novell iManager 2.5

Situation

Upgraded iManager 2.02 to 2.5.
Questions and Troubleshooting a iManager 2.5 install on NetWare 6.5
Basic troubleshooting of an iManager 2.5 upgrade on NetWare 6.5.

Resolution

Basic Troubleshooting:

Try clearing the browser cache as well as the backend renderer.

- Shutdown Tomcat and Apache
- Delete the SYS:\TOMCAT\4\WORK\STANDALONE\LOCALHOST\NPS directory.  This will be re-populated on the next login.
- Clear out the browsers temporary files (cache) including off-line files
- Close all browser instances, bring up Apache and Tomcat,  re-open the browser and log back in.

Does the logger show that port 9010 is listening?  If not, please check to see that you can successfully bind to the server's secure ldap port: 636.  Has the LDAP secure port been verified by actually binding to it via ICE or some other ldap utility?

What kind of messages are in the iManager debug log?  for more information on setting up iManager debugging, see TID 7006107 - How to get an iManager 2.5 debug trace

Additional Information

For more issues and actions, please refer to the iMangaer 2.x Readme Addendum (TID 7006099)


Formerly known as TID# 10097089