17.4 Identity Manager Driver Errors

The following errors might occur with Identity Manager drivers:

641 Unable to start the driver

Source: DSTrace screen.
Explanation: You might receive this error message when you start a Identity Manager driver through either iManager or Designer.
Possible Cause: There are several causes. The error means the Identity Manager engine cannot load properly when eDirectory loads.
Action: Perform the following troubleshooting steps on Identity Manager engine to know what exactly the engine is doing when it is loaded, and all jvmloader related messages.

Identity Manager engine running on Windows:

NOTE:Identity Manager is installed in the directory where eDirectory's dlms are present, by default, C:\Novell\NDS.

  1. Stop the eDirectory service.

  2. Move the dirxml.dlm file from the directory where eDirectory is installed.

  3. Start the eDirectory service.

  4. After eDirectory is loaded, start DSTRACE.dlm.

  5. Click Edit > Option.

  6. Set the following flags:

    • DirXML
    • DirXML Drivers
    • Misc Other

    Unselect all other options and click OK.

  7. Click File > New and specify a filename for your trace file.

  8. Move the dirxml.dlm file back to its original location.

  9. Close/reopen the eDirectory services console.

  10. Select dirxml.dlm and click Start.

The trace file contains the messages related to why the VRDIM module (IDM Engine) does not start.

Identity Manager engine running on Linux/Solaris/AIX:

  1. Stop ndsd by using the following command:

    /etc/init.d/ndsd stop

  2. Move the libvrdim.* files from their original directory to a different directory.

    In eDirectory 8.8.x, the files are present in the /opt/novell/eDirectory/lib/nds-modules/ directory.

  3. Start ndsd by using the following command:

    /etc/init.d/ndsd start

  4. Start ndstrace.

  5. In the ndstrace, type the following:

    • set ndstrace=nodebug
    • set ndstrace=+time
    • set ndstrace=+tags
    • set ndstrace=+misc
    • set ndstrace=+dxml
    • set ndstrace=+dvrs
    • ndstrace file on
  6. Let ndstrace run on the screen.

  7. Move the libvrdim.* files back to their original location.

  8. In the ndstrace screen, type the following:

    load vrdim

  9. After you see the errors, stop ndstrace.

The trace file contains the messages related to why the VRDIM module (IDM Engine) does not start.

You can specify a different location for the trace file. To see the contents of a trace file, click Edit Properties > Misc > Trace File.

After you have performed the specified troubleshooting steps, you might encounter the 783 Unable to start the drivererror.

Level: Error

783 Unable to start the driver

Source: DSTrace screen
Explanation: You might encounter this error message after performing the Action specified under 641 Unable to start the driver.
Possible Cause: There are several possible causes for the error. The following is a list of few possible causes with suggestions to help fix and/or track them further:
Possible Cause: Corruption in the association between the driver set and the server.
Action: Remove the association between the driverset and the server, cycle ndsd, and add the association back again.
Possible Cause: Damage/corruption in the DirXML-ServerKeys attribute that exists in the local DIB's Pseudo-Server object.
Action: DSDUMP (only done by Novell support) is needed to remove the attribute with pre-IDM 3.6. Use the new command within the dxcmd utility for IDM 3.6 and later.
Possible Cause: Using Dib Clone or dsbk will cause damage or corruption in the DirXML-ServerKeys attribute that exists in the local DIB's Pseudo-Server object.
Action: DSDUMP (only done by Novell support) is needed to remove the attribute with pre-IDM 3.6. Use the new command within the dxcmd utility for IDM 3.6 and later.
Possible Cause: Misconfiguration of the JVM heap sizes.
Action: This is shown in the +misc flag in ndstrace. All jvmloader messages exist under the MISC flag on Linux/Unix, and the MISC OTHER flag on dstrace.dlm (Windows). You cannot see the jvmloader messages on Netware. But you can always check the SYS:/ETC/JAVA.CFG file.
Possible Cause: Corruption/damage/insufficient rights on the libraries IDM requires in the box (check the install log, also do an rpm -V on the IDM packages)
Action: Try the following options:
  • Use rpm -V liberally against all IDM-related libraries. The command line works well for that:

    rpm -qa | grep DXML | xargs rpm -V

  • ldd your IDM libraries to see the dependencies they have, and check the dependencies also. The checkbin.sh script can be of great help when checking dependencies. It is part of the ntsutils package that can be downloaded from the following location:

    http://www.novell.com/communities/node/2332/supportconfig-linux

  • Use strace/ltrace tool to track what is happening. Because strace works on scripts, it is the best option. ltrace can only be run against binary files. These tools provide a lot of information, and quite a bit of it requires basic knowledge of C programming language.

  • Reinstall Identity Manager on top of itself. The process overwrites the libraries/rights.

Level: Error

Identity Manager Driver that is deleted without stopping, and re-created with the same port number fails to start

Source: DSTrace screen
Explanation: Delete a driver without stopping it, re-create the same driver with the same port number, and start the driver. The driver fails to start.
Possible Cause: IDM does not release the used port of a driver if the driver is deleted without stopping.
Action: Edit the driver to use another port. The driver starts.