Services not starting after June 2012 patches
Does anyone know what change occurred in the June 2012 'Patch Tuesday' set of patches that would have affected services? This request is because after applying this month patches several Services running decided to stop working after the reboot. It has happened on three different servers each running different applications. If we try to manually start the services they time out, yet if we manually start the program the service runs (which can be done for some of them) the program functions correctly. We have found a workaround which involves increasing the timeout, via creating a DWORD value "ServicePipeTimeout" (with a value, in our case of 60000 decimal) in the location of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control After a reboot the troubled services do eventually start, but as this increases the time a server takes to load we would still like to identify the source of the issue. The variety of services this has effected include a backup service, a EDMA export service and a service related to our financial software. Thank you
June 26th, 2012 12:21am

Honestly, I haven't seen any issues with regard to June 2012 patches on our servers. It might be a co-incidence that services stopped simultaneously on 3 of your servers. You might wanna check event viewer on servers in question to see if there are any warnings/errors related to stopped services.Thanks !
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2012 2:31am

Hi, Thanks for your posting. We dont get similar feedback about June 2012 patches, but we have similar article that describes services will not start after apply some updates. Workaround is modifying the registry to increase the default time-out value for the service control manager, just like what you did. This may resolve the problem, however we recommend that you research the problem to determine whether it is a symptom of another problem. Like K Seeker mentioned above, please check event viewer to find related event logs for further troubleshooting. And generally, Windows will create a system restore point before install Windows updates. You may restore the system point, if this issue disappears in the restored system state, we can use a 50/50 approach to quickly narrow down which update is causing this issue. For more information please refer to following MS articles: Event ID 7011 Basic Service Operations http://technet.microsoft.com/en-us/library/dd349371(v=WS.10).aspx A service does not start, and events 7000 and 7011 are logged in Windows Server 2003 http://support.microsoft.com/kb/922918 Reporting Services Windows Service will not start after applying MS08-052 http://blogs.msdn.com/b/psssql/archive/2008/09/23/reporting-services-windows-service-will-not-start-after-applying-ms08-052.aspx Hope this helps! TechNet Subscriber Support If you areTechNet Subscription user and have any feedback on our support quality, please send your feedback here.Lawrence TechNet Community Support
June 26th, 2012 10:55pm

Hi, I would like to confirm what is the current situation? Have you resolved the problem? If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.Lawrence TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2012 10:08pm

Thanks for that, but most of those links just mention the work around we have already applied, no help in isolating the main cause. Given that several of the affected servers are high use servers, system restore can not be used. (Example - The Exchange server) We have just had another server affected - the SCCM 2007 server, unfortunately this service is running as Local System not as a service account (most of the others used Service Accounts) so that possible link has been debunked. (The two trouble services were AI_UPDATE_SERVICE_POINT and SMS_EXCUTIVE - Once again after the delay was added to the registry, and the server restarted the troubled service resumed normal operation) Given the high use importance of the servers (Exchange Server, SCCM Server etc) we haven't been able to do much troubleshooting that would cause an interrupt in the service (given the workaround is letting them function as normal) When we can arrange some time, we are planning to try removing the June patches one at a time to see if we can isolate which patch is responsible. One of the reasons for posting on here was the hope that someone else had been inflicted with the issue and had already isolated the cause, or that someone could have advised us that one of the patches that was released in June directly affected Services in some way. Thanks
July 2nd, 2012 1:50am

Hi, Very glad to know we have available workaround for this issue. But we now dont have related information about which updates cause this problem. Wed like to do test to narrow down the problem, but we have different Server or OS environment with your company, we cant reproduce your issue. We recommend other customers or partners who meet similar issue to post their experience. Any update or help is appreciated. Also well still keep an eye on this thread, and update it if we found the root reason. TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Lawrence TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2012 3:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics