Outlook Web Access - Page cannot be displayed
Currently have OWA running on our Exchange 2003 server, and all works fine, then every so often, approx. once a month i can no longer connect to the web server, internally or externally. When you enter the url, and press go it states "page cannot be displayed". This to me looks simply like an IIS problem, so I've tried stopping and starting the Service in IIS Manager, it all starts up successfully, but still doesn't work when I open IE. Tried stopping all AV software then restarting the IIS manager services, still the same. The only way of resolving it, is by restarting the entire server.
Any ideas?
Any ideas?
next time it happens check to see if the HTTP protocol is started
exchange.GIF
exchange.GIF
Please cehck the firewall settings also...Antivirus integrated with firewall and do not stop antivirus services check that application having full control in firewall settings.
More Info:-
http://support.microsoft.com/kb/327843
Regards,
vijay kadadi
More Info:-
http://support.microsoft.com/kb/327843
Regards,
vijay kadadi
ASKER
Hello,
Yes I've checked the HTTP Exchange virtual server and it was running. I stopped and started it, and it had no effect. As for the firewall query, I've even tried running the OWA locally on the exchange server and nothing happens. I don't even get a logon prompt. I'm starting to think it is an IIS problem. I did try and set up a test web site, but it didn't work, I'm not sure whether thats because I've never set up a webpage before and done it wrong, or IIS isnt working. I'm going to give the exchange server a reboot tonight, and set up a working website, so I can test IIS next time it happens.
Yes I've checked the HTTP Exchange virtual server and it was running. I stopped and started it, and it had no effect. As for the firewall query, I've even tried running the OWA locally on the exchange server and nothing happens. I don't even get a logon prompt. I'm starting to think it is an IIS problem. I did try and set up a test web site, but it didn't work, I'm not sure whether thats because I've never set up a webpage before and done it wrong, or IIS isnt working. I'm going to give the exchange server a reboot tonight, and set up a working website, so I can test IIS next time it happens.
ASKER
Hello,
I've just re-booted the server and all is ok. If I just type the servers IP address into IE's url bar, it brings up a "under construction" page. This never happened before I rebooted, and its nothing to do with exchange, so it would indicate to me that its an IIS problem.
If I added, then removed IIS, would I lose my OWA website settings?
I've just re-booted the server and all is ok. If I just type the servers IP address into IE's url bar, it brings up a "under construction" page. This never happened before I rebooted, and its nothing to do with exchange, so it would indicate to me that its an IIS problem.
If I added, then removed IIS, would I lose my OWA website settings?
Locally you should be able to access OWA by typing in \\ip address\exchange
ASKER
I think your missing the point I'm making. I'm saying that web access is working now I've rebooted the server.
I think it's an iis problem, as even if I just type type fhe servers ip address now (forgetting owa), I get a web page back stating 'site under construction' which I didn't get before, so if therefor must be iis.
It seems that iis, is just stopping?
I think it's an iis problem, as even if I just type type fhe servers ip address now (forgetting owa), I get a web page back stating 'site under construction' which I didn't get before, so if therefor must be iis.
It seems that iis, is just stopping?
Over time, you will know if its IIS or not, depending on how often it fails, say every 3 days.
A reboot rarely helps, unless you've applied a software patch or upgrade and it was needed for changes to take effect.
I suspect that you will see OWA fail again, but the important thing to do is check that test web page to see if it loads at that time. Then, you will know if it's IIS or Exchange.
By the way, you have the latest service packs and updates for the OS and Exchange, right?
A reboot rarely helps, unless you've applied a software patch or upgrade and it was needed for changes to take effect.
I suspect that you will see OWA fail again, but the important thing to do is check that test web page to see if it loads at that time. Then, you will know if it's IIS or Exchange.
By the way, you have the latest service packs and updates for the OS and Exchange, right?
ASKER
Hello,
I've created a test web page, and after waiting for over two weeks the OWA failed again. I tested to see if my test web page was available, and it wasn't. Re-booted and resolved, this now definitely points to IIS.
Are there any tools or logs that can help me diagnose IIS. Or could I simply re-install IIS?
I've created a test web page, and after waiting for over two weeks the OWA failed again. I tested to see if my test web page was available, and it wasn't. Re-booted and resolved, this now definitely points to IIS.
Are there any tools or logs that can help me diagnose IIS. Or could I simply re-install IIS?
Did you find a solution to this problem?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
First thing I would determine is if it is an issue with IIS or Exchange.
Set up a simple ASP or HTML test page on the same web server. When OWA returns an error, try loading the test page. If the test page loads, then you will, at least, know that IIS is not having a problem. Also, since friendly error messages are turned off, you should get a slightly more descriptive error message to give you more guidance.