Scroll Top
Evotec Services sp. z o.o., ul. Drozdów 6, Mikołów, 43-190, Poland

Upgrading Exchange 2010 SP3 to Rollup Update 18 fails with blank webpage

Microsoft Exchange

Upgrading Exchange 2010 SP3 to Rollup Update 18 is fairly smooth process. This rollup update is part of standard Windows Update feature, you go in, press update, and if you're not careful enough (as you should be) your Exchange SP3 RU 18 is on it's way. In my case it first was stuck on all Exchange services being disabled which I've fixed with Qucik script fix for disabled services which was caused by Pulseway not being disabled prior to installation. But that's not what the post is about. After restarting installation of RU18 things went smoothly and finished installing Exchange update. Unfortunately OWA webpage was blank after upgrading.

Problem Description

After updating Exchange 2010 to SP3 Rollup 18 a post-check process requires to go and verify if everything went smoothly. Unfortunately after opening up OWA webpage it was completely blank with a weird &reason=0 added in the end.


No error messages were present on the website.

That's a bit unexpected.


To fix this issue you must start updatecas.ps1 script in the Exchange Management Shell as Administrator. The script can be found at C:\Program Files\Microsoft\Exchange Server\V14\Bin and comes with update rollup. The script handles OWA and ECP updates.

[PS] C:\Program Files\Microsoft\Exchange Server\v14\Bin>.\UpdateCas.ps1
[23:22:53] ***********************************************
[23:22:53] * UpdateCas.ps1: 2017-07-12 23:22:53
[23:22:55] Updating OWA/ECP on server EXCHANGE
[23:22:55] Finding ClientAccess role install path on the filesystem
[23:22:56] Updating OWA to version 14.3.361.1
[23:22:56] Copying files from 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\Current' to 'C:\Program
Files\Microsoft\Exchange Server\V14\ClientAccess\owa\14.3.361.1'
[23:23:01] Found 1 OWA virtual directories.
[23:23:01] Updating OWA virtual directories
[23:23:01] Processing virtual directory with metabase path 'IIS://EXCHANGE.private.corp/W3SVC/1/ROOT/owa'.
[23:23:01] Creating metabase entry IIS://EXCHANGE.private.corp/W3SVC/1/ROOT/owa/14.3.361.1.
[23:23:02] Configuring metabase entry 'IIS://EXCHANGE.private.corp/W3SVC/1/ROOT/owa/14.3.361.1'.
[23:23:02] Saving changes to 'IIS://EXCHANGE.private.corp/W3SVC/1/ROOT/owa/14.3.361.1'
[23:23:02] Saving changes to 'IIS://EXCHANGE.private.corp/W3SVC/1/ROOT/owa'
[23:23:02] Update OWA done.
[23:23:02] Updating ECP to version 14.3.361.1
[23:23:02] Copying files from 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\Current' to 'C:\Program
Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\14.3.361.1'
[23:23:03] Update ECP done.
[PS] C:\Program Files\Microsoft\Exchange Server\v14\Bin>

Finally refresh of website gives a proper web app again. Phew…

It's a bit weird this script is not started as part of update, but fortunately it's readily available as part of installation.

Related Posts

Leave a comment

You must be logged in to post a comment.