×

IDMWORKS Blog

How To Fix iMonitor On Windows 2012 Server


NetIQ iMonitor Failing To Load (Notes From The Field)
Here are some notes from the field when iMonitor failed to load after applying eDirectory 8.8.8 Patch 7 on a Windows Server 2012 R2.

Background Information
NetIQ iMonitor is a web-based tool that provides an alternative way to run many of the traditional server-based eDirectory applications such as DSRepair, DSBrowse, DSTrace, DSDiag, and other tools to monitor the health of a NetIQ eDirectory installation.  iMonitor allows remote monitoring via a web browser from any location where the eDirectory server is accessible. More information about iMonitor can be found in the eDirectory documentation accessible on NetIQ’s website.  

eDirectory is installed to support NetIQ’s Identity Manager product.  After applying eDirectory patch 7 during the installation of Identity Manager 4.5.3 and eDirectory 8.8.8 in a Windows 2012 R2 Server environment, the iMonitor server was no longer running.

Troubleshooting Steps
iMonitor is typically accessed using the following web address https://[server name or server ip]:8030.  Running a “netstat -a” command from a windows command prompt revealed the server was no longer listening on port 8030, the default port for iMonitor.  

An important point to remember is iMonitor is running on an independent web server hosted by the eDirectory (or ndsd) process; iMonitor is not tied to any Tomcat instance or other web server which may be used to run other web applications such as iManager.  Because iMonitor is tied to the eDirectory (or ndsd) process, the best place to troubleshoot iMonitor is by looking in the eDirectory logs or by running dstrace from the command line.  A capture of the dstrace from this particular server is shown below.  A few “error=200” messages appeared in the dstrace which didn’t reveal much other than the fact that iMonitor failed to initialize.

Resolution
Some of the network interface configuration settings of an eDirectory installation on a Windows server are stored in the config.acs file stored in the Dibfiles directory.  Knowledgebase article 3095848 (https://www.netiq.com/support/kb/doc.php?id=3095848) on NetIQ’s support site provides some additional information about modifying this file to ensure the proper NIC configuration.  

After the patch file was applied, the [NCP Engine/Transport/Enum] section where the configuration lines for the network interface are stored were missing.  The following line indicated there should be two additional lines with additional configuration information for the network interface: [NCP Engine/Transports/Enum] = 0x00000002.  However, the two lines (TCP & UDP configurations) which should have started with [NCP Engine/Transports/Enum/000] & [NCP Engine/Transports/Enum/001] were missing.  

To resolve the problem these two lines needed to be recreated.  The lines could have been copied from another server in the replica and modified to have the proper network address (see the NetIQ KB article).  The lines could also be located in a backup file in the Dibfiles directory (installations will sometimes create backup files of the config.acs file).  

After successfully re-adding these two lines to the config.acs file and restarting eDirectory, iMonitor began working again.

Below is a DSTrace Capture which showed some errors initializing iMonitor. After the DSTrace section is a portion of the config.acs file with lines that need to exist for iMonitor to load properly.

DSTRACE CAPTURE:

iMon : DiagLoggerThread shutting down err=0
iMon : Init routine SAL Layer, error: 0
iMon : Init routine DSUtilities Library, error: 0
iMon : Init routine DDS Functions, error: 0
iMon : Init routine Sync Primitives, error: 0
iMon : Init routine DNS Primitives, error: 0
iMon : Init routine Comm Primitives, error: 0
iMon : Init: LMInit(), error: 0
iMon : Init: LMRegisterResourcePath(E:\Novell\NDS\lang), error: 0
iMon : Init: LMSetLangProviderCB(), error: 0
iMon : Init: LMRegisterBuiltInMsgTable(ndsimon), error: 0
iMon : Init: BuiltInMsgTable version is 2080.0
iMon : Init routine Language Primitives, error: 0
iMon : Init routine Primitive Functions, error: 0
iMon : Init routine Formatter Functions, error: 0
iMon : Init routine DLList Functions, error: 0
iMon : Init routine Reference Class, error: 0
iMon : Init routine NDS Attribute Flags, error: 0
iMon : Init routine Thread Manager, error: 0
iMon : Init routine Configuration, error: 0
iMon : Init routine Working Context Mgr, error: 0
iMon : Init routine Http Server Functions, error: 0
iMon : Init routine CIA Client, error: 0
iMon : Init routine Reporting, error: 200
iMon : Init routine NDS Health Monitor, error: 200
iMon : Init routine NDS Trace, error: 0
iMon : Init routine NDS Repair Functions, error: 0
iMon : Init routine Utility Launching Functions, error: 0
iMon : Init routine NDS Activity Functions, error: 0
iMon : Init routine NDS Agent Functions, error: 200
iMon : DiagLoggerInit err = 0
iMon : Init routine Diagnostic Logger, error: 0
iMon : Init routine Http Server Functions, error: 200

 

conifg.acs Sections to Check

[NCP Engine/Transports/Enum] = 0x00000002
[NCP Engine/Transports/Enum/000] = {0x00 0x00 0x00 0x06 0x00 0x02 0x0c 0x02 0x0d 0x0c 0x0b 0x0a}
[NCP Engine/Transports/Enum/001] = {0x00 0x00 0x00 0x11 0x00 0x02 0x0c 0x02 0x0d 0x0c 0x0b 0x0a}

[Http Server/HTTP/Default Port] == 0x00001f5c
[Http Server/HTTP/Bind Restrictions] == 0x00000002
[Http Server/HTTP/Transports/Enum] = 0x00000002
[Http Server/HTTP/Transports/Enum/000] = {0x00 0x00 0x00 0x06 0x00 0x02 0x5e 0x1f 0x00 0x00 0x00 0x00}
[Http Server/HTTP/Transports/Enum/001] = {0x00 0x00 0x00 0x06 0x00 0x17 0x5e 0x1f 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00}

[Http Server/HTTPS/Default Port] == 0x00001f5e
[Http Server/HTTPS/Authentication Requires TLS] == ?1
[Http Server/HTTPS/Transports/Enum] = 0x00000002
[Http Server/HTTPS/Transports/Enum/000] = {0x00 0x00 0x00 0x06 0x00 0x02 0x5e 0x1f 0x00 0x00 0x00 0x00}
[Http Server/HTTPS/Transports/Enum/001] = {0x00 0x00 0x00 0x06 0x00 0x17 0x5e 0x1f 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00}

Questions, comments or concerns? Feel free to reach out to us below, or email us at IDMWORKS to learn more about how you can protect your organization and customers.

Leave a Reply

Your email address will not be published. Required fields are marked *