Software

Ask something
Discussion Locked

Outlook Web Access Problem

0 helpful
6 replies

by rabbit_runner

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have Outlook Web Access enabled. Our exchange server is an NT 4.0 with Exchange 5.5 with SP6a and sp4 for exchange installed. Our DNS is installed on this exchange server.

Our Web server handles the OWA (Outlook Web Access) files and it runon an NT 4.0, sp6a, and running IIS 4.0 We have created a virtural web site for OWA which runs the Active Server Pages.

Most of the time, the OWA runs fine. But whenever we have to reboot the exchange server, the OWA will not work, until we reboot the Web server. (not to our liking) We have not been able to correct this problem.

Now, we have a situation that is happening on the weekends. Several of our staff use OWA on the weekend to check their email. We have been loosing our connection between the Web Server and the Exchange Server. Our exchange server is still running, anyone inside the LAN can access exchange with no problem. Also anyone who is accessing our Web site, can access any page normally, Except the Exchange OWApages. For some reason we are loosing the connection, and it will not access the Active Server Pages.

Does anyone have any ideas or suggestions? If I have not provided enough information, I will be glad to give additional info if it will help.
Thanks in advance

6 replies

by brian

Try opening the Management console and stopping the webservice and then restarting it whenever the exchange server is restarted.

by rabbit_runner

We have already stopped and restarted the Web site from within IIS and also the NT WWW service. Neither of these would allow us to reconnect with the OWA. The only option that we have found will work is to do a reboot.

Please, are there any more ideas? Thanks in advance.

by a.grogan

I have seen this before and it relates to IIS and the way in which ASP is functioning.

I suspect that you may need to rebuild the IIS server - but before you do - is there a way you could setup another IIS server with OWA on it and test the functionality - if it does not suffer from the same problems you know you have a rebuild on your hands.

by rabbit_runner

Thanks for the input, but this will not solve my problem, because the system is a BDC and the software on it, the developers do not (refuse) want to reload. :-)

Thanks

This discussion is closed to new replies.