guramn
asked on
exchange 2010 sp1 owa blank screen
Hello everyone,
a couple days ago i installed new exchange 2010 sp1 on a fresh windows server 2008 r2 (CAS, HT, MBX - single machine).
All latest updates were installed on windows, and after installing exchange i applied all available updates too. i configured roles created mailboxes, applied new certificate. everything seemed allright, but when i checked owa, it didn't work, instead i'm getting blank screen and nothing else,
and url is changing to https://exchange.mydomain.com/owa/auth/logon.aspx?url=https://exchange.mydomain.com/owa/&reason=0
i searched internet a lot and found similar problems, caused by update rollups. i checked exchange updates and found only single exchange 2010 sp1 update rollup 2 installed. i removed the updated, but still the same, applied from command line (run as administrator) but still same problem, there should be simpler way then reinstalling exchange, i hope, as i have to put the server in production for tomorrow and users will need owa access.
and one more thing i applied all updates immediately after installing exchange, so i didn't notice when owa got wrong.
a couple days ago i installed new exchange 2010 sp1 on a fresh windows server 2008 r2 (CAS, HT, MBX - single machine).
All latest updates were installed on windows, and after installing exchange i applied all available updates too. i configured roles created mailboxes, applied new certificate. everything seemed allright, but when i checked owa, it didn't work, instead i'm getting blank screen and nothing else,
and url is changing to https://exchange.mydomain.com/owa/auth/logon.aspx?url=https://exchange.mydomain.com/owa/&reason=0
i searched internet a lot and found similar problems, caused by update rollups. i checked exchange updates and found only single exchange 2010 sp1 update rollup 2 installed. i removed the updated, but still the same, applied from command line (run as administrator) but still same problem, there should be simpler way then reinstalling exchange, i hope, as i have to put the server in production for tomorrow and users will need owa access.
and one more thing i applied all updates immediately after installing exchange, so i didn't notice when owa got wrong.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
all necessary components in iis weren't installed
http://blogs.msexchange.org/walther/2010/09/24/exchange-2010-sp1-experiecing-an-owa-http-500-error/