Exchange 2003 Performance Issues
I have an Exchange 2003 server that is in the starting phases of an inter-forest migration. At Microsoft Support's direction, I have set up a configuration that forwards mail for unresolved recipients over to the Hub Transport server in the other forest. This will allow me to gradually migrate users (and mailboxes) to the other forest. I am still successfully receiving NDRs coming back into the source forest if the user hasn't been migrated over to the destination forest, so it appears message routing is working properly. However, since I put this configuration in two weeks ago, the Exchange 2003 server on the source forest has stopped responding twice. I have checked the Event Log and haven't found anything worth examining. After a restart of the physical server, Exchange comes back and functions properly. I noticed that store.exe ramps up to using over 1 GB of memory now, but I am not sure what a true baseline for it is. This server has about 150 mailboxes and is not receiving what I would consider a heavy amount of mail (probably closer to moderate). Please let me know some additional troubleshooting and performance tuning steps that I can take. Thanks so much!
April 6th, 2010 5:25pm

You could run Exchange Best Practices Analyzer. I'm sure you're already watching the event log. You could also start up a Performance Monitor job with relevant counters and change them if you don't catch anything useful. The memory ramping up is normal. Store.exe uses nearly all available memory to cache content and releases it when needed by other processes.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "heatfan2010" wrote in message news:d2b26d7d-6171-4661-9b7c-184d2039458e... I have an Exchange 2003 server that is in the starting phases of an inter-forest migration. At Microsoft Support's direction, I have set up a configuration that forwards mail for unresolved recipients over to the Hub Transport server in the other forest. This will allow me to gradually migrate users (and mailboxes) to the other forest. I am still successfully receiving NDRs coming back into the source forest if the user hasn't been migrated over to the destination forest, so it appears message routing is working properly. However, since I put this configuration in two weeks ago, the Exchange 2003 server on the source forest has stopped responding twice. I have checked the Event Log and haven't found anything worth examining. After a restart of the physical server, Exchange comes back and functions properly. I noticed that store.exe ramps up to using over 1 GB of memory now, but I am not sure what a true baseline for it is. This server has about 150 mailboxes and is not receiving what I would consider a heavy amount of mail (probably closer to moderate). Please let me know some additional troubleshooting and performance tuning steps that I can take. Thanks so much! Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2010 4:23am

I found that the Diagnostic logging was turned all the way up: HKLM\System\CurrentControlSet\Services\MSExchangeTransport\Diagnostics All values were set to "7". I changed all of them back to "0". After making this change, store.exe dropped down to ~170MB. It was previously over 1 GB in memory.
April 7th, 2010 7:35pm

Thank you for sharing the solution with us. It will benefit more people here. :)
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2010 6:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics