// you're reading...


Citrix XenApp 6.0 Hotfix 003 problem: MFCOM Service hangs on “Starting”

One of my newly installed Citrix XenApp 6.0 servers has not been able to shutdown completely. The installation of several hotfixes was necessary to shutdown the server completely. I created this blog entry because the installation of these hotfixes was a kind of a nightmare. Please read:

It is very important to install hotfix 002 as the first hotfix – especially if the Citrix Licensing component is installed on the same server. You can download this hotfix here: http://support.citrix.com/article/CTX126123 – Reboot!

As a next step, you can download and install the hotfix 003 (XA600W2K8R2X64003) for the shutdown problem. See here:http://support.citrix.com/article/CTX126211 – Reboot!

After the reboot I noticed that the “MFCOM Service” was hanging on status “Starting” and the IMA Service was not starting at all – and the nightmare started!

I tried several things including a re-installation of the Installation Manager (found that in one of the forums); nothing helped. Many users with the same problem were only able to solve it by completely reinstalling the whole Citrix installation.

After a while, I found one article describing that an empty “lmalhc.dsn” file could be the source of the problem. I modified that solution a little bit and voilà – all services were starting again!

Here is the solution:

  1. Execute cmd with administrative privileges
  2. Execute “dsmaint recreatelhc”
  3. Check if content of “C:\Program Files (x86)\Citrix\Independent Management Architecture\Imalhc.dsn” is not empty. If empty, then copy and paste the following content:
  4. [ODBC]
    DRIVER=Microsoft Access Driver (*.mdb)
    FIL=MS Access
    DBQ=C:\Program Files (x86)\Citrix\Independent Management Architecture\Imalhc.mdb
  5. Use the task manager to kill the “mfcom.exe *32″ process (if running)
  6. Execute “dsmaint recreaterade”
  7. Reboot server


4 Responses to “Citrix XenApp 6.0 Hotfix 003 problem: MFCOM Service hangs on “Starting””

  1. Just to make a quick point. Usually the MFCOM service won’t fully start after a corrupted or incomplete install of a hotfix. So even if you do this, it won’t work until after you successfully install the hotfix. I usually recommend stopping all Citrix services prior to installing any hotfix (especially MFCOM).

    Posted by Yangzhi Zhao | 9. March 2011, 17:59
  2. Hi….do you still feel it is important to install this hotfix XA600W2K8R2X64060 (which replaced XA600W2K8R2X64002) first ? It does say

    “Installing hotfixes or performing a repair on the base product for Citrix XenApp 6 for Windows Server 2008 R2 can inadvertently remove the Citrix Licensing component, if present, from the system. This fix prevents the Citrix Licensing component from being removed when installing subsequent hotfixes.”


    Posted by Andrew Parry | 25. August 2011, 10:10
  3. just wanted to point out that recreating the farm is what fixed it for me. This happened to me with my very first XA 6.5 server.

    thanks for all your contributions.

    Posted by Jim | 13. January 2012, 22:06
  4. I had the same problem in my company after creating a XenApp 6.5 farm. The IMA service and the MFCOM service did not run after joning the server to the farm and rebooting the server. Both services are running with the Network Service account.

    dsmaint config /user:domain\username /pwd:password

    After that both services are running fine, also after rebooting the server.

    Posted by Frank Abdoelhafiezkhan | 20. June 2012, 09:03

Post a comment