Novell Home

My Favorites

Close

Please to see your favorites.

Troubleshooting -641 or -783 Errors Starting an IDM driver - eDirectory fails to load (vrdim)

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

Environment


Novell Identity Manager 3.0.1
Novell Identity Manager 3.5
Novell Identity Manager 3.5.1
Novell Identity Manager 3.6
Novell Identity Manager 3.6.1
Novell Identity Manager 4.0
Novell Identity Manager 4.0.1
Novell Identity Manager 4.0.2

Situation

When trying to start an IDM driver through iManager, receive the error message: "Unable to start the driver, error: -641 "

When trying to start an IDM driver through iManager, receive the error message: "Unable to start the driver, error: -783 "

Same error codes (-641 and -783) seen when trying to start the driver through Designer

Search:  783 vrdim edirectory fails to start load-783 641 641  

Resolution

This issue can have several different causes. The errors just mean that the main IDM engine is not able to load properly when eDirectory loads.

The first step is to try rebooting the server that IDM/eDirectory is running on.  This has resolved the issue in a number of cases.

The second step is to make sure that no security or auditing software is involved.  LSM (SELinux, AppArmor or other similar programs) or auditing software such as Novell Audit can cause this problem.  Often the server with the auditing program will not be responding due to some problem such as a full disk.  Any problem with this type of program will cause the 783 error.
On NetWare check for a file sys:\etc\logevent.cfg and on linux check for a file /etc/logevent.conf  These files can point to auditing software that is tied into the server.

Troubleshooting steps per platform below:

IDM engine running on Windows Platform:

- IDM is installed in the same directory where eDirectory's dlms are (by default, C:\Novell\NDS)
01) Stop the eDirectory service
02) Move the file “dirxml.dlm” from the directory where eDirectory is installed
03) Start the eDirectory service
04) After eDirectory finishes loading, start DSTRACE.dlm
05) Go to the 'Edit' menu, then select 'Option'
06) Set ONLY the flags 'DirXML', 'DirXML Drivers', 'Misc Other'. Uncheck all the others and hit 'OK'
07) Go to the 'File' menu, then select 'New', then enter a filename for your trace file
08) Move the file “dirxml.dlm” back to its original location
09) Close/reopen the eDirectory services console
10) Select dirxml.dlm and hit the Start button
11) The trace file will show messages related to why the VRDIM module (IDM Engine) won't start

IDM engine running on Linux/Solaris/AIX Platform:

01) Stop ndsd with the command "/etc/init.d/ndsd stop" (without the double-quotes)
02) Move the libvrdim.* files from their original directory to a different directory
     in eDirectory 8.7.3.x they reside at /usr/lib/nds-modules/
     in eDirectory 8.8.x 32 bit: they reside at /opt/novell/eDirectory/lib/nds-modules/
     in eDirectory 8.8.x 64 bit: they reside at /opt/novell/eDirectory/lib64/nds-modules/
03) Start ndsd with the command "/etc/init.d/ndsd start" (without the double-quotes)
04) Start ndstrace
05) Within ndstrace, type:
    set ndstrace=nodebug
    set ndstrace=+time
    set ndstrace=+tags
    set ndstrace=+misc
    set ndstrace=+dxml
    set ndstrace=+dvrs
    ndstrace file on
06) Leave ndstrace it running on screen
07) Move the libvrdim.* files back to their original location
08) Back on the ndstrace screen, type "load vrdim"
09) After you see the errors, stop ndstrace. The trace file will show messages related to why the VRDIM module (IDM Engine) won't start

Additional Information

Those steps will show you exactly what the engine is doing as it loads, as well as all jvmloader related messages. Somewhere there you probably will have the exact problem, and after that the -783 will happen.

  There are several possible causes for the error, some are listed bellow with suggestions to help fix and/or track them further:
 
- Cause:  Installing Novell Identity Manager, versions 3.5.1 or 3.6 or 3.6.1, on a server that already has eDirectory 8.8.5 ftf1 will cause issues when IDM tries to load. Drivers will not start and give the errors -641 or -783.  Running ndstrace with +DXML and +DVRS flags will show the message:
DirXML JVM interface initialization failed <failed, -299 (0xfffffffffffffed5)>, unloading DIRXML
Suggestions: The easy fix in this case is to install eDirectory 8.8.5 ftf4.  See TID 7004299 for details on this problem.

- Cause: Corruption in the association between the driverset and the server
  Suggestions: The easy fix in this case is to remove the association between the driverset and the server, cycle ndsd, add the association back again

- Cause: Damage/corruption in the DirXML-ServerKeys attribute that resides in the local DIB's Pseudo-Server object
   Suggestions: 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.
- Cause: Using Dib Clone or dsbk will cause damage or corruption in the DirXML-ServerKeys attribute that resides in the local DIB's Pseudo-Server object
  Suggestions: 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.

- Cause: Misconfiguration of the JVM heap sizes
  Suggestions: This shows in the +misc flag at ndstrace. All jvmloader messages come under the MISC flag on Linux/Unix, and under the MISC OTHER flag on dstrace.dlm (Windows). Unfortunately there is no way of seeing them on Netware ( but we can always check the SYS:/ETC/JAVA.CFG file there)

- 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)
  Suggestions: This is by far the hardest to track down properly, but here are some 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 those dependencies as well.  The checkbin.sh script can help greatly when checking dependencies, it is part of the ntsutils package that can be downloaded here: http://www.novell.com/communities/node/2332/supportconfig-linux
    > use strace / ltrace to track what is happening. strace works on scripts, so that will probably be 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 C knowledge
    > For a quick solution, reinstall IDM on top of itself. That will simply overwrite the libraries/rights. If you run IDM 3.0.1 or 3.5.1 installer with the -DCLUSTER_INSTALL="true" option, it will only lay down the rpms again without extending the schema (even though it does show the messages that its doing that).

If the above still does not resolve the issue, ensure the jclnt symbolic link is pointed to the correct directory.  View TID 7006778 for further information.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7002449
  • Creation Date:26-JAN-09
  • Modified Date:08-JUL-14
    • NetIQIdentity Manager

Did this document solve your problem? Provide Feedback