The Citrix Delivery Services Console Discovery is unsuccessful when trying to administer one particular XenApp server, but is successful for all other XenApp servers in the Farm, even if the Console is run locally on that server.

All other Server and Farm functions without issues and users can access published and streamed resources without any issues.

Additionally, you might experience one or more of the following symptoms:

• The Citrix MFCom Service fails to start or the service is not displayed.

• The MFCom object is not displayed in the DCOM Configuration in the Windows Component Services snap-in.

• Custom scripts written using the MFCOM SDK are unable to administer the affected XenApp server, but are able to administer all other servers.

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

You must re-register MFCOM in Windows to resolve this issue.

To re-register MFCOM in Windows complete the following procedure: 

1. Navigate to the %programfiles(x86)%\Citrix\system32 folder from the command prompt.

2. Run the following command from the command prompt:
   mfcom /unregserver
   No output is displayed

3. Run the following command from the command prompt:
   mfcom /regserver

4. Run the following command from the command prompt:
   regsvr32 mfcomsrv.dll

5. Click OK.

6. Open the registry editor and navigate to the following entry:
   HKLM\SYSTEM\CurrentControlSet\Services\MFCom

7. Create a DWORD value with the following details:
   Name: ServiceSidType
   Data: 1

8. Restart the server.
   Verify if the Citrix MFCOM Service is displayed and has started.

Problem Cause

This error might occur if the Citrix MFCom object is corrupt or unregistered in Windows.

The preceding procedure must only be followed if the Discovery process fails on the local and optionally the remote Citrix Delivery Services Console.

If Discovery is unsuccessful only when trying to administer a remote server, refer to Maintaining Server Farms in the Citrix eDocs.