Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1262
  • Last Modified:

Error upgrading Exchange 2010 to SP3

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
TwoTricky
Asked:
TwoTricky
2 Solutions
 
Simon Butler (Sembee)ConsultantCommented:
Download the service pack again, deleting the original download.

Simon.
0
 
Alexander KireevIT ArchitectCommented:
0
 
TwoTrickyAuthor Commented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now