After you install update rollup 1,2 or 3 on an Exchange 2010 Client Access Server you often get a blank OWA page when browsing to the OWA page.
After installing the rollup updates you will receive something like the following URL; https://mail.msexchangeblog.nl/owa/auth/logon.aspx?url=https://mail.msexchangeblog.nl/owa/&reason=0 .
To fix this issue you must start updatecas.ps1 in the Exchange Management Shell. You can find the script in C:\Program Files\Microsoft\Exchange Server\V14\Bin . The script updatecas.ps1 will handle the OWA and ECP updates. The updatecas script comes with the update rollup.
July 14, 2011 @ 08:19
I’ve been searching for a solution everywhere and all I could find is craps like reinstalling IIS and things like that.
This one has done the job and I’m finally able to access my OWA site.
Your solution is not easy to find but it’s the easiest to apply.
August 24, 2011 @ 19:54
many many thanks it was the solution 4 me
September 6, 2011 @ 08:49
I met this problem after every rollup pack with Exchange 2010.
After retablished OWA with other tricks found on the Internet, your solution is the greatest.
Thanks a lot buddy!
September 13, 2011 @ 02:08
Absolutely brilliant post! Spot on!
After applying Exch2010 Roll-up 2 and 3 we ran into this issue at a customer. This was the fix! Many thanks!
September 15, 2011 @ 14:12
This works great. Thanks.
September 20, 2011 @ 15:18
I am having this issue with only one user. I was having it with several, but not all. Now one user is still getting the same reason=0 issue. I have followed all of the above instructions.
September 21, 2011 @ 15:28
Brilliant! Thank you for the guidance and clear documentation of the fix. I owe you a beer.
September 21, 2011 @ 18:10
No worries! Beers are always welcome 😉
October 6, 2011 @ 19:38
You sir are a godsent! Thanks for a great help and saving me insane amounts of frustration. If your ever in NYC beers on me!
October 14, 2011 @ 12:35
Why isn’t this up in lights somewhere?
And why haven’t *more* people offered you beer?
Just hit the dreaded OWA blank page issue after Exchange 2010 SP1 Update Rollup 5 . This is on dear little SBS 2011.
Users complain re OWA going dead. Takes a while to figure out the Update Rollup has been pushed down the pipe at you and is the likely culprit.
Then m-u-c-h longer researching any number of ‘it worked for me’ solutions, many of which involve uninstalling & reinstalling the Rollup.
When all along, we could have simply run the updatecas.ps1 script. I found this blogpage, ran the script, problem solved.
Worked for me.
October 14, 2011 @ 12:36
October 16, 2011 @ 21:30
This just saved my life. I just finished an SBS 2003 to 2011 upgrade, which has been a nightmare. Between the undocumented settings and patches screwing more things up than fixing them, I can’t believe how complex this was. I’m always amazed at how these gems are not documented by Microsoft. I’m an IT consultant that does technical support as well, and Exchange has become a beast.
Thanks again, I could hug you,
October 28, 2011 @ 03:22
You just need to install the RPC over HTTP Proxy feature by heading to Server Manager – Features – Add Feature then select RPC over HTTP Proxy from the list and continue through the wizard to add the feature!
March 13, 2012 @ 23:23
I tried updatecas.ps1 but same error. Then installed the RPC over HTTP Proxy feature recommended by Adde. It fixed the issue. Thanks Adde.I was struggling from last week and now it fixed.
April 3, 2012 @ 23:53
Thanks! This is the step that worked for me. Hosted Exchange seems to be the way to go. Let someone else deal with M$oft and their bloated programming!
September 20, 2012 @ 16:17
I still had the blank OWA screen after running the updatecas.ps1 script. Installing the RPC over HTTP proxy fixed it! Thank you.
March 15, 2013 @ 20:42
YUDAMANNNN!!!! This worked! I installed IIS before Exchange and did not select the required IIS options. RPC over HTTP Proxy installed the remaining required options. Thank you!
October 31, 2011 @ 22:48
Thanks very much for this Brilliant post.
November 24, 2011 @ 12:19
Installed rollup 6 yesterday and it caused trouble with owa. This fixed the problem. Thanx a lot mate! Cheers
November 30, 2011 @ 22:35
THANK YOU!. Great and easy fix. I just installed update rollup 6 for exchange 2010 service pack 1 (KB2608646) and it shut off all of my exchange services and screwed up owa. Thanks again..
December 19, 2011 @ 12:43
That was exactly my situation, too. Thanks very, much. I’ll gladly buy you a pint.
December 5, 2011 @ 23:37
Thank you very much.
December 23, 2011 @ 12:48
Good Day, I ran the fix in the command shell, but still getting the blank page on OWA.
Is there anything else that needs to be checked?
March 4, 2012 @ 09:11
Thanks! This helped a ton!
Bijo P G
March 10, 2012 @ 16:13
I tried this fix but still i have this issue,I didn’t installed any rollup recently but Owa stopped working
March 12, 2012 @ 15:23
Nice! Solved my problem.
Just remember to start the Exchange management shell as Administrator.
March 15, 2012 @ 13:18
Thanks, it worked! Thumbs up!!
March 29, 2012 @ 01:56
Thank you! It worked perfectly, greatly appreciated.
March 29, 2012 @ 16:47
Thanks a lot !
You’re the best
I had the same problem with after the rollup 6
April 4, 2012 @ 04:14
It’s cool.. really help me.. thanks…
if your exchange is in D drive, use below command to change directory to Bin folder..
April 13, 2012 @ 12:11
Thank you – all working again
May 3, 2012 @ 17:02
Thanks!! This worked great! Was getting worried I was going to have to go the reinstall route. 🙂
May 5, 2012 @ 08:13
Solved my problem after installing UR2 on an Exchange 2010 SP2!
Thanks a lot!
May 8, 2012 @ 09:45
Thanks! Great post! Had to install the RPC over HTTP Proxy feature as well as the fix but sorted! Thank you!
May 19, 2012 @ 19:02
Thanks! very obscure script to track down and run and I forgot to launch the powershell as admin. Very rare to find a straight forward solution.
May 30, 2012 @ 14:19
we had installed rollup 6 owa stopped working but could log into mailbox from the server itself, now after running the script as it has worked just fine. Thanx a million
May 30, 2012 @ 19:26
Thats a win. Thats a fixed OWA win!!!
May 31, 2012 @ 06:23
Thank you so much! I was sure it was update related, however it just recently showed up and we install server updates weekly. There is so much garbage advice related to fixing this so thank you for being the real deal! You are the only one with the simple fix. Even Microsoft doesn’t have an easy answer on this. Yahoo!
June 2, 2012 @ 13:00
Thanks for this tip, worked great for me, this one is a keeper. Thanks, Mark
June 5, 2012 @ 23:33
Thank you! thank you! thank you!!!
What a simple solution!!!
I owe you also a beer!!!
June 18, 2012 @ 00:59
You just saved the rest of my Fathers Day, thank you!
July 2, 2012 @ 19:05
Very helpful and simple! Only issue I ran into was I did not run powershell as admin.
July 14, 2012 @ 00:17
Thanks very much. Also thanks Andres.
July 27, 2012 @ 11:24
August 13, 2012 @ 17:41
This saved me a great headache, thanks for the post!
August 16, 2012 @ 09:18
It was very helpfull.
Excahnge 2012 OWA stopped working after updating with Rollup7 for Exchange 2010 sp1.
I right clicked on UpdateCas and run it in PowerShell.
August 16, 2012 @ 14:17
Thanks man you saved my day 😉
August 17, 2012 @ 02:46
Thank you! Perfect…worked!!
August 21, 2012 @ 02:18
Awesome! Just saved me a ton of time tonight. Thanks!
August 23, 2012 @ 11:11
Thanks a lot … your Site help me to fix the Problem after Install Rollup 4 for Exchange 2010 SP2.
August 24, 2012 @ 21:49
Same issue for Rollup 7 kb2743248. I went to the BIN folder, under V14, scrolled down to UpdateCas.ps1, right-click, and left-click “Run with PowerShell”. Worked for me, bedankt Peter
August 24, 2012 @ 23:00
August 25, 2012 @ 13:54
August 30, 2012 @ 21:51
Thank you very much. Similar to Shairpoint’s psconfig it seems.
I will keep this in my list of useful commands.
September 4, 2012 @ 14:52
this is indeed a great post
September 4, 2012 @ 22:13
Thank you so much! Been searching for a while! it worked great!
Mike from Canmore
September 11, 2012 @ 22:29
Saved my butt…
September 12, 2012 @ 00:02
Third time this has happened this week!
September 18, 2012 @ 16:44
I just wanted to say thanks!! I have been beating my head against the wall for 2 days and finally came across this thread.
September 20, 2012 @ 13:10
September 26, 2012 @ 16:37
I spent many hours to find the solution in a couple of sites
October 9, 2012 @ 14:54
Thanks! This worked for me.
November 11, 2012 @ 13:11
Have this error on SBS2011 exchange 2010 after installing rollup update v7-2. Your solution was working for me.
November 26, 2012 @ 23:41
Thank you so much!!! All other websites talk about a useless IIS reinstallation. I cant believe Microsoft allowed this to happen, and hasn’t even released documentation about it!
December 10, 2012 @ 03:55
Thank you very much! It worked perfectly.
December 10, 2012 @ 08:48
Thank you very much for the solution! It works perfectly!
I am surprised that MS’s rollup can’t run the script automatically 🙂
December 16, 2012 @ 04:58
Works like a charm…thanks,
December 17, 2012 @ 00:38
you are a GOD… thanks resolve my problema too.
December 17, 2012 @ 11:07
Thanks a lot, easy and very useful trick|
dazed and confused
December 18, 2012 @ 00:22
Thank you very much for the advice. Worked like a charm.
December 19, 2012 @ 15:58
Does not work for me. This issue appeared after I installed on my SBS 2011 server, this update: Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908).
December 22, 2012 @ 05:13
I recently installed rollup5-v2 for exchange 2010 SP2 and had OWA blank page. This fixed it!Awesome!
I would like to understand why OWA displayed blank page after installing rollup. Our OWA is not customized.
December 26, 2012 @ 21:45
Glad i found this.
Still works after rollup 8
December 28, 2012 @ 17:27
Brilliant suggestion, save me hours today.It must be run as administrator.
January 4, 2013 @ 17:53
FYI for those who have never used powershell, just open the exchange management shell as administrator
cd to c:
and then just type updatecas.ps1
(so it will look like)
I was trying to run it from C:Program FilesMicrosoftExchange ServerV14Bin and it wasnt having any of it
January 21, 2013 @ 21:21
Thanks !! Worked for me…
January 30, 2013 @ 10:32
AWESOME, this is THE solutions thank you 🙂 much much
February 10, 2013 @ 03:12
OH MY GOD! I am currently drinking a nice cold one in your honor sir! THANK YOU SO MUCH! Why in the world would MS updates NOT do this?! After every rollup I suppose I should do this instead of attempting rebuilds on my virtual web directories.
You are the man!
February 17, 2013 @ 12:56
This helped a whole lot. Just had this issue after update6 on SP2 (e2k10) and this did the trick.
Chris ‘The Geek’
February 18, 2013 @ 15:01
Why oh why can’t Microsoft just clearly document this I don’t know – perhaps this info is only for the MS clique or something.
anyway – thanks for posting this, saved me some time. I’ll have a beer dedicated to you.
February 18, 2013 @ 17:13
Thank you for the resolution. Fixed the issue straight away.
EMS needs to be run as Administrator or you will get access denied errors.
February 25, 2013 @ 10:25
Thanks so much for this. Very useful and easy fix.
February 26, 2013 @ 19:28
Gracias me ayudo mucho y funciono rapido.
February 26, 2013 @ 21:02
If you already have RCP over HTTP Proxy installed as a feature, then this is all you need.
For those who said the RPC solution fixed it for them, that’s because you already ran the script.
March 5, 2013 @ 11:08
This is a work of genius.
April 30, 2013 @ 14:38
Yep, same after 3 years and rollup 7&8, this is very helpfull…
May 25, 2013 @ 22:02
Absolutely Brilliant. Been trying to fix this for ages.
Thanks very much.
June 5, 2013 @ 17:23
Spend a couple hours working on this, and this script solved my problem.
June 24, 2013 @ 12:22
My problem following Sp1 was the blank page being presented when you went into web outlook. I applied the script Updatecas.ps1 as suggested, but continue to get the following error when applying the script in the Exchange management Shell…
[12:15:43] Copying files from ‘C:Program FilesMicrosoftExchange ServerV14ClientAccessowaCurrent’ to ‘C:Program
[12:15:43] Found 1 OWA virtual directories.
[12:15:43] Updating OWA virtual directories
[12:15:43] Error updating OWA/ECP: Access is denied.
I’m continually getting OWA/ECP: Access is Denied. I have checked all security settings I can think of but to no avail. Any help would be greatly appreciated.
July 17, 2013 @ 07:18
June 18, 2015 @ 11:41
Brilliant!!!! Works even in 2015!!!
June 30, 2015 @ 22:43
Rollup9 für Exchange 2010 in SBS 2011 caused the OWA to have the blank Screen Problem again.
We are living in 2015 now and updatecas.ps1 is stil a solution that works.
Thanks a lot !!!
July 25, 2015 @ 01:06
Thank YOU! this was the final piece of the puzzle!
August 27, 2015 @ 14:55
I LOVE SMART PEOPLE. Your solution worked. Thank you.
March 12, 2016 @ 10:24
Perfect! Works like a charm.
March 15, 2016 @ 21:52
simple but Godlike..Thank you
April 5, 2016 @ 10:14
June 23, 2016 @ 08:44
Many thanks to you.
this realy safe my life.
this is realy simple and worked instantly.
SBS 2011 with Exchange 2010
July 22, 2016 @ 18:53
January 16, 2017 @ 10:46
it been pending about 2 months, its solved becuse of your clear and strait forwarred post.. and work approcah.
Big Thank you..