[ExchangeList] Re: Exchange 2003 Event ID 9659

You need to make sure McAfee is not scanning your any of your Exchange files.  Please review http://support.microsoft.com/kb/823166/ for more information.  You could try disabling McAfee and see if the crashes continue.

James also has an excellent point about examining the crash dump file.

Do you have any other Exchange servers in your environment, and if so, are they exhibiting the same behavior?

On 6/5/07, James Chong < jchong@xxxxxxxxxxxx > wrote:

Is there a dump file created when its crashing? If so run windbg.

 

Download MS debugger,

1. file open, crash dump, point to your minidump
2. inpute command !analyze -v;r;kv;lmnt;.logclose;q
3. Should show faulting module.

Install Debugging Tools for Windows 32-bit Version
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

 

 

James Chong (MVP)

MCSE | M+, S+, MCTS, Security+

msexchangetips.blogspot.com

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto: exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Dave stevens
Sent: Tuesday, June 05, 2007 11:43 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 Event ID 9659

 

Sorry guys a bit more information.

 

I just confirmed that the server is actually a windows 2000 standard server running on a HP DL360 G3 dual processor server. Just wondering if this issue might be resources related. We have 2 72GB disks mirrored with 2gb memory. Our IS is currently 25GB , stm file 11GB.

 

There doesnt seem to be much stuff out there relating to this issue and I am kinda running out of ideas. even thinking of a defrag to reduce the DB size.



Gideon12 <gideon12@xxxxxxxxx> wrote:

Check out http://support.microsoft.com/?kbid=872963, it describes exactly what you are experiencing with one exception, you are on SP2 and the article is for SP1.

Did you encounter any kind of issues when you installed SP2?

Also, be sure that you don't have any anti-virus software running on your Exchange server that is allowed to scan the transaction logs.  Things do not work well when AV is scanning a log while backup software is trying to commit it.

On 6/5/07, Dave stevens <london31uk@xxxxxxxxx > wrote:

Hi Guys,

 

this is a strange one, but getting pretty critical.

 

Environment

Windows 2003

Exchange 2003 Sp2

Symantec Backup Exec V10.0

we have been experiencing the following problems everytime we run full backup

 

The Information Store just craches with the following event ids

 

Event Id: 9659 - Source MSExchangeIS

Event Id: 1000 - Source Microsoft Exchange Server.

 

Thanks

 

Dave

 

Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when.

 

 

 

You snooze, you lose. Get messages ASAP with AutoCheck
in the all-new Yahoo! Mail Beta.


Other related posts: