CTX125158 – Case Study: IMA Startup Error Because of the Data Store – Citrix Knowledge Center

Problem Definition

The IMA service running is necessary for the discovery of the XenApp server and proper XenApp functionality.

Requirements

Basis XenApp Administration Skills

Background

The Citrix IMA service is required to be running on each XenApp server for the discovery process to work correctly and normal operability of XenApp.

Using the registry, you can use the CurrentlyLoadingPlugin string to identify if the issue is related to the data store.

Troubleshooting Methodology

The steps to complete the task:

Check to see if the IMA service is started.
Attempt to start IMA service; the error message below might appear.

“Windows could not start the Citrix Independent Management
Architecture on Local Computer. For more information, review the
System Event Log. If this is a non-Microsoft service, contact the
service vendor, and refer service-specific error code 0.”

Use the registry editor and look at the following registry string:
HKLMSOFTWARECitrixIMARuntimeCurrentlyLoadingPlugin
Note: In Windows 64-bit operating systems this registry key is located under HKLMSOFTWAREWow6432NodeCitrixIMARuntimeCurrentlyLoadingPlugin

If the IMA service fails to start and this value is blank or not present, the IMA service could not connect to the data store or the local host cache is missing or corrupt.

Procedure 1

Check your database connectivity and authentication by using the Windows OBDC Configuration in you Administrative tools.
Select the System DSN Data Source and click Add to add a new data source.

Select Next on main DSN Configuration Prompt.

Select Next on the Authentication selection.

This example produced the following error:

This showed that the database authentication and db_owner roles needed to be set on the database in the SQL server.
Address the connectivity issue and attempt to restart the IMA service.

Procedure 2

Run the XenApp Role manager in XenApp 6.0 to reconfigure your XenApp Configuration.
Select Edit Configuration in the XenApp selection.
Click Create new server farm or Join an existing server farm.
Creating a new database and Farm will rule identify existing farm as problematic.
Join an existing working farm if you have a working farm.
Note: Joining an existing farm should be used if you have a development or test farm. Joining a production farm is not recommended.

To address the issue required creating a new server farm.
When the server farm was recreated and configured, the IMA service started and the appropriate registry entries were present.