• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 841
  • Last Modified:

OWA failing - memory issues on Exchange 2003

I have setup a new Exchange Server and I ran the best practices analyzer tool which told me to add the /3GB and /USERVA=3030. I did that but have been getting the errors below in the HTTPERR log. I followed this kb (http://support.microsoft.com/kb/934878) and added the reg key for aggressive memory usage. This fixed OWA but it failed again today with the same errors in the HTTPERR log until I reset IIS. When I run Best Practices Analyzer it tells me that Nonpaged pool memory is critical - 119MB.


Thanks,
Bobby


2010-01-08 16:00:34 - - - - - - - - - 5_Connections_Refused -
2010-01-08 16:00:39 - - - - - - - - - 1_Connections_Refused -
2010-01-08 16:01:09 - - - - - - - - - 12_Connections_Refused -
2010-01-08 16:02:24 - - - - - - - - - 1_Connections_Refused -
2010-01-08 16:02:49 - - - - - - - - - 12_Connections_Refused -
2010-01-08 16:03:39 - - - - - - - - - 1_Connections_Refused -
2010-01-08 16:04:24 - - - - - - - - - 2_Connections_Refused -
2010-01-08 16:04:29 - - - - - - - - - 6_Connections_Refused -
2010-01-08 16:04:44 - - - - - - - - - 2_Connections_Refused -
0
ob1_
Asked:
ob1_
1 Solution
 
lastlostlastCommented:
The steps mentioned in KB 934878 is not to resolve the issue but it is a temporary relief to get OWA to work.
Even performing a 'iisreset' sometimes can fix the issue for a couple of hours... but it does not resolve it.

The "connections_refused" are logged in as the 'Non-Paged Memory' pool consumption by the IIS is too high i.e. > 100 MB.

You might have to take a performance dump of the IIS to see as to why it is leaking the memory and fix the same.

There are quite a lot of logs that need to be analyzed from the server. I would suggest you engage a performance guy or contact MS Performance team to help you with Non-paged pool memory leak issue.

Let us know how it goes.

0
 
ob1_Author Commented:
I will open a case with MS on Monday if I can't get it fixed this weekend. I am going to reboot the server tonight per the suggestions in the Best Practices Analyzer. If anyone else has more info please let me know.
 
Thanks,
Bobby
0
 
DotxCommented:
Il sugest you use performance monitor to check memory related counters
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
DotxCommented:
and question about spam filter ,what you using?
0
 
ob1_Author Commented:
I use MX Logic Spam filter but it is an external service and is not on our Exchange server.
I am checking the Free System PTE in Performance Monitor and the value is 9554. This kb on the /USERVA switch (http://support.microsoft.com/kb/810371/en-us) says anything below 7000 is too low but that the target value is 24000, and that I should adjust the value in the Userva switch down to raise the # of Free System PTE's. Do you think that is the issue?
0
 
Satya PathakLead Technical ConsultantCommented:
I would suggest you.
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB /USERVA=3030 /BURNMEMORY=8192 /PAE


http://support.microsoft.com/kb/815372
0
 
ob1_Author Commented:
I don't see anything regarding /burnmemory or /pae in the linked kb - what do they do?
0
 
ob1_Author Commented:
It appears the issue is with DNS.EXE - which is utilizing 15000k of NP pool. I am going to delete this question and repost more accurately. Thanks for trying to help.
 
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now