The Microsoft Exchange Information Service and the Exchange Transport service fail to start after a reboot when using Forefront Security for Exchange

By |2017-12-11T11:45:14+00:00June 16th, 2011|Exchange|0 Comments

A customer recently had an issue where the Microsoft Exchange Information Service and the Exchange Transport service would fail to start after a reboot. While investigating this issue, we noticed the following events in the Application log:

 

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Description:
The FSCController service hung on starting.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Description:
The FSEIMC service depends on the FSCController service which failed to start because of the following error:
After starting, the service hung in a start-pending state.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Description:
The Microsoft Exchange Transport service depends on the FSEIMC service which failed to start because of the following error:
The dependency service or group failed to start.

 

Solution:

Ensure Service Pack 2 is installed for Forefront Security for Exchange Server

Leave A Comment

like what you see? 

Sign-up to our newsletter and never miss out on the latest blogs, events and tech news from the world of risual
SUBSCRIBE!
Give it a try, you can unsubscribe anytime.