asked on

IIS Server getting Hanged

Hi Experts,

Since iam facing a big issues for a long time and unable to resolve this.

In my enviroment we have configured one MS exchange 2003 Front end server and 20 exchange Backend servers.
Currently 150 users configured to use RPC over Http/s facility.
Every 3 days my exchange front end server IIS server got hanged
for resolution If we restart the IIS admin service on exchange front end server then also the OWA will not be accessible and last we want to restart the server, if we restart the server then it's working properly.
Kindly help in this to resolve the issue.

Thanks in Advance

supports

do you get any event errors or does the IIS logs points out any issue....

sobitharaj

ASKER

There is no error/warning events recorded for this issue on event viewer.
This is the reason iam unable to find any solution

CorpComp

Is the IIS service consuming large amounts of Memory or CPU time when it hangs?

It might be useful to snap some key performance counters on the IIS service from the next time you restart it until it next crashes.

Here is a link to a bunch of useful counters for monitoring IIS. Setup perfmon to take a snap every 1 hour on a pile of the key counters in this article and then retrieve the counter after the crash to see what has changed unexpectedly from normal activity.

sobitharaj

ASKER

My server is normal, when the IIS server getting hang.
As per MS article i have checked the scalability of requests for RPC over Http/s.
now i need to start perfom monitor on this server.

Kindly assist which counters i need to add and monitor on this..

Thanks
Sobitharaj.S

MegaNuk3

Run the Exchange Best Practice Analyser (Exchange 2003 version):
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3

ExBPA will highlight any misconfiguration on there that you should resolve before doing any further troubleshooting.

sobitharaj

ASKER

After running EXBPA, I got the below errors, whether it will be the impact for IIS crash???
1. Free page table entries (PTE) on server abc.com is at the critical threshold. System instability may occur. Current free PTE count: 3582.
2. Exchange server abc.com has more than 4 GB of memory. To avoid severe kernel memory depletion, limit or remove physical memory. Memory count is 7991 MB.

Please guide me.

MegaNuk3

Exchange 2003 won't see or use anything above 4Gb or RAM so you might as well remove the extra RAM as system page table entries will be allocated to address RAM.

It is Exchange 2003 enterprise what OS is it running on? Windows 2003 standard or Enterprise.

I'd remove RAM till you are down to 4Gb and then see what happens with the server stability and free PTEs...

MegaNuk3

Hot Swap memory also eats PTEs.

Can you see if the below key exists:
HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\DynamicMemory (REG_DWORD) 1

If it doesn't exist then consider adding it as this will turn off hot swap memory support from an OS level.

As per: http://msexchangeteam.com/archive/2005/12/14/416065.aspx

MegaNuk3

Or instead of removing memory you can use BURNMEMORY in your boot.ini file:
use /BURNMEMORY=4096

as per http://technet.microsoft.com/en-us/library/aa997419(EXCHG.80).aspx

SOLUTION

sobitharaj

membership

This solution is only available to members.

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

Start Free Trial

MegaNuk3

Is the server not booting up at all now?

sobitharaj

ASKER

After adding this switch and rebooted the server, it's not entering into windows.
Please assist what could be the reason and why??

MegaNuk3

Boot off a floppy and then remove the burnmemory switch after that reboot and confirm windows starts properly again.

Then paste your boot.ini here

sobitharaj

ASKER

I have deleted the boot.ini file, now the server working fine.

This is the old file after adding /BURNMEMORY
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /NoExecute=OptOut /BURNMEMORY=4096

MegaNuk3

Have you thought about removing 4gb of RAM from the server to make EXBPA happy? And then see how stable the server is?

ASKER CERTIFIED SOLUTION

sobitharaj

membership

This solution is only available to members.

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

Start Free Trial

MegaNuk3

Have you resolved the issue?

MegaNuk3

Thanks for our help, but no points?

Is the server running fine now?