Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1159
  • Last Modified:

Outlook Web Access not rendering properly for hosts.

We are having a problem at a customers site with Outlook Web access.  It works when I load the webpage locally on the server, page renders fine, but when we come from any other host, internal or external, it renders all funky. (see examples below)  I didn't see anything out of the ordinary in the logs, and if I keep hitting refresh, it will render a different way with a different error each time.

Is there either an easy fix for this, or an easy way to reset the webserver to its default settings?  I am not hosting any other websites on the server, and need to get this working for outside users.  Is there any reason this would load on IE on the server but no where else?


  • 4
  • 3
1 Solution
I can tell from the screenshots, but it would help if you posted the Exchange version in your question.

If it works on the server, then it looks like classic authentication issues. If it wasn't working anywhere, then I would suspect application.

Check the authentication of the Exchange virtual directories in IIS Manager:

/exchange - basic and integrated ONLY
/exchweb - anonymous ONLY
/exadmin - integrated ONLY
/public  - basic and integrated ONLY
/oma - basic ONLY
/Exchange-Server-ActiveSync - basic and integrated only

I would also check the application pools are correct:

/exchange - ExchangeApplicationPool*
/exchweb - ExchangeApplicationPool*
/exadmin - ExchangeApplicationPool*
/public  - ExchangeApplicationPool*
/oma - ExchangeMobileBrowseApplicationPool
/Exchange-Server-ActiveSync - ExchangeApplicationPool

veruscorpAuthor Commented:
Thanks Simon, sorry for leaving out some of the details.  It is a Windows 2003 server running Exchange 2003 SP2.  Some of the permissions and App Pools we're definately not set as you suggested, so I changed them to match up.  This seems to allow me to get a bit further, but the page still is not loading completely, and will load differently and with a different error every time I hit refresh ( see new screenshots below).  It seems like it will render any number of ways, I don't think I've seen the same page come up twice, it always looks different and has a new error.


Let me know if I am leaving out any other details that would be helpful.


Did you do an iisreset after making the changes?
If not, do that first.

Drop in to a command prompt and type


press enter and wait.

Before you trying connecting again, flush the temporary internet files in the browser.

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

veruscorpAuthor Commented:
I tried the iisreset and flushed all temp internet files out of the browser.  If I refresh the page 4 or 5 times, I can get a bit closer to a working interface, but it still isnt quite there. See new screenshot:  http://members.arstechnica.com/x/seedless/OWA5.jpg

Is this still looking like a permissions issue?  It seems to accept my username and password, and the errors all looked like the server isn't sending a page that will render properly judging by some of the errors, see below:

g_winDocAll.idFontSize.offsetHeight' is null or not an object

Unterminated string constant

'm_fAttach' is undefined

'L_ErrComm' is undefined

Thanks again for your help

You have the elements there, so it isn't an authentication issue.
Now it elsewhere in the OWA system.

I would be tempted to simply reset the virtual directories to their default and see if that fixes it.

Otherwise it could be something with the .net framework or something like that.

veruscorpAuthor Commented:
Well, we finally found what the problem was.... The binding order of the two adapters in network connections>advanced>advanced settings was backwards, and for some reason, even though the adapter was disabled in Windows, it was set higher in the binding order and this was causing the problem.  After switching the binding order and rebooting, OWA came up fine.

Thanks for your help along the way Simon.

Glad to hear that you got it fixed.
Don't forget the close the question. If you aren't sure on how to award the points, then post in the Support TA (top right corner) with a link to this question and the moderators will assist you.

PAQed with points refunded (500)

Community Support Moderator

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now