Comments on: Outlook Web Access page not displaying properly

By: colinnz

colinnz — Sat, 29 Jan 2005 15:32:46 +0000

You don’t say whether the server is a domain controller or not..

A working Exchange 2K member server dcpromo’d would break OWA – requiring much work to get going again. (the local IIS IWAM and IUSR accounts are no longer valid once the machine is a DC)

If this could be your problem, uninstall/reinstall IIS and OWA after your server has been DCPromo’d to be a DC. That way the IWAM and IUSR accounts get created in the domain, rather than the local machine. This allows ASP pages to load correctly.

Does the event log display any errors when the OWA page is downloaded?

By: madwand

madwand — Thu, 30 Dec 2004 11:17:41 +0000

May not be related … but we saw a similar issue on some test PCs running Outlook 2003 with local file caching .. there is an interal zone setting on the Security Tab .. had to update from “Restricted Sites” to “Internet” before anything containing HTML content would load or display correctly. There might be a similar setting in the OWA client.

By: petroleumman

petroleumman — Thu, 30 Dec 2004 09:17:49 +0000

Hello Russ,

Here is a great MS KB Article that may help you troubleshoot your problem. It describes several scenarios which cover SSL, Permissions, Firewalls etc. all of which can create symptoms such as your experiencing. You did not mention what browser version your using, whether your config includes SSL or if a Firewall is present and where your server sits in relation to it (i.e. trusted or external-DMZ)or whether or not you have tried accessing your OWA site from other (alternatley configured)computers.

Check this article out and if it does not help, post a more detailed discription of your server/network config as that should shed a brighter light on your problems.

http://support.microsoft.com/?kbid=280823

Good Luck!

By: eunisaao

eunisaao — Wed, 29 Dec 2004 16:33:31 +0000

If I remember correctly it has something to do with either permisions or scripts no set to execute. You either don’t have permission to the scripts directory or you don’t have script execution turned on in the exchange virtual directory. I believe it has something to do with one or both of these.