For the past several days, in the morning it appears that the clients are not able to connect. I'll check all services for Exchange and they are started. If I restart the server, it then works fine. When I go to just stop all the MSExchange services, I can stop them all except for the Information Store service. If I force stop the MSExchangeIS PID and then restart the service, also everything works fine again. I've checked the Application log in EV but can't find any errors. Is there anything else I can try?

On Wed, 27 Jun 2012 12:21:59 +0000, juicejug1016 wrote: >For the past several days, in the morning it appears that the clients are not able to connect. I'll check all services for Exchange and they are started. If I restart the server, it then works fine. When I go to just stop all the MSExchange services, I can stop them all except for the Information Store service. If I force stop the MSExchangeIS PID and then restart the service, also everything works fine again. > >I've checked the Application log in EV but can't find any errors. Is there anything else I can try? Before you do anything, have you checked to see if the status of the mailbox databases say "Mounted"? It would help if you mention what release, SP, and update rollup of Exchange you're using, and the O/S release and SP. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Sorry, Exchange 2007 SP2 on SBS 2011 Yes they are both mounted when this occurs. Edit- It looks like when it happens, if I open EMC and go to the mailbox to view the status, it hesitates for a bit and then seems to be running normal again.

You need to do some more troubleshooting, could be anything maybe the arp table is loosing entry for the exchange etc. When this happens next time see if OWA works on the client if not see if it works on the exchange server itself to determine if its an application issue or a network issue.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

OWA does work, but the problem still exists. I do now see event ID 4999 in the event viewer. I've since updated Exchange to SP3 and done all the updates but we are still having the issue.

On Mon, 2 Jul 2012 13:33:45 +0000, juicejug1016 wrote: >OWA does work, but the problem still exists. I do now see event ID 4999 in the event viewer. I've since updated Exchange to SP3 and done all the updates but we are still having the issue. That eventid is useless without the rest of the event details. Your description is a bit cryptic, too. Did you meant to say that you saw the event BEFORE you moved to SP3? Or that you saw it before AND after installing SP3? If it happeded before AND after is he event the result of the same problem (that's where the event description come in)? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I don't know how to get the rest of the event details you are looking for. It is happening before and after SP3

Watson report about to be sent to dw20.exe for process id: 6296, with parameters: E12N, c-rtl-AMD64, 08.03.0083.006, store.exe, MSVCR80.dll, 1e360, c0000005, 322, 8.00.50727.6195. ErrorReportingEnabled: False

On Tue, 3 Jul 2012 02:27:38 +0000, juicejug1016 wrote: >I don't know how to get the rest of the event details you are looking for. It is happening before and after SP3 Select the event and then, in the Actions pane, click "Copy" and select "Copy details as text". You can save the text into Notepad and paste it into your reply. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Tue, 3 Jul 2012 02:32:47 +0000, juicejug1016 wrote: >Watson report about to be sent to dw20.exe for process id: 6296, with parameters: E12N, c-rtl-AMD64, 08.03.0083.006, store.exe, MSVCR80.dll, 1e360, c0000005, 322, 8.00.50727.6195. ErrorReportingEnabled: False If the store is generating faults your best bet is to get MS involved. None of us have access to the source code. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP