[Last Call] Learn how to a build a cloud-first strategyRegister Now


exchange 2013 service pack install failure

Posted on 2014-07-16
Medium Priority
Last Modified: 2014-08-19
2013 exchange service pack 2013 failed during installation and I can not recover.
Question by:2knetworks
  • 3
  • 3
LVL 19

Expert Comment

by:Adam Farage
ID: 40200011
A bit more details would be helpful, such as the installation logs and errors you get when what you tried? Just saying..

Accepted Solution

2knetworks earned 0 total points
ID: 40200103
Sorry, I am a first time user.  When I posted the question I thought I was just asking a question.  I did find out how to work around it.  As the service pack upgrades the different areas of Exchange is set all the services as disabled.  The problem is, some of the areas don't  have the correct scripting to re-enable the service to start it when it is done that part of the upgrade.

You need to watch the services and each time it moves onto another area it will disable them all.  At that point, set them all the manual.  (You can do this with a powershell script to make it quick.  You will have to do it about 8 times.)  It will then do the upgrade.  After that you just need to set the appropriate services to auto start.

Thank you Microsoft for doing such a great job of writing your service packs!!!!
LVL 19

Expert Comment

by:Adam Farage
ID: 40200457
That shouldnt happen.. within the MSI Package installer there should be a script in there that renables the services. Can you provide the setup log or check the setup log for or [DEBUG] flags?
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments


Author Comment

ID: 40201759
The log is attached.  I talked to one of our other engineers.  He said this is a known issue with Microsoft and they actually have a fix.  (Although, I could not find anything specific from Microsoft on it.)  He said it usually has to do with certain types of virus software and the interaction with the transport.  

I also read some information regarding this on Exchange 2010. That is what lead me toward looking at the services during the installation.
LVL 19

Expert Comment

by:Adam Farage
ID: 40201860
The log is attached.  I talked to one of our other engineers.  He said this is a known issue with Microsoft and they actually have a fix.  (Although, I could not find anything specific from Microsoft on it.)

hrm, being that I worked @MSFT I never heard this before, unless the restart-service or start-service did not work on the clients machine. This is why after a CU is done being installed, you MUST reboot a machine afterwards as some services will deadlock when attempting to start (e.g: timeout).

If you look in the installer log, you see several instances where services are either started / restarted:
            restart-service MSExchangeServiceHost
            start-setupservice -ServiceName MSExchangeADTopology 
            start-SetupService -ServiceName MSExchangeDelivery

Open in new window

The list goes on. What I would recommend doing is looking through the log to figure out what services didnt start, and see what you see within this log on why... This is NOT normal since the old days of Exchange 2007 / Exchange 2010 RTM patching, but then again you should to restart post installation which would have had all of your services started either way. You should not have to set them to manual.

Author Closing Comment

ID: 40269791
Resolved issue myself

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Determining the an SCCM package name from the Package ID
Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month18 days, 8 hours left to enroll

826 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question