Try downloading the Process Explorer from the
http://www.sysinternals.com/ntw2k/freeware/procexp.shtml and see if you
can find more information about Store.exe process.  I am not sure if it
will or not, but you never know.  Also, there's security fix, Exchange
Server 5.5 Post-SP4 RPC Fixes which will replace many files including
the Store.exe on your Exchange server.  You can look at the Q304062
article for more info.  Or you can run the Security Analyzer to see what
you need.

After applying SP, it's good idea to re-optimze your Exchange server
again.

Brian

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joe Haines
Sent: Tuesday, July 22, 2003 9:25 AM
To: Exchange Discussions
Subject: Store.exe pegging the processor


Hello all... need some help with an issue. here's my scenario


exchange 5.5 sp4 in a 2 site organization: The store.exe  has recently
starting pegging the processor. It almost looks like online maintenance
is
not releasing the store.exe after it has completed. We also run sybari
antigen 7.5 for exchange server. So i've:

1. disabled antigen and unhooked its services
2. searched the queues for any bouncing messages (mta size limit is
5.5mb
and imc size limit is 5.5mb)
3. reapplied service pack 4
4. run isinteg -fix -priv -test alltests
5. run isinteg -fix -pub -test alltests

Now with that being said... I did recently have a corrupt calendar on
the
server in the other site that replicates free/busy to the problem
server.
The corrupt calendar has been deleted but the other server is still
getting
pegged. (i know that's quite a reach)

I dont have a backup with recent enough info to do a restore and I'd
like to
avoid eseutil /p. Im wondering if I should do on an offline defrag to
create
a new database structure????

Any suggestions would be greatly appreciated

Thanks!!

************************************************************************
***
The information contained in this message is intended only for the
confidential use of the recipient(s) named above. This message is
privileged
and confidential. If the reader of this message is not the intended
recipient or any agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this document
in
error and that any review, dissemination, distribution, or copying of
this
message is strictly prohibited. If you have received this communication
in
error, please notify us immediately. SMG reserves the right to monitor
and
review all content sent to and from this email address. Messages sent to
and
from this address may be stored on the SMG email system. 

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to