Modify the registry setting that is referenced in the SP1/FR1 readme.
After installing the Oracle Client Version 7.3.3 and rebooting the server, the MFCOM service failed to start. Increasing the TimeOut Value, stated in the SP1/FR1 for MetaFrame XP readme, resolved the issue.
MFCOM Service Timeout
MetaFrame COM Server (MFCOM) is a service that starts when a MetaFrame XP server starts up. The IMA service must be running for MFCOM to start. If a Service failed to start message appears when you restart a server, check the Event Log (Terminal Server) or the System Log (Windows 2000 Server).
If the messages "IMA service hung on starting" and "MFCOM service failed to start" are in the log, IMA service did not start within three minutes, the default timeout period for the MFCOM service. Timeout of the MFCOM service at startup is not a problem, because MFCOM will start later if it is needed. To prevent MFCOM from timing out, edit the following registry key, which sets the amount of time that MFCOM waits for the IMA service to start:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMFComIMAWaitTimeout
Set the value to 1,200,000 milliseconds (20 minutes) or higher. The following registry key controls the time MFCOM waits before polling the IMA service for its status:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMFComIMAWaitPause
The default value is 30,000 milliseconds (30 seconds), which works well in most cases. A value of -1 of timeout indicates to wait indefinitely.
Note:
MFCOM is a COM server that supports the API calls defined in the Citrix Server SDK. If the CWC, Citrix Web Console, which is based on MFCOM, or any other application based on MFCOM, is not being used, the MFCOM Service can be disabled via the control panel. The Citrix server SDK can be obtained through a registration process from the CDN (Citrix Develop Network) at www.citrix.com (Click on the developer link) or http://apps.citrix.com/cdn/.