Failed to initiate IMA Service on XenApp Server

Description

Independent Management Architecture Service (or IMA) is not starting on a XenApp server. The ODBC connection file does not show DRIVER= Microsoft Access Driver (*.mdb).

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

Troubleshooting Steps

Run the CDF trace(only selecting IMA modules). When trying to run the IMA, the following error is noticed in the trace.

828	1	2015/02/20 19:11:04.83639	1740	360	-1	system	hostidtable.cpp	1562	LSA_GetDecryptedString	5	CDF_ENTRY	LSA_GetDecryptedString - entry for keyName 'RADEOFFLINE_USERPASSWORD'
829	1	2015/02/20 19:11:04.83705	1740	360	-1	system	hostidtable.cpp	406	GlobalData_GetDecryptedString	1	CDF_ERROR	GlobalData_GetDecryptedString: Failed to read from LSA! error -1073741772
830	1	2015/02/20 19:11:04.83706	1740	360	-1	system	hostidtable.cpp	411	GlobalData_GetDecryptedString	5	CDF_ENTRY	GlobalData_GetDecryptedString - exit;
891	0	2015/02/20 19:11:06.25888	7052	7240	-1	support	IMA.cpp	176	ImaInit	1	CDF_ERROR	Failed to get local host record: 802D000Ch
892	0	2015/02/20 19:11:06.25888	7052	7240	-1	client	ima_pif_remoteaccess.cpp	171	InitiateRemoteAccess	1	CDF_ERROR	Failed to initiate IMA.

Run the Procmon tool. It is observed that it has the error for the dsmaint.exe to configure the DNS file and also LHC is not getting created.
The command to run the LHC works but it does not give an output indicating " LHC created successfully".
Run the API Monitor 32 bit on the XenApp 64 Bit server. Run 32 bit on the server as the XA 6.5 and 6.0 codes are written in 32 bit.
Run the API Monitor using the filter dsmaint.exe. It is observed that the entry %WINDIR%\system32\odbcjt32.dll was missing on to the server. The following screen shot illustrates example of the same in the working server.
Export the registry HKLM\Software\Wow6432Node\ODBC\ODBCINST.INI\Microsoft Access Driver(*.mdb) from the working server and import on to the non-working server.

It is noticed that on the non working server's ODBC connection file that the DRIVER is not equal to Microsoft Access Driver.

After you replace the file as mentioned, the LHC is recreated and this created the IMALHC.mdb file. The IMA started working.

Note: The Desktop Database Drivers are needed to execute the Microsoft Open Database Connectivity (ODBC) interface on Windows. These drivers are contained in one driver file, the odbcjt32.dll module that the ODBC driver manager module uses.
Export the registry HKLM\Software\Wow6432Node\ODBC\ODBCINST.INI\Microsoft Access Driver(*.mdb) from the working server and import on to the non-working server.

Problem Cause

Issue/Introduction

This article provides solution to when IMA is not running and ODBC connection does not show Driver=Microsoft Access Driver.

Welcome to "KB Articles"