STORE starts hogging CPU time early in the morning each day. NAV is set to ignore the Exchange Server data folders, letting NAVE take care of it, so there shouldn't be any conflict there.

Making the best of a bad situation, I no longer have to restart the entire server every day since finding the PSTools kit. (You can not stop the STORE service from 'Services' when it gets into this state.) The PSTools kit includes pskill.exe - a handy program that lets you stop a service that would normally return a 'Permission Denied' from task manager.

PSTools is available to download at SysInternals - www.systeminternals.com

I spoke to a guy a www.burleightech.com and he passed me this info:

Upgrade my ram

1. Stop the Exchange Directory service

2. Clean and defrag the directory:
Go to a command prompt and change to the D: Drive
Type: CD\EXCHSRVR\DSADATA
this will take you to the D:\EXCHSRVR\DSADATA directory
Type: C:\EXCHSRVR\BIN\ESEUTIL /p /ds
You will see a gauge come up and count to 100%, when it completes, the directory is done.

3. Start the Directory service
Type: NET START MSEXCHANGEDS

4. Next you want to clean and defragment the Information Store
Type: CD \EXCHSRVR\MDBDATA
This will take you to the D:\EXCHSRVR\MDBDATA directory
Type: C:\EXCHSRVR\BIN\ESEUTIL /p /is
Same counter as in step 2

5. Verify the integrity of the Private and Public stores
Type: ISINTEG -FIX -PRI -TEST ALLTESTS
This will take awhile, it runs a series of tests on the priv.edb. When it completes, check to see how many errors and warnings were generated. Typically if there is more than 20 errors I run it again.
Once it comes up clean type: ISINTEG -FIX -PUB -TEST ALLTESTS
This should go faster than the priv did.

6. Patch the Information store to match the clean directory service.
at the D:\EXCHSRVR\MDBDATA prompt
Type: C:\EXCHSRVR\BIN\ISINTEG -PATCH
When that completes successfully you will be ready to bring the server back online

7. Type: NET START MSEXCHANGEIMC