Bize Ulaşın / Contact Us

Exchange Server Logo

Exchange Server 2013 CU3 Finalizing Setup FAILED

16 / 02 / 2014 by Exchange Server, Exchange Server 2013 Yorum yok / No Comments


If your Exchange Server 2013 Cumulative Update fails with the following error:

The following error was generated when “$error.Clear();
$windir = $env:windir;
# Note: Turning off DynComp for AppPools like MSFFOGLSAppPool as well
$backEndAppPrefix = “Exchange Back End”;
$apps = &”$windir\system32\inetsrv\appcmd.exe” “list” “app”;
foreach($app in $apps)
$startIndex = $app.IndexOf(‘”‘) + 1;
$numChars = $app.SubString($startIndex).IndexOf(‘”‘);
$appName = $app.SubString($startIndex, $numChars);

# Don’t want to disable Dynamic Compression on 1 box topologies for BE Apps, so adding check
Write-ExchangeSetupLog -Info “Skipping $appName since Dynamic Compression should remain turned on for
# We’ll set this whether or not the app pool exists. Failures are ignored.
$a= &”$windir\system32\inetsrv\appcmd.exe” “set” “config” “$appName” -section:urlCompression /doDynami
cCompression:false /commit:apphost
Write-ExchangeSetupLog -Info ($a)
” was run: “Cannot convert ‘System.Object[]’ to the type ‘System.String’ required by parameter ‘Message’. Specified method is not supported.”.
The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.


Check the execution policy of Windows PowerShell and ensure it is set to ‘Unrestricted’.

To check the execution policy run:

  • Get-ExecutionPolicy

To set it to unrestricted run:

  • Set-ExecutionPolicy Unrestricted



Leave a Reply

Your email address will not be published. Required fields are marked *

Kontrol / Control * Time limit is exhausted. Please reload CAPTCHA.

This site uses Akismet to reduce spam. Learn how your comment data is processed.