Home All Groups Group Topic Archive Search About

Exchange 2003 Becomes Unresponsive

Author
11 May 2009 3:06 PM
Jeff Tucker
Hello,

We have 2 clients currently experiencing this issue. Periodically the
Exchange 2003 SP2 server (SBS) becomes unresponsive to connections from
Outlook client, OWA, BackupExec, ActiveSync, etc. The only thing that can be
done to continue the connections is to end the store.exe process in task
manager. The Information Store cannot be stopped in services. Once the store
process is ended the Information Store in services starts without a hitch.
There are no errors in the Application Event logs except for Server
Activesync 3007 and 3014 after the store has become unresponsive. I have
tried to go through the logs to determine a commonality between the events
such as scheduled processes yet I cannot find anything.

I am avoiding calling MS support until all other hopes have been
extinguished. Any ideas are welcome.
--
Jeff Tucker
Doran Consulting
Virginia Beach, VA

Author
11 May 2009 7:47 PM
DamageJackal
Hi,

Have you tried using Diagnostics Logging?

Try setting the ones related to IS to medium or maximum.
If you still get nothing you can try tweaking it to 7 using the Registry
at HKLM\System\CurrentControlSet\Services\MSExchangeIS\Diagnostics.
If you set the logging level to 7, remember to increase the Application
Log size because you'll be getting A LOT of messages.

Just do yourself a favor and turn the logging off once you're done. :)


DJ

Jeff Tucker wrote:
Show quoteHide quote
> Hello,
>
> We have 2 clients currently experiencing this issue. Periodically the
> Exchange 2003 SP2 server (SBS) becomes unresponsive to connections from
> Outlook client, OWA, BackupExec, ActiveSync, etc. The only thing that can be
> done to continue the connections is to end the store.exe process in task
> manager. The Information Store cannot be stopped in services. Once the store
> process is ended the Information Store in services starts without a hitch.
> There are no errors in the Application Event logs except for Server
> Activesync 3007 and 3014 after the store has become unresponsive. I have
> tried to go through the logs to determine a commonality between the events
> such as scheduled processes yet I cannot find anything.
>
> I am avoiding calling MS support until all other hopes have been
> extinguished. Any ideas are welcome.
Author
21 May 2009 1:31 PM
Gary D
We and others have same problem. see "Exchange Information Store
Unresponsive" in microsoft.public.windows.server.sbs  newsgroup.  Appearing
to be A/V related especially TREND WFBS5 but not finalised yet.

Gary D
Show quoteHide quote
"DamageJackal" <d*@wimr.com> wrote in message
news:004cf7d9$0$13480$c3e8da3@news.astraweb.com...
> Hi,
>
> Have you tried using Diagnostics Logging?
>
> Try setting the ones related to IS to medium or maximum.
> If you still get nothing you can try tweaking it to 7 using the Registry
> at HKLM\System\CurrentControlSet\Services\MSExchangeIS\Diagnostics.
> If you set the logging level to 7, remember to increase the Application
> Log size because you'll be getting A LOT of messages.
>
> Just do yourself a favor and turn the logging off once you're done. :)
>
>
> DJ
>
> Jeff Tucker wrote:
>> Hello,
>>
>> We have 2 clients currently experiencing this issue. Periodically the
>> Exchange 2003 SP2 server (SBS) becomes unresponsive to connections from
>> Outlook client, OWA, BackupExec, ActiveSync, etc. The only thing that can
>> be done to continue the connections is to end the store.exe process in
>> task manager. The Information Store cannot be stopped in services. Once
>> the store process is ended the Information Store in services starts
>> without a hitch. There are no errors in the Application Event logs except
>> for Server Activesync 3007 and 3014 after the store has become
>> unresponsive. I have tried to go through the logs to determine a
>> commonality between the events such as scheduled processes yet I cannot
>> find anything.
>>
>> I am avoiding calling MS support until all other hopes have been
>> extinguished. Any ideas are welcome.