CTX129526 – IMA does not Start with Two Network Interfacing Cards Enabled – Citrix Knowledge Center

Symptom When two Network Interface Cards (NICs) are enabled and one NIC does not have an IP address assigned to it, IMA fails to start. Cause This problem occurs if the server has the following value set in the registry to disable Automatic Private IP Addressing (APIPA): HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters/IPAutoconfigurationEnabled=0 Workaround The following workarounds can resolve this issue: Set IPAutoconfigurationEnabled=1 Note: You can apply this to all interfaces or each interface in the relevant GUID under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters subkeys. Caution! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your […]

Read more

The IMA Service Fails to Start After Restarting the XenApp Server

Symptoms After you restart a XenApp server, the IMA Service fails to start. The following error is displayed in the System Event Log. "Failed to load plugin C:Program FilesCitrixSystem32CitrixIMASubsystemsRADESessionSs.dll with error IMA_RESULT_FAILURE" Cause If the RADESessionSs.dll plugin is present in the IMA Subsystems directory, the RadeOffline.mdb file is either missing or corrupt. Resolution To resolve the preceding issue, complete the following procedure: Run the following command from the affected server to re-create the RadeOffline.mdb file, as shown in the following screen shot: Dsmaint recreaterade Restart the IMA Service after the RadeOffline.mdb file is re-created. More Information Refer to the Knowledge […]

Read more

Future Citrix Products Might Not Function Depending on the Date in the License File

Summary Future Citrix products might not function depending on the version of the license file on the license server. Background Citrix is using what is called Date Based Versioning for all future Citrix products. Each Citrix product has a hard coded date called a burn-in date which corresponds to that particular product’s release/build. The burn-in date for a product is likely around the Release to Manufacturing (RTM) date for that release. For example: The burn-in date for MetaFrame Presentation Server 3.0 is 2/27/04. Date Based Versioning is based on a comparison between the burn in date of a product and […]

Read more