Hi We have attempted to deploy SP1 on our Exchange 2007 server. All prerequisite checks pass, however on Step 1 of preparing setup, we receive the following error: Summary: 10 item(s). 0 succeeded, 1 failed. Elapsed time: 00:01:33 Preparing SetupFailed Error:Unexpected error [0x78A45562] while executing command '$error.Clear(); $RoleNames = $RoleRoles.Replace('Role','').Split(','); if( test-path "$env:TMP\StoppedServices.xml" ) { .\ServiceControl.ps1 Stop $RoleNames; } else { .\ServiceControl.ps1 Save; .\ServiceControl.ps1 Stop $RoleNames; .\ServiceControl.ps1 DisableServices $RoleNames; }'. File D:\E2K7SP1EN64\Setup\ServerRoles\common\servicecontrol.ps1 cannot be loaded. The contents of file D:\E2K7SP1EN64\Setup\ServerRoles\common\servicecontrol.ps1 may have been tampered because the hash of the file does not match the hash stored in the digital signature. The script will not execute on the system. Please see "get-help about_signing" for more details.. Warning:An unexpected error has occurred and debug information is being generated: Unexpected error [0x78A45562] while executing command '$error.Clear(); $RoleNames = $RoleRoles.Replace('Role','').Split(','); if( test-path "$env:TMP\StoppedServices.xml" ) { .\ServiceControl.ps1 Stop $RoleNames; } else { .\ServiceControl.ps1 Save; .\ServiceControl.ps1 Stop $RoleNames; .\ServiceControl.ps1 DisableServices $RoleNames; }'. Elapsed Time: 00:01:29 I have searched high and low for the solution to this as it also seems to have broken our activesync and OWA since the first attempt at installing. Thank you for your help in this Regards Bruce

Looks like PowerShell(EMC) execution policy is set to All Signed, change it to Remote Signed and try. Set-ExecutionPolicy RemoteSigned

Thanks, however the error is still the same... I've tried re-downloading it and unpacking it however it still fails with the same error

Hi, Base on my research, you may try to copy servicecontrol.ps1 from the RTM setup media to the \E2K7SP1EN64\Setup\ServerRoles\common\ then try to install sp1. Besides, please re-download SP1 to a different directory. Exchange Server 2007 Service Pack 1 http://www.microsoft.com/downloads/details.aspx?FamilyId=44C66AD6-F185-4A1D-A9AB-473C1188954C Hope it helps. Thanks.

Thanks for the reply. We ended up re-downloading again, however it failed because it was also a GC. With the GC role removed, SP1 installed fine. However I still have the issue that OWA and ActiveSync are blocking access (ActiveSync error 0x85010004 "Your Account Does Not Have Permission) and OWA fails on post login with page cannot be found. I think either ISA or IIS is at fault here...

Hi, I suspect that thesomething wrong with metaBase IIS. Please try to follow the below steps to re-create ActiveSyncVirtualDirectory. 1. Please check whether the wildcard application mapping was missing.(Note:IIS-defalut web site-Microsoft-Server-ActiveSync-properties-virtual directory-starting point-configuration-Mappings.) If it has missed it,then please mapped it to %systemroot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll 2.If that is not helpful, then you can try to delete ActiveSyncVirtual Directory and re-create it. A. Back up your IIS metabase. To do this, follow these steps: 1. Start IIS Manager. 2. Right-click Default Web Site, point to All Tasks, and then click Save Configuration to a File. 3. In the Save Configuration to a File dialog box, type a configuration name in the File name input box, and then click OK. B. Delete the virtual directory ActiveSyncVirtualDirectory. To do this, use the Exchange Management Shell. 1. Remove-ActiveSyncVirtualDirectory -Identity "Microsoft-Server-ActiveSync (Default Web Site)" this will delete the virtual directory. 2. New-ActiveSyncVirtualDirectory this will create a new ActiveSync Vdir in the default web site. Beside, please check whether ActiveSync virtual directory had Require secure channel option checked. More information refer to you: Check \owa wildcard application mapping . Added this back in, and mapped it to %systemroot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll, and limited verbs to GET and POST, checked "Script engine".Check \Autodiscover, the .xml application extension (Properties of OWA vDir, configuration button, Application Extensions) was missing. Added this back in, and mapped it to %systemroot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll, and limited verbs to GET and POST, checked "Script engine". Hope it helps. Xiu

Thank you Xiu this worked perfectly. It turned out there was no xml application extension handling, and the wild card was also missing. I have no idea how this broke, unless there was an IIS hotfix rolled out about a week and a half ago... Again thank you so much. Cheers Bruce

Glad to hear it works now.