Exchange 2010 SP3 CAS Installation Failing – IISRESET “Process execution failed with exit code 1062”
While preparing my org for the migration to Exchange 2013, I was installing SP3 for Exchange 2010 and I got the following error.
Client Access Role installation Failed
Error:
The following error was generated when “$error.Clear();
Start-SetupProcess -Name “iisreset” -Args “/noforce /timeout:120”
“was run: “Process execution failed with exit code 1062.”.
Process execution failed with exit code 1062.
Manually tried to do a iisreset which also failed with the error.
The IIS Admin Service or the World Wide Web Publishing Service, or a service dependent on them failed to start. The service, or dependent services, may had an error during its startup or may be disabled.
Checked event viewer and I got the following event:
Cause:
Checked the MSMQ service in Services.msc which was not present.
Solution:
Installed Message Queue Services from add feature and installation continued.
Prabhat Nigam
Microsoft MVP | Exchange Server
Team @MSExchangeGuru
June 22nd, 2013 at 7:09 pm
[…] Exchange 2010 SP3 CAS Installation Failing – IISRESET “Process execution failed with exit code 1… – […]
June 22nd, 2013 at 7:14 pm
[…] Exchange 2010 SP3 CAS Installation Failing – IISRESET “Process execution failed with exit code 1… – […]
June 25th, 2013 at 12:58 am
[…] Exchange 2010 SP3 CAS Installation Failing – IISRESET “Process execution failed with exi… […]
July 11th, 2013 at 5:50 am
Thank you very much. This worked for me.
July 26th, 2013 at 11:55 pm
Thanks so much for posting this! It worked great and saved my Friday night!!
July 27th, 2013 at 12:00 am
You owe me a drink… 😛
March 22nd, 2014 at 9:40 am
Totally rocked it! Worked like a charm.
March 29th, 2014 at 1:08 pm
it did work for me, I’ve been battling with this for the past 10 hours and no luck.
now outlook cannot connect to exchange, since the sp3 install got interrupted.
any help is appreciated.
March 29th, 2014 at 1:24 pm
Did you do the IISreset?
March 29th, 2014 at 3:30 pm
Yes I did, and I’m getting the error about attempt restart failed.
both services can be started from the service console without any issue.
any more suggestions? I have removed the none-http activation from net framework feature also.
I seems to be stuck on this.
March 29th, 2014 at 3:34 pm
Yes I did, and I’m getting the error about attempt restart failed.
both services can be started from the service console without any issue.
any more suggestions? I have removed the none-http activation from net framework feature also.
I seems to be stuck on this.
thanks,
March 29th, 2014 at 3:44 pm
Yes i did, I’m still getting this iisreset error. rebooted the server many times, no fix.
I have also removed the none-http activation feature.
still stuck at same place.
any other suggestions?
thanks
March 29th, 2014 at 4:31 pm
Let me understand the issue.
Are we unable to connect outlook to exchange server after installing 2010 sp3?
How about owa and active sync?
Do you see any error on outlook?
What is the outlook and OS of the outlook client machine?
September 1st, 2014 at 5:30 am
Hi,
Im stuck at the same fase, when iisreset /noforce /timeout:120 is called i get restart attempt failed, i get that’s why my sp3 instalation for exchange 2010 also fails:
Attempting stop…
Internet services successfully stopped
Attempting start…
Restart attempt failed.
The IIS Admin Service or the World Wide Web Publishing Service, or a service dep
endent on them failed to start. The service, or dependent services, may had an
error during its startup or may be disabled.
Anynone has any ideas how to solve this?
Thanks in advance,
Oscar.
November 2nd, 2014 at 12:30 am
Other than the suggestion above, I also had to pay attention to the World Wide Web Publishing server.
I had to restart it when the SP3 installation got to that point ( I kept trying to restart).
Also,
This issue could be caused by the corrupted PowerShell Virtual Directory or saving the changes failed from AD to Metabase. In light of this, we need to first remove the affected PowerShell Virtual Directory, then restart the upgrade process. Please refer to the following steps:
1. Remove the PowerShell Virtual Directory by command:
Get-PowerShellVirtualDirectory –Server “Affected_server” | Remove-PowerShellVirtualDirectory
2. Then try to restart the upgrade process. However if we can’t remove the PowerShell Virtual Directory by above command or the upgrade still failed, please refer to step3 to remove the PowerShell Virtual Directory from AD.
3. Remove the PowerShell Virtual Directory from AD:
Open ADSI editor, connect to the “Configuration” partition;
Navigate to the database object under the Exchange 2013 Administrator Group “Exchange Administrative Group (FYDIBOHF23SPDLT)->Servers->Affected_server->Protocols->HTTP”;
Find the “PowerShell-Proxy” and “PowerShell” object like below.
Remove these two objects.
. Then try to restart the upgrade process. If needed, we can first restart the server then try the upgrade.
This link below can help you to remove the virtual directory as well.
https://social.technet.microsoft.com/Forums/exchange/en-US/7b363004-dbed-43da-878c-6d3ac021df0f/upgrade-to-exchange-2010-sp3-failed-at-hub-transport?forum=exchange2010