FSCController service hung on starting
- Hi,
It seems that every once in a while, my two CAS/HUB servers (2 servers with both roles) have the same issue on reboot. They generally only reboot for updates.
I get the following errors in a row in the System Logs:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Date: 10/27/2008
Time: 4:06:02 AM
User: N/A
Computer: Servername
Description:
The FSCController service hung on startingEvent Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 10/27/2008
Time: 4:06:02 AM
User: N/A
Computer: Servermane
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
Date: 10/27/2008
Time: 4:06:02 AM
User: N/A
Computer: Servername
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.
As a result, the transport service does not start after the system reboots. All of my exchange servers are E2007 SP1 w/rollup 4 on W2K3 SP2.
Version: 10.1.0746.0(Subscription)
Service Pack: 1
Product ID: 89131-005-2000005-60598
Licensed Components:
Component License Type Expiration Date
Forefront Subscription Tuesday, October 05, 2010
Incidents Database Locale: English (United States)
Quarantine Database Locale: English (United States)
Exchange Version: 8.1.240.6
Computer Name: Servername
Operating System: Windows NT Version 5.2, Build number 3790
Operating System Service Pack: Service Pack 2
Processor: Intel processor
Number of Processors: 4
Total Physical Memory: 4294008 KBytes
Available Physical Memory: 910143 KBytes
Temporary Directory Being Used: C:\WINDOWS\Temp\
Available Space on Drive C:\ : 19123342 KBytes
Has anybody else run into this problem? If so, what is the fix for the transport service getting hung on startup? Thanks in advance for any help.
All Replies
- - Is there any 3rd party software on the servers such as Symantec?
- I did see a case which the "Symantec Branch" service was halting the FSCController service from starting
- After disabling that service everything worked fine
- Do you have any exclusions set in place for file level AV to exclude Forefront & Exchange?
John - Hi John,
Thanks for the reply. We don't have Symantec running on any of our servers. All mail servers have MS Forefront for Exchange Server, the Edge uses built in Anti-Spam/Content filtering. All mail servers have Forefront Client Security.
I have just read that Rollup 3 for Forefront for Exchange Server should correct this issue. I am going to try this out first as the hotfix section does mention the service being hung on startup. - I've been experiencing the exact same problem on both my mailbox and hub transport servers, it's very annoying. I've just applied rollup 3 and unfortunately it didn't fix the problem for me. I'll be very interested to hear if you are able to resolve this. I also do not have any other AV software on these servers apart from ForeFront for Exchange.
- Hi Ashton
I have 2 Exc07 HUB Transport servers (Sp1 with Rollup 5). On the first server, the issue has appeared once the patches has been installed, reason why I decided to not apply the patches to the second one. This results in the situation where the first server has the FSCC problem you have described while the second HUB Transport server is running fine.
It seems, that one of the following patches is the origin of this issue:
KB958215
KB958215
KB960714
KB956802
KB958623
KB958624
KB958687
do you already applied this patches to your systems?
The timeout issue regarding the Transport and the FSCIMC and FSCController is a known issue certain people are seeing with Forefront.
However it looks like it is only after a reboot because after that you can go in and start the service and it starts up fine.
This is fixed in a buddy build we have and is in Forefront Sp1 rollup 4 that is not out yet. If you need the buddy build to address this issue you will need to contact Support regarding this.
Thanks.
- Proposed As Answer byMike Sehon Friday, January 23, 2009 8:33 PM
To make everyone aware that for this patch to work you will need to be running Forefront Sp1 rollup3 then apply the patch.
Also this should in the SP2 release of Forefront.
Thanks.
- Hi
I have the same exact problem as the person above.
I am about to install Exchange 2007 SP1 Rollup 7
This error with Forefront has only occured since I first installed this update (seeing other people with problems after insuallting the update I uininstalled it, the comptuer worked fine for a while, then it did the same problem as described above)
My confusion is this
On Forefront I beleive I have RollUp 2 as I have 10.1.0746.0
and on Rollup 3 description it states roll up version is not stated thus there is a fix.
However the rolup description on microsofts site makes it read as if, don;t install the rollup wait for a service pack, which is confusing as Exchange is very muhc, don;t install hot fixes install roll ups
Now you say there is a buddy fix for this problem, which I beleive is something I need as its inpractical to be onsite when the PC is rebooted to manually start the services, and you say I need to be on RollUp 3 to use it.
So does that mean I install RollUp3 to get it running, and then where do i get the buddy fix from?
Surely as this is becomming a more often occurance now, as more peopel are using SBS 2008, surely Microsoft should have released a proper fix for this by now as it is pretty business critical not all Server users have onsite IT technicians to be able to start services upon a PC reboot.
Any help would be gratefully appreciated, and advice on what I should install and how and where from
Thanks
Tristan - try emove the FSEIMC dependency at Micrsofto Exchange Edge Transport service. In regedit, edit DependOnService in HKLM\System\CurrentControlSet\Services\MSExchangeTransport\. Remove the line 'FSEIMC', make sure the last line is blank.
- Proposed As Answer byDaniel Yu Sunday, May 03, 2009 7:36 PM
- Again... This is just something that Microsoft has messed up again with a "HOTFIX" because obviously their testing and Q&A departments can't figure out how to do their jobs. You would think especially with it being SBS that they would do strenuous testing as almost everyone who uses SBS would not have a test environment and is just rolling these updates out to production. This small issue right here has actually caused significant downtime to a client of ours which is unacceptable. Why can't you actually hire some real programmers who know how to do their jobs and test throughly before releasing out to your automated update system things which just are a waste of time and actually break things more than fix them???
Karmst77,
I second that. It all started for me with a patch and one year later (and many patches after), I still have to manually start these services everytime the server is rebooted. It is such a nuisance that I have to credit labor cost back to my clients because I recommened the product after MS said (in a matter of speaking), that "SBS is the best things since sliced bread." Its a great product, no doubt, but can MS just fire the QA team for SBS and hire some expeirences testers. It is costing businesses MONEY HERE FOLKS!!!!! Come on guys, your losing our confidence.
- Rashad Rivera
Omegus Prime, LLC- This is really not good SBS 2008. All i have seen sofar is just issue upon issue. Everytime the server restarts I get a call from customer and issue is with exchanges services not start due to this problem. When are you guys going to fix this. I actually dont want to run ForeFront,
Please give us a solution not hot fix!
Smarthost Design Technologies LLC - Forefront for Exchange SP2 fixes this issue. It has already been released.
- I can't find any links to a standalone SP2. Do I really need to re-install the product in order to get SP2?
- Hi Martin,
there is no standalone SP2, you always have to download the full package.
To apply SP2 don't have to uninstall the former version you only have to run setup and the existing installation will be upgraded.
Greetings
Christian
Christian Groebner MVP Forefront - Thanks. :)
