I have a very annoying ongoing issue, every couple of days our OWA site goes down along with any other IIS sites running on our Exchange server. There is nothing interesting in the event logs pointing to any problems with IIS. The annoying part is that restartting the IIS services does not resolve the issue, I have to completely reboot the server for the OWA site to work again. Everything else on the Exchange Server works fine. I am running Exchange 2003 on Windows 2003 SP2. Everything is up to date, so I have the latest version of IIS.
Any suggestions would be great.
How much memory do you have in the Exchange server? Do you have the /3gb switch in the boot.ini file?
Also, do you have one server for both the mailboxes and for outlook web access? Why did you mention other sites in IIS; is your OWA server hosting webpages other than exchange?
0
Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
To answer the first question, I looked at the IIS logs, nothing really of interest there either. We currently do not use RPC over HTTP so there is no service for that. And last but not least, the server has 4GB and has the /3GB switch in the boot.ini. One server is used for mailboxes and owa. The owa is not hosting other webpages other than exchange, we just have another site for our exchange antivirus protection in IIS. It is just odd that this would happen, sometimes the entire OWA site will not work, and sometimes just the activesync for oma will not work. During these down periods, All services required to run owa and oma appear to be running. I can't even browse locally on the server when this happens.
How many processor cores does this machine have when you open task manager? Each core requires 128MB of RAM. If you have eight cores and only 4GB of RAM, your cores and the information store process are consuiming all the memory and IIS is being starved of memory. If the processors are dual core with hyper-threading, simply turing off hyper-threading in the BIOS could fix your problem.
0
Hector7869Author Commented:
I am showing a total of 4 cores total. It seems that most of the suggestions are leading to a lack of memory. Do you think that upgrading to another 2GB of memory would help?
Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.