12.3 Troubleshooting an Identity Server Import and Installation

12.3.1 Identity Server Fails to Import into Administration Console

Check for the following points if you have installed your Administration Console and Identity Server on different machines:

  • The following ports should be opened between the machines:

    • 8444
    • 1443
    • 1289
    • 524
    • 636

    Identity Server firewall also needs to have ports 8080 and 8443 open between the server and the clients for the clients to log into Identity Server. For more information about firewalls and ports, see Setting Up Firewalls.

  • Time needs to be synchronized between the two machines. Ensure that both machines are configured to use a Network Time Protocol server.

  • If firewalls and time synchronization do not solve the problem, run the reimport script. See Reimporting Identity Server for instructions.

12.3.2 Reimporting Identity Server

  1. Verify that Administration Console is up by logging into Administration Console.

  2. Verify that you can communicate with Administration Console. From the command line of Identity Server machine, enter a ping command with the IP address of Administration Console.

    If the ping command is unsuccessful, fix the network communication problem before continuing.

  3. In Administration Console, delete Identity Server.

    For more information about how to delete Identity Server in Administration Console, see Identity Server Advanced Configuration in the NetIQ Access Manager 4.3 Administration Guide.

  4. On Identity Server machine, change to the jcc directory:

    Linux: /opt/novell/devman/jcc

    Windows: \Program Files (x86\Novell\devman\jcc

  5. Run the reimport script for jcc:

    Linux: ./conf/reimport_nidp.sh jcc

    Windows: conf\reimport_nidp.bat jcc

  6. Run the reimport script for Administration Console:

    Linux: ./conf/reimport_nidp.sh nidp

    Windows: conf\reimport_nidp.bat nidp <admin>

    Replace <admin> with the name of your administrator for Administration Console.

  7. If these steps do not work, reinstall the device.

12.3.3 Check the Installation Logs

If Identity Server fails to install, check the installation logs.

Linux Installation Logs

Installation logs are located in the /tmp/novell_access_manager directory. Check them for warning and error messages.

Table 12-1 Installation Log Files for the Linux Identity Server

Log File

Description

inst_nids_<date&time>.log

Contains the messages generated for Identity Server module.

inst_main_<date&time>.log

Contains the Tomcat messages generated during the installation.

inst_jcc_<date&time>.log

Contains the messages generated for the communications module.

inst_audit_<date&time>.log

Contains the messages generated for the auditing components.

inst_devman_<date&time>.log

Contains the messages generated for the interaction between Identity Server and Administration Console.

Windows Installation Logs

Installation logs are located in the \Program Files\Novell\Tomcat\webapps \nps\WEB-INF\logs\install directory. Check them for warning and error messages.

Table 12-2 Installation Log Files for the Windows Identity Server

Log File

Description

basejar_InstallLog.log

Contains the messages generated when installing Identity Server JAR files.

base_InstallLog.log

Contains the messages generated during the installation of Identity Server.

nauditjar_InstallLog.log

Contains the messages generated when installing the Novell Audit JAR files.

nauditjar_InstallLog.log

Contains the messages generated for the auditing components.

NIDS_Pluginjar_InstallLog.log

Contains the messages generated when installing Identity Server plug-in JAR.

NIDS_Plugin_InstallLog.log

Contains the messages for the plug-in component.

NMASjar_InstallLog.log

Contains the messages generated when installing the NMAS JAR files.

NMAS_InstallLog.log

Contains the messages for the NMAS component.