Novell Home

My Favorites

Close

Please to see your favorites.

Tips and Tricks in Troubleshooting iManager 1.5

(Last modified: 24Jan2003)

This document (10076889) is provided subject to the disclaimer at the end of this document.

goal

Tips and Tricks in Troubleshooting iManager 1.5

symptom

An error occurs while using iManager

fix

iManager is a complex environment.  This document will give some good starting points to look at when troubleshooting errors received in iManager.

Web browser:
What version of browser is being used?
- Microsoft Internet Explorer 5.5 or later is the recommended browser
- Netwscape 6.2 or later can be used in simple mode only
--- Simple mode is accessed by going to http://serveraddress:port/eMFrame/Simple.html
----">http://serveraddress:port/eMFrame/Simple.html
----
I.E.  http://10.10.10.1:2200/eMFrame/Simple.html (on Netware)

Is SSL setup and working correctly for the browser?
- Are you using HTTP or HTTPS?  For HTTPS, SSL/NTLS must be working.
-- Try going to http://serveraddress:8008 (on Netware)
-- Try going to https://serverip:8009 (on Netware or 443 on Windows/Unix)

Web server:
Can you reach the web server port?
--Default Ports:
---Windows/Unix: 80 or (8000)
---Netware with Enterprise Server: 51080/51443
---Netware with Apache: 80/443
---Netware must go through port 2200 by default

Check for port conflicts.  In NDSiMonitor, check configuration management.
For Win32, check the HTTP stack object / other tab for configuration settings. 

Web app server / Java servlet Gateway:
Is the Tomcat port bound?
--Port 8080 for Win32
--Type java -show in Netware.  There should be one and only one Tomcat thread.

Can you get the iManager login screen? 
Tomcat is required in order to get the login screen, however tomcat is not fully used yet at this point.

Is the Jakarta / Apache / IIS service running for Win32?

If install fails, set Java environment variables and reinstall.  Tomcat must know where to find Jclient.
Java_home,Tomcat_home,Ld_library_path
On NW – tomcat\bin\tomcat33.ncf – initializes Tomcat

Webaccess / Emframe:
Are the /webaccess/emframe files and directories present?
Check for case sensitivity

Jclient:
Is Java running?
On NW6, check the logger screen for jclient errors.
Jclient on UNIX uses NICI.  Is NICI working?

HTTP Stack:
On NW, is HTTPSTK.NLM loaded?
Set SADMIN password.  Allow access to NRM/ndsimon without eDir available by holding password in an encrypted file on the server.
NW – Access NRM, configure button, set sadmin password.
Win32 – https://serverip:8010/dhost - set sadmin password.

SOAP/Embox:
In NDS iMonitor check Agent Configuration for bound ports that are bound to SOAP.
Make sure embox.nlm / embox.dlm are running.

For additional information on eDirectory 8.7, please see the following solution.  NOVL81742  - eDirectory 8.7 Readme Addendum

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10076889
  • Solution ID: NOVL84130
  • Creation Date: 19Nov2002
  • Modified Date: 24Jan2003
    • NovellBeta

      Management Products

      NetWare

      eDirectory

Did this document solve your problem? Provide Feedback