Hi, The Process store.exe. is taking 100% of my cpu. There is my setup: Exchange 2003 SP2 on Windows 2003 Entreprise SP3. Everything is uptodate. Running on VMware 4.1. 2x 2.4 Ghz with 4 GB of Ram. We have 180 users, 25 Iphone and 60 Blackberry connected on this server. There is what I try: ExBPA: Everything is OK. Exmon: Some user are loading but it's not the same user always. Eseutil: scan my 3 DB Scandisk: Done All my log and database are on different partition. I have no error on the event log. When the store.exe take 100% of my CPU, i'm staring to get delay on the email up to 1 hours. I have some disconnection from the Outlook and the Iphone but without error on them. I try to disconnect all my iphone (stop IIS) and shutdown my BES... no change on the store.exe Even after a reboot, it's not better. I try 3 KB and apply the patch from Microsoft and no change. Also, the queue and bad email are empty. I call Microsoft and their don't want to help me since I'm on VMware... what ever. I know that is not the problem. Somebody have an idea? Regards, Marc

Hi Mark, Can you dismount all 3 DB once and mount it one by one with some time difference. If you see any perticular DB is eating much resource then check the health of this and later you can consider move mailbox from this DB. Please post the updates.Anil

Confirm AV is not real time scanning your DB's configure the /3gb switch as appropriate in your boot.ini etc and confirm your virtual memory settings.

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /PAE /3GB /USERVA=3030 /BURNMEMORY=4096 I try to dismount my db one at the time and it's the same thing. There is no AV on this server.

RUn ExBpa against the server. ALso, can you raise the CPU to 4 and test? When did this start?

Increase disgnostics logging, check performance logging, last thing you may attempt is defrag the database one at a time on a remote machine .. /d and then isinteg -fix

Please temporarily turn off SMTP service to check the result. Does the issue persist? Meanwhile, please collect Store dump by ADPLUS utility. a. Download windbg from the following location http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx b. Install it on the problematic server c. Create a folder to place dump files (e.g. c:\dump) d. Open a command window, navigate to the folder that debugging tools for windows installed, normally, it is C:\program files\debugging tools for windows f. Run the following command “cscript adplus.vbs -crash -NoDumpOnFirst -iis -pn store.exe -o c:\dump” (without quotes) g. Click ok button if there are any popped up window. Note: Do note close any command window, let adplus.vbs run until the problem reproduced Reference: http://support.microsoft.com/?id=286350 h. Please collect the dump file and send it to me for research. Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

AndyD_: I try to raise it to 4 CPU and it's talking at 100%. Like I said in my first post, I already run EXBpa and there is no error or warning. Khoi: I try to raise up the loggin and I'm still have no error for exchange on my Application Log. Novak: I'm working on this and send to you the information in 1 hours. Also, I note that when I stop IIS, the store process start to go normaly. As soon has I start IIS again, it's start to take the CPU again. I try to stop SMTP, I have no difference. Thanks, Marc

When you're at 100% it's hardly due to lack of resources and more due to some run away process whether it's due to some misconfiguration, bug, third party app etc. You mentioned that there is no av on the server, I also wouldn't doubt that your box is infected. The only way to isolate the affending process is to do the dump that novak suggested. You can also install an Exchange aware AV and scan to determine if you're also infected.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

I agree with Jamestechman, check to see if you have some process sucking up the CPU. Pidexplorer may help but if the store is the only one consuming the cpu, you may have something like maintainance running or some sort of mailbox notification process running. check your policies on each db for warning limits. Y