When I reboot my Exchange server I receive Event ID 4001 from"MSExchange System Attendant Mailbox" with thedescription"A transient failure has occurred. The problem may resolve itself in awhile. The service will retry in 56 seconds. Diagnostic information: Cannot open mailbox {Information Store}..." The "Microsoft Exchange Information Store", which runs under the default "Local System Account", is stopped. Here's the peculiar part: if I manually start the service it loads just fine.This is Exchange 2007 SP1 on Windows 2008 Server.Jeremy

My guess is that your server is looking for services (like DNS) and they are not available at boot-up.

I'm going totry setting the information store to "Automatic (Delayed Start)" and see if that solves the problem. Seems like that "ought not" be necessary, but....

Jeremy,I suspect you may be running Ex2007 on your Global Catalog (or only DC). If you have other DC's, take the GC role off this one. If this is your only DC, think about adding another, or better two and take the DC role off this server completely.Look here:http://support.microsoft.com/default.aspx/kb/940845Ross

Hi, 1. First please disable RSS on the Broadcom NIC for Windows 2008 Server. 2. Please disable Offload Checksum" option on the NIC. 3. If you are running Macfee on the Exchange Server, then please try to disable MACfee Framework Service and then check the issue. Besides, Id like to know if the issue occur after you installed Rollups for Exchange 2007 sp1.If yes, then please follow kb 944752 to correct the issue. Exchange Server 2007 managed code services do not start after you install an update rollup for Exchange Server 2007. http://support.microsoft.com/kb/944752/ If not, then please try to run dcdiag from a command prompt to check whether your domain controller is normal. Dcdiag Overview http://technet2.microsoft.com/WindowsServer/en/library/f7396ad6-0baa-4e66-8d18-17f83c5e4e6c1033.mspx?mfr=true Regards, Xiu

Ross is correct. This is a Global Catalog. We're a small organization and are currently in the middle of a domain migration; once that is complete we will have two Domain Controllers and can move the Global Catalog to the other server. Oddly, I don't have any of the events noted in that KB article but it otherwise describes the symptoms and environment perfectly.That said, setting the Information Store service to "Automatic (Delayed Start)" effectively works around this problem. Although Isuspect some of the methods mentioned in KB940845might be more universal since they include either a) setting specific dependencies (Method #2) or b) a configurable delay (Method #3).Thank youfor your help.Jeremy