But after a customer had some SAN issues today, it suddenly appeared out of nowhere for a couple of users. The preceeding events were a store.exe process running amoc being completely unresponsive. Restarting the service left it hanging. After a reboot of the server, all looked well; but not for two users.
The were disconnected from Outlook, and logging on to webmail, they just got a less than helpful “there is something wrong with this mailbox” message.
Setting up a clean Outlook-profile returned the classic “Unable to open your default e-mail folders” message. Opening the properties on the mailbox gave me a System Attendant error message while browsing the calendar settings.
And best of all: No error messages anywhere. Not on the server, not on the client.
At this point I was pretty much going “what the hell??” to myself. And decided I might try to disconnect and reconnect the mailbox.
So I did a test-run with one of my test users first. But the mailbox didn’t show as a disconnected mailbox at first. So I did a “clean-mailboxdatabase” command to get it to show.
Lo and behold, the other mailboxes started working!
I honestly have to say that I’m not seeing the connection here, but it’s there apparently.
When everything else fails: clean-mailboxdatabase