Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Error upgrading Exchange 2010 to SP3

Posted on 2013-05-22
3
Medium Priority
?
1,226 Views
Last Modified: 2013-06-08
I have installed a Exchange Server 2010 on Windows Server 2012 Standard. When upgrading to SP3 I get an error during Client Access Role intallation and the upgrade process stops.

Error:

------------------

The following error was generated when "$error.Clear();
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          $imagePath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess\Owa\auth\exppw.dll");
          Start-SetupProcess -Name "$CommandAppCmd" -args "install module /name:exppw /image:`"$imagePath`" /add:false" -IgnoreExitCode @(183);
          Start-SetupProcess -Name "$CommandAppCmd" -args "add module /name:exppw /app.name:`"Default Web Site/owa`"" -IgnoreExitCode @(183);
        " was run: "Process execution failed with exit code 50.".

Process execution failed with exit code 50.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp

------------------

Can anyone help?
Error.txt
0
Comment
Question by:TwoTricky
3 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 1200 total points
ID: 39189439
Download the service pack again, deleting the original download.

Simon.
0
 
LVL 4

Assisted Solution

by:Alexander Kireev
Alexander Kireev earned 300 total points
ID: 39207394
0
 

Author Closing Comment

by:TwoTricky
ID: 39232019
I wish I could inform if the given advice was of any help, but in fact I decided to start from scratch before the first advice was submitted. Point awarded on bases of response time.

If any one  interested I can inform that I was migrating from Win SMB 2003 to Win Srv 2012 Essentials, installed Exchange  2010 before realizing it does not run on Essentials, tried to unistall Exchange without success because of a mailbox error, promoted to Win Srv 2012 Std, installed SP3 for Exchange on gave up when it did not succeed.

Starting from scratch was no easy game either as it involved restoring the SMB server to its pre-migration state, migrating to 2012 Essentials, promoting to 2012 Std and finally installing Exchange.

Conclusion: Consider opting for SMB 2011 instead of a Win Srv 2012 environment if sufficient, 2012 does not provide a simple solution for SMB's who need an onsite mail server . But if you go for 2012, a fresh install is probably the way to go instead of a migration.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

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

Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
In this post, I will showcase the steps for how to create groups in Office 365. Office 365 groups allow for ease of flexibility and collaboration between staff members.
This video discusses moving either the default database or any database to a new volume.
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…
Suggested Courses

885 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