IS Stopped

Hi
Running W2K SBS - all patched up - with Exchange 2000 (again all pathced up.)
The IS store stopped today. I restarted it without problem. However I cannot
find any reason why it should stop.

Belwo are the reactive event log errors - but apart form that I am at a loss
as to where to begin troublehsooting this. Badmail folder did not have
anything in it apart from a few messages from hours earlier that day.

Any ideas please?

Thanks in advance

Lewej

********************

Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 1005
Date: 26/04/2005
Time: 12:32:51
User: N/A
Computer: JAVANT01
Description:
Unexpected error <<0xc1050000 - Network problems are preventing connection
to the Microsoft Exchange Server computer. An unexpected, unknown error has
occurred. Microsoft Exchange Server Information Store ID no:
80040115-0514-000006ba>> occurred.

For more information, click http://www.microsoft.com/contentredirect.asp.

*****************************

Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 26/04/2005
Time: 12:34:01
User: N/A
Computer: JAVANT01
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

For more information, click http://www.microsoft.com/contentredirect.asp.

***************************

Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 1005
Date: 26/04/2005
Time: 12:34:01
User: N/A
Computer: JAVANT01
Description:
Unexpected error <<0xc1050000 - 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>> occurred.

For more information, click http://www.microsoft.com/contentredirect.asp.

****************************

Jim
Tue Apr 26 18:03:42 CDT 2005

Do you have lots of hard drive space free on all partitions?

"Lewej" <Lewej@discussions.microsoft.com> wrote:

>Hi
>Running W2K SBS - all patched up - with Exchange 2000 (again all pathced up.)
>The IS store stopped today. I restarted it without problem. However I cannot
>find any reason why it should stop.
>
>Belwo are the reactive event log errors - but apart form that I am at a loss
>as to where to begin troublehsooting this. Badmail folder did not have
>anything in it apart from a few messages from hours earlier that day.
>
>Any ideas please?
>
>Thanks in advance
>
>Lewej
>
>********************
>
>Event Type: Error
>Event Source: MSExchangeSA
>Event Category: Monitoring
>Event ID: 1005
>Date: 26/04/2005
>Time: 12:32:51
>User: N/A
>Computer: JAVANT01
>Description:
>Unexpected error <<0xc1050000 - Network problems are preventing connection
>to the Microsoft Exchange Server computer. An unexpected, unknown error has
>occurred. Microsoft Exchange Server Information Store ID no:
>80040115-0514-000006ba>> occurred.
>
>For more information, click http://www.microsoft.com/contentredirect.asp.
>
>*****************************
>
>Event Type: Error
>Event Source: MSExchangeSA
>Event Category: MAPI Session
>Event ID: 9175
>Date: 26/04/2005
>Time: 12:34:01
>User: N/A
>Computer: JAVANT01
>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
>
>For more information, click http://www.microsoft.com/contentredirect.asp.
>
>***************************
>
>Event Type: Error
>Event Source: MSExchangeSA
>Event Category: Monitoring
>Event ID: 1005
>Date: 26/04/2005
>Time: 12:34:01
>User: N/A
>Computer: JAVANT01
>Description:
>Unexpected error <<0xc1050000 - 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>> occurred.
>
>For more information, click http://www.microsoft.com/contentredirect.asp.
>
>****************************

Jim B. SBS MVP
I don't have much to say but it can be found here
http://msmvps.com/bgb/

Lewej
Wed Apr 27 01:52:06 CDT 2005

Hi Jim
Ah - good thought - but no, there is plenty of space now, (and has been for
some months.)
Thanks
Lewej


"Jim Behning" wrote:

> Do you have lots of hard drive space free on all partitions?
>
> "Lewej" <Lewej@discussions.microsoft.com> wrote:
>
> >Hi
> >Running W2K SBS - all patched up - with Exchange 2000 (again all pathced up.)
> >The IS store stopped today. I restarted it without problem. However I cannot
> >find any reason why it should stop.
> >
> >Belwo are the reactive event log errors - but apart form that I am at a loss
> >as to where to begin troublehsooting this. Badmail folder did not have
> >anything in it apart from a few messages from hours earlier that day.
> >
> >Any ideas please?
> >
> >Thanks in advance
> >
> >Lewej
> >
> >********************
> >
> >Event Type: Error
> >Event Source: MSExchangeSA
> >Event Category: Monitoring
> >Event ID: 1005
> >Date: 26/04/2005
> >Time: 12:32:51
> >User: N/A
> >Computer: JAVANT01
> >Description:
> >Unexpected error <<0xc1050000 - Network problems are preventing connection
> >to the Microsoft Exchange Server computer. An unexpected, unknown error has
> >occurred. Microsoft Exchange Server Information Store ID no:
> >80040115-0514-000006ba>> occurred.
> >
> >For more information, click http://www.microsoft.com/contentredirect.asp.
> >
> >*****************************
> >
> >Event Type: Error
> >Event Source: MSExchangeSA
> >Event Category: MAPI Session
> >Event ID: 9175
> >Date: 26/04/2005
> >Time: 12:34:01
> >User: N/A
> >Computer: JAVANT01
> >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
> >
> >For more information, click http://www.microsoft.com/contentredirect.asp.
> >
> >***************************
> >
> >Event Type: Error
> >Event Source: MSExchangeSA
> >Event Category: Monitoring
> >Event ID: 1005
> >Date: 26/04/2005
> >Time: 12:34:01
> >User: N/A
> >Computer: JAVANT01
> >Description:
> >Unexpected error <<0xc1050000 - 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>> occurred.
> >
> >For more information, click http://www.microsoft.com/contentredirect.asp.
> >
> >****************************
>
> Jim B. SBS MVP
> I don't have much to say but it can be found here
> http://msmvps.com/bgb/
>

Jodie
Fri Apr 29 09:15:00 CDT 2005

My background is in desktop support, but I have recently taken over server
administration for my company. My predecessor setup a batch file to run
nightly that resets ExchangeIS. He told me that Exchange was freezing ever
1-3 weeks, requiring a reboot and that this scheduled task band-aided it.

The batch file is simply

Net Stop MSExchangeIS
Net Start MSExchangeIS

I truly don't know if this is a best practice or not, but I don't have
nearly as many Exchange problems as he was having before he set that up.

J.

SuperGumby
Fri Apr 29 15:31:27 CDT 2005

The other 99.999999999999999999999999999999999999 percent of Exchange
servers on the planet _only_ get restarted shortly after patch Tuesday (2nd
Tuesday, most months). If I was in your situation I'd be wondering why.

"Jodie Marshall via WinServerKB.com" <forum@WinServerKB.com> wrote in
message news:7ceb7b9d40d24a6e8c6696faa56ad5cf@WinServerKB.com...
> My background is in desktop support, but I have recently taken over server
> administration for my company. My predecessor setup a batch file to run
> nightly that resets ExchangeIS. He told me that Exchange was freezing
> ever
> 1-3 weeks, requiring a reboot and that this scheduled task band-aided it.
>
> The batch file is simply
>
> Net Stop MSExchangeIS
> Net Start MSExchangeIS
>
> I truly don't know if this is a best practice or not, but I don't have
> nearly as many Exchange problems as he was having before he set that up.
>
> J.