asked on

OWA will not work on Exchange 2003, shows red crosses and no icons

I recently installed Exchange 2003 on a Windows 2003 Server. The server is on SP2, Exchange is on SP2 also. All was well for a few weeks as far as Outlook Web Access is concerned until recently. Now OWA simply loads up a load of big icons with red crosses in each of the boxes and will not show you any messages. Everything else on the server works fine, all clients on local Outlook 2003 work fine.

It matters not what machine I try and log on to OWA from, still the same, even on the server itself.

The only thing I can assume that has happened is that someone else has loaded another application (Autodesk Vault Manager) which has made some changes to IIS in some way to throw out the OWA.

I'm not sure where to start.

rakeshmiglani

you might have to reset the exchange virtual directories in IIS
http://support.microsoft.com/kb/883380
http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html

inbarasan

Just restart IIS and Check once.

andrew_2706

ASKER

I have done all of the bove to no avail. All the directories in IIS have re-created themselves, I've checked permissions etc and all seems ok. Then I restarted IIS and still just get big blue boxes with red crosses in them.

andrew_2706

ASKER

Not sure if this helps, but if I click on one of the icons with a cross in the box I get error on page, the details of which show:
Line:96
Char:1
Error:Object Expected
Code:0

Not sure what this means but I'm sure its relevant to the problem.

ASKER CERTIFIED SOLUTION

andrew_2706

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

phrea84

andrew--i am having this same issue. what permissions did you set to resolve this?

andrew_2706

ASKER

Hi I'm sorry I can't help with this as I have slept since 3.5 years ago! I'm not sure which server it was in order to check it out either, there must be more info on here I would have thought. The most common issue I have come acrtoss is that the IIS folders do get the permissions mixed up and need resetting, Sorry for being unhelpful.
Andrew.