We have two CAS servers and 1 mailbox server.

OHS-EXCHCAS (Client Access, Hub Transport)

SP2 upgrade complete

SP3 upgrade complete

Rollup 9 Update complete

OHS-EXCHFE (Client Access, Hub Transport)

SP3 Update Failed

Rollup 9 not complete

OHS-EXCHBE (Mailbox )

SP3 Update Failed

Rollup 9 not complete

We successfully upgraded  OHS-EXCHCAS (Client Access, Hub Transport)

We get the following error while upgrading OHS-EXCHFE (Client Access, Hub Transport)

Are you running the service pack installation from a unc path or a local path?  I've seen error 50 when doing certain things from a UNC Path.  Try copying the Service Pack locally and running setup.

I am running the setup locally.

Did you make any changes to the IIS websites like adding additional vdirs?

No changes were made to dir.

Hi,

Please collect the Exchange Setup logs events for further troubleshooting.

Regards,

Run Get-OwavirtualDirectory -server <servername>

[PS] C:\EMTshooter>.\EMTshooter.ps1

Welcome to the Exchange Management Troubleshooter!

We recommend that you run the troubleshooter after making changes to

IIS to ensure that connectivity to Exchange Powershell is unaffected.

Checking IIS Service...

Checking the Exchange Install Path variable...

Checking the Powershell Virtual Directory...

Checking the Powershell vdir SSL setting...

Checking the Powershell vdir path setting...

Checking HTTP Port 80...

Checking HTTP Port 80 Host Name...

Testing for errors...

VERBOSE: Connecting to OHS-EXCHFE.Mail.orange.k12.nj.us

[ohs-exchfe.mail.orange.k12.nj.us] Connecting to remote server failed with the following error message : The WinRM clien

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep

    + FullyQualifiedErrorId : PSSessionOpenFailed

The Exchange Management Troubleshooter successfully completed connecting to:

OHS-EXCHFE.Mail.orange.k12.nj.us

Failed to connect to any Exchange Server in the current site.

Problem found:

Looking for error...

These are the possible causes for this error:

1. If the WSMan module entry is missing from the global modules section of the

C:\Windows\System32\Inetsrv\config\ApplicationHost.config file, as follows:

<globalModules>

           <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />

This will result in the WSMan module displaying as a Managed module on the PowerShell virtual directory.

To correct this, make sure that the WSMan module has been registered (but not enabled) at the Server level, and has been

enabled on the PowerShell virtual directory.  Confirm that the WSMan entry exists in the Global Section of the Applicat

ionHost.config file as shown above.

2. Remote PowerShell uses Kerberos to authenticate the user connecting.  IIS implements this Kerberos authentication met

hod via a native module. In IIS Manager, if you go to the PowerShell Virtual Directory and then look at the Modules, you

should see Kerbauth listed as a Native Module, with the dll location pointing to \Program Files\Microsoft\Exchange Serv

er\v14\Bin\kerbauth.dll. If the Kerbauth module shows up as a Managed module instead of Native, or if the Kerbauth modul

e has been loaded on the Default Web Site level (instead of, or in addition to, the PowerShell virtual directory), you c

an experience this issue. To correct this, make sure that the Kerbauth module is not enabled on the Default Web Site, bu

t is only enabled on the PowerShell virtual directory.  The entry type of "Local" indicates that the Kerbauth module was

enabled directly on this level, and not inherited from a parent.

3.  The Path of the Powershell virtual directory has been modified.  The PowerShell virtual directory must point to the

"\Exchange Server\v14\ClientAccess\PowerShell"

directory or you will encounter problems.

After each error is resolved, close this window and re-run the tool to check for additional problems.

The Exchange Setup Logs

https://onedrive.live.com/redir?resid=f3743c55dc76b1ee!15331&authkey=!AJywMixo1SbCLl8&ithint=folder%2clog

       
[04/22/2015 19:45:04.0481] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'MiddleGrib.Mail.orange.k12.nj.us', Preferred Global Catalog: 'MiddleGrib.Mail.orange.k12.nj.us', Preferred Domain Controllers: '{ MiddleGrib.Mail.orange.k12.nj.us }'
[04/22/2015 19:45:04.0481] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\System32\inetsrv\appcmd.exe' -Args:'install module /name:exppw /image:"C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll" /add:false' -IgnoreExitCode:'183'
[04/22/2015 19:45:04.0481] [2] Starting: C:\Windows\System32\inetsrv\appcmd.exe with arguments: install module /name:exppw /image:"C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll" /add:false
[04/22/2015 19:45:04.0777] [2] Process standard output: ERROR ( message:Failed to add duplicate collection element "exppw". )
[04/22/2015 19:45:04.0777] [2] Process standard error:
[04/22/2015 19:45:04.0777] [2] IgnoreExitCode parameter specified - Ignoring exit code 183.
[04/22/2015 19:45:04.0777] [2] Ending processing Start-SetupProcess
[04/22/2015 19:45:04.0777] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'MiddleGrib.Mail.orange.k12.nj.us', Preferred Global Catalog: 'MiddleGrib.Mail.orange.k12.nj.us', Preferred Domain Controllers: '{ MiddleGrib.Mail.orange.k12.nj.us }'
[04/22/2015 19:45:04.0777] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\System32\inetsrv\appcmd.exe' -Args:'add module /name:exppw /app.name:"Default Web Site/owa"' -IgnoreExitCode:'183'
[04/22/2015 19:45:04.0777] [2] Starting: C:\Windows\System32\inetsrv\appcmd.exe with arguments: add module /name:exppw /app.name:"Default Web Site/owa"
[04/22/2015 19:45:04.0824] [2] Process standard output: ERROR ( message:Must use exact identifer for APP object with verb SET. )
[04/22/2015 19:45:04.0824] [2] Process standard error:
[04/22/2015 19:45:04.0824] [2] [ERROR] Unexpected Error
[04/22/2015 19:45:04.0824] [2] [ERROR] Process execution failed with exit code 50.
[04/22/2015 19:45:04.0824] [2] Ending processing Start-SetupProcess
[04/22/2015 19:45:04.0824] [1] The following 1 error(s) occurred during task execution:
[04/22/2015 19:45:04.0824] [1] 0.  ErrorRecord: Process execution failed with exit code 50.
[04/22/2015 19:45:04.0824] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 50.
[04/22/2015 19:45:04.0824] [1] [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.".
[04/22/2015 19:45:04.0824] [1] [ERROR] Process execution failed with exit code 50.
[04/22/2015 19:45:04.0824] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponent___5effe7121e1740c083904cc189687464 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[04/22/2015 19:45:04.0824] [1] Setup is stopping now because of one or more critical errors.
[04/22/2015 19:45:04.0824] [1] Finished executing component tasks.
[04/22/2015 19:45:04.0871] [1] Ending processing Install-ClientAccessRole
[04/22/2015 19:52:52.0816] [0] End of Setup
[04/22/2015 19:52:52.0816] [0] **********************************************

• Edited by Parvinder_Randev 16 hours 16 minutes ago

Recreating OWA Virtual Directory  fixed the issue.

• Marked as answer by Parvinder_Randev 10 hours 57 minutes ago