Error
"Citrix MFCOM Service did not respond as expected. Make sure that your user account is a member of this computer's Distributed COM Users group if you are connecting to a remote server. Check the version of Citrix Presentation Server on the computer and make sure that a compatible version of Citrix MFCOM Service is installed and running."
Resolution
go to Compone nt Services within Adminis trative Tools
Expand Compone nt Services
Expand Compute rs
Expand My Computer
Expand COM+ Applicatio ns
Expand Citrix IMA COM Interop
Expand Roles
Expand Citrix Administra tors
Right click Users and add an existing user or group
***
"Citrix MFCOM Service did not respond as expected. Make sure that your user account is a member of this computer's Distributed COM Users group if you are connecting to a remote server. Check the version of Citrix Presentation Server on the computer and make sure that a compatible version of Citrix MFCOM Service is installed and running."
Resolution
go to Compone
Expand COM+ Applicatio
Expand Roles
Expand Citrix Administra
***
To re-register MFCOM in Windows complete the following procedure:
- Navigate to the %programfiles(x86)%\Citrix\system32 folder from the command prompt.
- Run the following command from the command prompt:
mfcom /unregserver
No output is displayed - Run the following command from the command prompt:
mfcom /regserver - Run the following command from the command prompt: (for XA 6.5)
regsvr32 mfcomsrv.dll - Click OK.
- Open the registry editor and navigate to the following entry:
HKLM\SYSTEM\CurrentControlSet\Services\MFCom - Create a DWORD value with the following details:
Name: ServiceSidType
Data: 1 - Restart the server.
- Verify if the Citrix MFCOM Service is displayed and has started.
Missing Citrix MetaFrame COM Server
February 22, 2011
I am picky when it comes to the Citrix XenApp servers on which I work. Warnings and Errors in the event logs just drive me up the wall. They are both to be banished if at all possible. A client site I was at recently fixing issues had hundreds of DCOM errors recorded in every XenApp server’s System event log. A particular event that is recorded is shown in Figure 1.
One of the common reasons for this error is when an administrator executes the Citrix Management Consoles on XenApp servers which are not Zone Data Collectors. Best practice is to install and run the Citrix Delivery Services Console and Advanced Configuration Console on the Zone Data Collectors.
To resolve this error, Microsoft recommends the following steps be followed (http://tinyurl.com/DCOM10016 ).
I knew from other servers that this should be showing as MetaFrame COM Server (Figure 3).
Looking in DCOM Config shows no component named MetaFrame COM Server (Figure 4).
However, the CLSID of {ED62F4E0-63C2-11D4-94D8-00C04FB0F326} is found (Figure 5).
For this server, the problem is simply that the component does not have the name configured. To fix this problem, return back to the registry editor and double click on (Default) (Figure 6).
For Value data Enter MetaFrame COM Server, click OK and exit the registry editor (Figure 7).
Note: This entry may be case sensitive, so enter the Value data exactly as shown above.
In Component Services, click on DCOM Config and then click on the Refresh icon (Figure 8).
The MetaFrame COM Server component is now in the proper location (Figure 9).
You can now use the instructions given above under DCOM Repair Instructions, to add the user and assign the Allow – Remote Activation permission.
Also, the MetaFrame COM Server is missing in Component Services (Figure 11).
The CLSID of {ED62F4E0-63C2-11D4-94D8-00C04FB0F326} is also missing (Figure 12).
To fix these issues, from an elevated command prompt, register both by typing the following commands (Figure 13).
mfcom /regserver
mfreg /regserver
net start MFCom
The Citrix MFCOM Service returns and is started (Figure 14).
In DCOM Config in Component Services, the CLSID appears (Figure 15).
Open the registry editor, search for the CLSID and double click on (Default) (Figure 16).
For Value data Enter MetaFrame COM Server, click OK and exit the registry editor (Figure 17).
Note: This entry may be case sensitive, so enter the Value data exactly as shown above.
In Component Services, click on DCOM Config and then click on the Refresh icon (Figure 18).
The MetaFrame COM Server component is now in the proper location (Figure 19).
You can now use the instructions given above under DCOM Repair Instructions, to add the user and assign the Allow – Remote Activation permission.
One of the common reasons for this error is when an administrator executes the Citrix Management Consoles on XenApp servers which are not Zone Data Collectors. Best practice is to install and run the Citrix Delivery Services Console and Advanced Configuration Console on the Zone Data Collectors.
To resolve this error, Microsoft recommends the following steps be followed (http://tinyurl.com/DCOM10016 ).
DCOM Repair Instructions:
- Copy the CLSID
- Open the registry editor
- Search for the CLSID
- Record the name
- Open Administrative Tools -> Component Services
- Double-click Component Services
- Double-click Computers
- Double-click My Computer
- Click DCOM Config
- Scroll down and find the object with the name you recorded earlier
- Right-click the object and select Properties
- Click the Security tab
- In the Launch and Activation Permissions section, select Customize and click Edit…
- Add the user reported in the event
- Select the user just added and check Allow – Remote Activation
- Click OK, OK and exit Component Services
- CLSID found but not MetaFrame COM Server.
- Neither MetaFrame COM Server nor the CLSID is found.
CLSID found but not MetaFrame COM Server
Searching the registry for the CLSID on one server returned what is shown in Figure 2.I knew from other servers that this should be showing as MetaFrame COM Server (Figure 3).
Looking in DCOM Config shows no component named MetaFrame COM Server (Figure 4).
However, the CLSID of {ED62F4E0-63C2-11D4-94D8-00C04FB0F326} is found (Figure 5).
For this server, the problem is simply that the component does not have the name configured. To fix this problem, return back to the registry editor and double click on (Default) (Figure 6).
For Value data Enter MetaFrame COM Server, click OK and exit the registry editor (Figure 7).
Note: This entry may be case sensitive, so enter the Value data exactly as shown above.
In Component Services, click on DCOM Config and then click on the Refresh icon (Figure 8).
The MetaFrame COM Server component is now in the proper location (Figure 9).
You can now use the instructions given above under DCOM Repair Instructions, to add the user and assign the Allow – Remote Activation permission.
Neither MetaFrame COM Server nor the CLSID is found
On one server, the Citrix MFCOM Service is missing (Figure 10).Also, the MetaFrame COM Server is missing in Component Services (Figure 11).
The CLSID of {ED62F4E0-63C2-11D4-94D8-00C04FB0F326} is also missing (Figure 12).
To fix these issues, from an elevated command prompt, register both by typing the following commands (Figure 13).
mfcom /regserver
mfreg /regserver
net start MFCom
The Citrix MFCOM Service returns and is started (Figure 14).
In DCOM Config in Component Services, the CLSID appears (Figure 15).
Open the registry editor, search for the CLSID and double click on (Default) (Figure 16).
For Value data Enter MetaFrame COM Server, click OK and exit the registry editor (Figure 17).
Note: This entry may be case sensitive, so enter the Value data exactly as shown above.
In Component Services, click on DCOM Config and then click on the Refresh icon (Figure 18).
The MetaFrame COM Server component is now in the proper location (Figure 19).
You can now use the instructions given above under DCOM Repair Instructions, to add the user and assign the Allow – Remote Activation permission.
No comments:
Post a Comment