Freigeben über

Setup for Exchange 2010 Service Pack 1 failing with : “Process execution failed with exit code 1168”

  • Artikel

Consider the following Scenario:

 

You have an Exchange 2010 Organisation. When you try to install for Example Service Pack 1, Setup fails with exit code 1168.

 

We see this in many cases, error 1168 is a generic error.

 

When you examine the ExchangeSetup.log file on the C Drive ( C:\ExchangeSetupLogs) you find the following:

 

[11.08.2010 13:42:11.0906] [2] Starting: C:\Windows\System32\inetsrv\appcmd.exe with arguments: add module /name:exppw /app.name:"Default Web Site/owa"

[11.08.2010 13:42:12.0109] [2] Process standard output: ERROR ( message:Cannot find APP object with identifier "Default Web Site/owa". )

 

[11.08.2010 13:42:12.0109] [2] Process standard error:

[11.08.2010 13:42:12.0155] [2] [ERROR] Unexpected Error

[11.08.2010 13:42:12.0155] [2] [ERROR] Process execution failed with exit code 1168.

[11.08.2010 13:42:12.0155] [2] Ending processing Start-SetupProcess

[11.08.2010 13:42:12.0155] [1] The following 1 error(s) occurred during task execution:

[11.08.2010 13:42:12.0155] [1] 0. ErrorRecord: Process execution failed with exit code 1168.

[11.08.2010 13:42:12.0155] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 1168.

[11.08.2010 13:42:12.0171] [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 1168.".

[11.08.2010 13:42:12.0171] [1] [ERROR] Process execution failed with exit code 1168.

[11.08.2010 13:42:12.0171] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponent___5effe7121e1740c083904cc189687464 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

[11.08.2010 13:42:12.0171] [1] Setup is stopping now because of one or more critical errors.

[11.08.2010 13:42:12.0171] [1] Finished executing component tasks.

[11.08.2010 13:42:12.0296] [1] Ending processing Install-ClientAccessRole

 

The reason why this is happeing, is because you renamed the Default Web Site virtual directory in IIS.

 

The Exchange Setup needs this Default Web Site to be named like this to be able to install Service Pack 1.

 

The only way to get this working is by reinstalling the Servers. ( OS + Exchange ).

 

WE DO NOT RECOMMEND RENAMING THE Default Web Site Virtual Directory in IIS !

 

WE ALSO DON’T HAVE ANY WRITTEN DOCUMENTATION ABOUT HOW TO DO THIS BECAUSE THIS HAS NEVER BEEN TESTED.

 

If you have any questions, please send me an Email to patrisel@microsoft.com

 

Patrick

Comments

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    April 05, 2011
    I got this error and i did not rename the IIS Default Web Site, I tried uninstalling and re-installing IIS and then the CAS Role and I got this error.

  • Anonymous
    July 08, 2011
    Alot of help this article is... it tells me that I did nothing wrong, it just borked.... why waste my time with a useless URL?

  • Anonymous
    November 15, 2011
    what a waste of the time . i dont have loot of time to reinstall all the system from the begining so i just renamed the iis7  name with  (Default Web Site ) & its ackward but it works

  • Anonymous
    November 15, 2011
    what a waste of the time . i dont have loot of time to reinstall all the system from the begining so i just renamed the iis7 sites that i did renamend in the begining  to the    name with  (Default Web Site ) & its ackward but it works / so folks just rename the iis7 site with the Default Web Site

  • Anonymous
    November 15, 2011
    shitttttt it turns out that it dint work

  • Anonymous
    February 21, 2012
    I received this error during the Exchange SP2 upgrade.   The default site had been renamed as a result of CA role having been installed.  However, renaming the IIS site back to "Default Site" and restarting IIS resolved the problem.  SP2 then successfully installed.   Then it was just a case of renaming the site back to "Certificate Authority" and everything worked.

  • Anonymous
    August 08, 2013
    I got the same error an 1168 and had a customized name for the default web site. Renamed it back to "Default Web Site" and that fixed the error.