Environment
NetIQ Identity Manager 4.02
Windows Server 2008R2 virtualised within VMWare server.
Situation
Unable to start any drivers from iManager.
The Windows eDirectory console showed that dirxml.dlm was not loaded. Attempting to start dirxml.dlm produced the following log from an iMonitor trace with the DirXML, DirXML Drivers and Misc Options enabled.
========================================
13:12:58 1E7C Drvrs: DirXML starting.
13:12:59 1E7C Misc: jvmload: No JVM module found
13:12:59 1E7C Misc: jvmload: Creating new JVM
13:12:59 1E7C Misc: jvmload: JavaVMInitArgs:
13:12:59 1E7C Misc: jvmload: version 10002
13:12:59 1E7C Misc: jvmload: nOptions 9
13:12:59 1E7C Misc: jvmload: -Djava.home=d:\Novell\NDS\jre
13:12:59 1E7C Misc: jvmload: -Xbootclasspath:d:\Novell\NDS\jre\lib\\alt-rt.jar;d:\Novell\NDS\jre\lib\\alt-string.jar;d:\Novell\NDS\jre\lib\\charsets.jar;d:\Novell\NDS\jre\lib\\deploy.jar;d:\Novell\NDS\jre\lib\\javaws.jar;d:\Novell\NDS\jre\lib\\jce.jar;d:\Novell\NDS\jre\lib\\jsse.jar;d:\Novell\NDS\jre\lib\\management-agent.jar;d:\Novell\NDS\jre\lib\\plugin.jar;d:\Novell\NDS\jre\lib\\resources.jar;d:\Novell\NDS\jre\lib\\rt.jar
13:12:59 1E7C Misc: jvmload: -Djava.ext.dirs=d:\Novell\NDS\jre\lib\ext
13:12:59 1E7C Misc: jvmload: -Djava.endorsed.dirs=d:\Novell\NDS\jre\lib\endorsed
13:12:59 1E7C Misc: jvmload: -Xverify:none
13:12:59 1E7C Misc: jvmload: exit
13:12:59 1E7C Misc: jvmload: extra info = 00000000DD7C2960
13:12:59 1E7C Misc: jvmload: -Xmx512M
13:12:59 1E7C Misc: jvmload: -Xms128M
13:12:59 1E7C Misc: jvmload: No JVM module found
13:12:59 1E7C Drvrs: DirXML JVM interface initialization failed <failed, -299 (0xfffffed5)>, unloading DIRXML
13:12:59 1E7C Drvrs: DirXML shutting down.
=========================
The trace indicates that no jvm module was found but
d:\Novell\NDS\jre\bin\server\jvm.dll did exist.
Windows Process Monitor (available from the Microsoft support site) was installed and procmon showed dhost.exe trying to access jvm.dll in the above location whenever dirxml.dlm was loaded from the eDirectory console.
Resolution
Checking the eDirectory cache configuration
iMonitor -> Agent Configuration -> Cache Maximum Size
showed that a maximum cache of 3GB was configured. Reducing this maxium cache to 1GB resolved the issue and allowed dirxml.dlm to load normally
Cause
We could not determine why this cache configuration caused an issue after many months of normal operation.
It was suspected that there may have been a virtual host configuration change or upgrade and that may have affected memory allocation with the guest.
In any case, a smaller cache configuration was a more appropriate setting in this environment.