Had a weird one today that I'm hoping someone has insight. Exchange 2007 SP1, RU9. Multiple SG's. User's on only one database experienced issues logging in to their mailboxes. Those who were already logged in, either through Outlook or browser, were fine. Logging in was impossible. No warnings or errors were found in the logs, no MOM errors reported, and the database was mounted. We ran the BPA and database health check from the Toolbox, but again, no problems were reported. We dismounted the database, but were unable to mount thereafter. We tried bouncing the IS, but it wouldn't come down cleanly, so we had to resort to a reboot. The restart worked, all databases mounted, and no problems were reported in the logs. In our haste to get user function back up and running, we didn't take time to run any perf counters. While I'm glad the reboot worked, I'm uneasy because we don't know the root cause or how to prevent reoccurrence. Any advice would be most appreciated. Ted

Hi Ted, I would suggest you to increase loging level for MSExchange IS and analyze App log. http://technet.microsoft.com/en-us/library/bb201668(EXCHG.80).aspx . As you said problem is with only one database then you can move mailbox's from problemtic DB to new one and delete this. Please post your status.Anil

On Sat, 19 Jun 2010 01:27:04 +0000, TedF1 wrote: > > >Had a weird one today that I'm hoping someone has insight. Exchange 2007 SP1, RU9. Multiple SG's. User's on only one database experienced issues logging in to their mailboxes. Those who were already logged in, either through Outlook or browser, were fine. Logging in was impossible. No warnings or errors were found in the logs, no MOM errors reported, and the database was mounted. We ran the BPA and database health check from the Toolbox, but again, no problems were reported. > >We dismounted the database, but were unable to mount thereafter. We tried bouncing the IS, but it wouldn't come down cleanly, so we had to resort to a reboot. > >The restart worked, all databases mounted, and no problems were reported in the logs. In our haste to get user function back up and running, we didn't take time to run any perf counters. > >While I'm glad the reboot worked, I'm uneasy because we don't know the root cause or how to prevent reoccurrence. Any advice would be most appreciated. Using "test-mapiconnectivity" might have helped (with the emphasis on "might"). I think your problems were more than just not being able to connect to the database. :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, To improve the logging level in order to get more information when this issue reoccurring. Thanks Allen