Solved

Error upgrading Exchange 2010 to SP3

Posted on 2013-05-22
3
1,133 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 400 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 100 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

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

706 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

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now