Exchange Server TechCenter >
Exchange Server Forums
>
Unified Messaging
>
OCS Standard 2007 front-end server won't start
OCS Standard 2007 front-end server won't start
- Our OCS server was working GREAT for almost 1 year.
Out of the sudden, after installing October 2009 Microsoft updates, OCS front-end server won't start.
Excat event ID Error:The Office Communications Server Front-End service terminated with service-specific error 3286842403 (0xC3E93C23).
This is the event error from OCS:
The service is shutting down due to an internal error.
Error Code: C3E93C23 (SIPPROXY_E_INVALID_INSTALLATION_DATA)
Resolution:
Check the previous event log entries and resolve them. Restart the server. If the problem persists contact Product Support Services.
10/13/2009 1:57:50 PM OCS Server 1000 12290 The evaluation period for Microsoft Office Communications Server 2007 has expired. Please upgrade from the evaluation version to the full released version of the product. 10/13/2009 1:53:01 PM OCS MCU Infrastructure 1022 61013 The process DataMCUSvc(4888) failed to send health notifications to the MCU factory at https://union.e-sfo.net:444/LiveServer/MCUFactory/.
Failure occurrences: 64, since 10/13/2009 1:37:17 PM.10/13/2009 1:52:48 PM OCS MCU Infrastructure 1022 61013 The process AVMCUSvc(4836) failed to send health notifications to the MCU factory at https://union.e-sfo.net:444/LiveServer/MCUFactory/.
Failure occurrences: 63, since 10/13/2009 1:37:18 PM.10/13/2009 1:52:45 PM OCS MCU Infrastructure 1022 61013 The process AcpMcuSvc(3516) failed to send health notifications to the MCU factory at https://union.e-sfo.net:444/LiveServer/MCUFactory/.
Failure occurrences: 64, since 10/13/2009 1:37:01 PM.10/13/2009 1:52:15 PM OCS MCU Infrastructure 1022 61013 The process IMMcuSvc(4960) failed to send health notifications to the MCU factory at https://union.e-sfo.net:444/LiveServer/MCUFactory/.
Failure occurrences: 62, since 10/13/2009 1:37:01 PM.10/13/2009 1:44:48 PM OCS MCU Infrastructure 1022 61013 The process AVMCUSvc(4836) failed to send health notifications to the MCU factory at https://union.e-sfo.net:444/LiveServer/MCUFactory/.
Failure occurrences: 30, since 10/13/2009 1:37:18 PM.10/13/2009 1:44:47 PM OCS MCU Infrastructure 1022 61013 The process DataMCUSvc(4888) failed to send health notifications to the MCU factory at https://union.e-sfo.net:444/LiveServer/MCUFactory/.
Failure occurrences: 31, since 10/13/2009 1:37:17 PM.
Please advise what I need to do.
Thanks
All Replies
- I have the exact same problem. Also the first time it failed for me in this way was this night, right after I rebooted after installing updates.
Kind regards,
Tomasz - Hey,
I found the solution.
I had to remove MS updates one by one to determine which one is causing the issue.
Now I am back on after many reboots.
The update causing the issue is:Security Update for Windows Server 2003 (KB974571)
I removed it and all worked OK since; I turned OFF automatic update on the sytem so it won't get installed
later on byitself.
I hope this help.- Proposed As Answer byClemens1 Wednesday, October 14, 2009 6:46 AM
- Yes, removing the KB974571 solved the problem.
I will need to call microsoft tomorrow asking about the worst patch tuesday!!! in a long time. - Same Problem Here,
whats microsoft gonna do?
think that many ocs installations will have the problem ... Same problem here, had uninstalled one microsoft update from tuesday when i saw this post. KB974571 was the one that messed it up. Thanks.
/MichaelPlease post any prograss here, if there is a update to the.. update. Not installing security updates won't do us good :-)
Christoph Schmidt || IT Consultant || MCITP EA || LinkedIn: http://www.linkedin.com/in/schmidtchristoph || XING: http://www.xing.com/profile/Christoph_Schmidt59- This is a known issue and we did blog about this today when confirmed. As an fyi - the process we failed to follow today and will follow in the future is to update the article with a Known Issues section and then we would create a blog referencing it. In today's world of blogs/twitter/email we are trying to leverage the mediums as best we can but certainly invite feedback.
http://communicationsserverteam.com/archive/2009/10/14/632.aspx
Tom Laciano - Microsoft Thanks,
Your suggested also corrected my OCS issue.- This also fixed our issue as we just rebooted our systems from updated that stopped OCS from working. We had to remove this update from all the OCS servers.
Any update from Microsoft as to if this update was pulled and redone?
