Installation SP2 on a dag member - Process execution failed with exit code 50
-
lunes, 30 de abril de 2012 21:52
Hi
I tried to install Exchange 2010 sp2 on a dag member, following http://technet.microsoft.com/en-us/library/bb629560.aspx
Bu I always get the following error:
===================================
Client Access Role
FailedError:
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.2.247.1&e=ms.exch.err.Ex88D115&l=0&cl=cp
=============================================I really need help!
Thanks and regards
Peter
Todas las respuestas
-
lunes, 30 de abril de 2012 22:18
While I have never seen this error, on Exchange 2010 CAS servers you have to install the IIS6 WMI Compatibility role. Have you done so?
New Prerequisite for Exchange 2010 SP2
http://www.expta.com/2011/12/new-prerequisite-for-exchange-2010-sp2.htmlInstalling Exchange 2010 SP2
http://thoughtsofanidlemind.wordpress.com/2011/12/05/installing-exchange-2010-sp2/MCTS: Messaging | MCSE: S+M
-
lunes, 30 de abril de 2012 22:24
Hi Jon-Alfred
Thanks for replying.
Yes, I had to install it before I could continue with the installation. I even rebooted the system after that.
This server has all roles installed: mbx, hub and cas.Regards
Peter -
lunes, 30 de abril de 2012 22:32stupid question but are you running it as administrator (opening cmd with run as administrator and running the file)
-
martes, 01 de mayo de 2012 8:09
Not that stupid. The first time i was running it in "normal" mode ;-)
Then I also tried to run it as administrator, but directly on the file (Shift + right click, run as Administrator)
-
martes, 01 de mayo de 2012 14:31try running through CMD. CMD being elevated to Admin
-
martes, 01 de mayo de 2012 19:52
I will try that, but I will be able only next week. I'll keep ypu updated.
Regards
Peter -
domingo, 03 de junio de 2012 20:58
Hi
Just a short update.
Running the update through an elevated cmd didn't work.
The following article gave me a hint to the problem:
http://blogs.technet.com/b/ehlro/archive/2010/11/21/setup-for-exchange-2010-service-pack-1-failing-with-process-execution-failed-with-exit-code-1168.aspxI didn't change the name of the default website, but I created a new owavirtualdirectory in another website. So I recreated the owa virtual directory in the default website, and the service pack 2 installation worked.
Regards
Peter- Marcado como respuesta PeterN22 domingo, 03 de junio de 2012 20:59

