Is the service crashing or stopping gracefully? If crashing, there should be some debug info, your events logs system should give you some indication if it?s crashing or stopping gracefully events 7031. For grins run Ntbackup tonight instead of Symantec. Anything in the Symantec logs? Also set diagnostic logging for dsaccess, let?s see if your Exchange box is having issues communicating with your DCs.
You also mentioned that when this happens IS fails to recover.
Start run drwtsn32 ?i
Start run drwtsn32
Check dump symbol table, Dump all threads, Append to existing log file,
Create crash dump. Not where the dump file is created. When you start the IS service and crashes check to see if the dump file is generated.
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: Wednesday, June 27, 2007 10:05 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Exchange 2003 Sp2 Error 9175 and 1005
Well most of the time when this error is logged is during the full backup. So we set service recovery to restart of failuer twice. Not quite sure if that is working as we come in the morning to meet the service down.
We are currently using
symantec backup exec 10.0d.
Nothing else in the logs besides this.
Dave
James Chong <jchong@xxxxxxxxxxxx> wrote:
Your IS stops during backups? Can you describe fails to recover? You mean during backup process or it is currently down? What backup software are you using? Anything else in the logs besides that?
James Chong
Sr. Systems Engineer
InPhonic, Inc.
10805 Parkridge Blvd.
Reston, VA 20191
O (703) 657-4612
C (703) 863-1483
From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Dave stevens
Sent: Tuesday, June 26, 2007 11:16 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Exchange 2003 Sp2 Error 9175 and 1005
We been having this error for so,etime now, and it is driving me crazy.
Not quite sure what it is, but we seem to get this during our full
backups, The problem is that the IS falls over and fails to recover. I am now thinking of going down the route of a total exchange rebuild cos this is getting pretty critical, and I do not seem to be getting thr right pointers to the problem. MS resolution is very vague and unhelpful. Maybe someone can advice on the error below.
Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event
ID: 9175
Date: 26/06/2007
Time: 07:45:32
User: N/A
Computer: EXCH003
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
