Microsoft KB Archive/929073

Knowledge Base

Error message when you start Forefront Server Security Administrator: "ERROR: Unable to connect to service"

Article ID: 929073

Article Last Modified on 9/26/2007

---

APPLIES TO

• Microsoft Forefront Security for Exchange Server
• Microsoft Forefront Security for SharePoint

---

SYMPTOMS

When you start Forefront Server Security Administrator, you may receive an error message that resembles the following:

ERROR: Unable to connect to service. An error was returned. Location:
CoCreateInstanceEx. Error: This service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

CAUSE

This problem occurs if Forefront Server Security Administrator cannot connect to the FSCController service either locally or remotely. Forefront Server Security Administrator cannot connect to the FSCController service if one of the following conditions is true:

• The FSCController service is disabled.
• The server that is running Microsoft Forefront Security is unavailable on the computer network.
• Another Forefront Server Security Administrator client is connected to the FSCController service.
• The DCOM configuration disallows Forefront Server Security Administrator to access the FSCController service.

RESOLUTION

To troubleshoot and to resolve this problem, follow these steps in the order that they are presented. After you complete each step, start Forefront Server Security Administrator to test whether the problem is resolved. If you do not receive the error, ignore the remaining steps. If you receive the error, continue with the next step.

1. Enable the FSCController service. To do this, follow these steps:
   1. Click Start, click Run, type services.msc, and then click OK.
   2. In the list of services, double-click FSCController, click Manual in the Startup type list, and then click OK.
2. Use one of the following methods to test whether Forefront Security is available:
   • Run a ping command together with the name of the Forefront Security server.
   • Examine the computer network to see whether the Forefront Security server is listed.
   • Use Microsoft Outlook to send an e-mail message to the Forefront Security server.
   If the Forefront Security server is unavailable, reconnect to the Forefront Security server.
3. Disconnect any Forefront Server Security Administrator clients that are currently connected to the FSCController service. Only one connection is permitted at a time.
4. Use the Dcomcnfg.exe utility to resolve any DCOM issues. To do this, follow these steps:
   1. Click Start, click Run, type dcomcnfg, and then click OK.
   2. In the left pane, expand Component Services, and then click Computers.
   3. In the right pane, right-click My Computer, click Properties, and then click the COM Security tab.
   4. In the Access Permissions area, click Edit Limits.
   5. In the Group or user names box, click ANONYMOUS LOGON, click to select the Allow check box for Remote Access in the Permissions for ANONYMOUS LOGON box, and then click OK two times.
5. Make sure that Windows Firewall is not blocking Forefront Server Security Administrator from communicating with FSCController. To do this, follow these steps:
   1. Click Start, click Run, type firewall.cpl, and then click OK.
   2. Click the Exceptions tab, and then click Add Program.
   3. In the Programs box, click Browse.
   4. In the Forefront installation folder, select FSCController.exe, and then click OK.
   5. In the Programs and Services box, click Add Port.
   6. Type a name in the Name box, type 135 in the Port number box, click TCP, and then click OK two times.
      
      Optionally, you can then edit the FSCController entry, click Change Scope, and then restrict access to My network (subnet) only.

Keywords: kbexpertiseadvanced kbtshoot KB929073

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.