Exchange config changes leads to MWI issue... please help! 1

[wheelma2]

Our Microsoft Exchange Administrator has setup a new information store and moved most of our IT group to the new store as "guinea pigs". Now, those of us who have been moved are not getting MWI. We have no other known issues as a result of this change... we just don't get MWI now.

I have tried restarting the MWI service on the MAS, but that didn't correct the issue.

The following Warning is present in Event Viewer on the MAS for each of the users who have been moved to the new information store in Exchange....
Source: gv_mwiserver
Category: General
Type: Warning
Description: The Message Waiting Indicator service failed to initialise mailbox monitoring for user EX:/O=<company_name>/OU=<ou>/CN=RECIPIENTS/CN=<username>. There may be a general problem with access to the Mailbox Monitor Server, or there may be a specific problem with this user's mailbox. (HR=0x80004005).

Information from our Exchange Admin...

Day 1: "I moved users from one information store to another information store within the same storage group. All permissions were inherited correctly. The store we moved to, was a new store that was created a day prior, to be sure all of the Domain controllers knew it was there."

Day 2: "I have been watching yesterday and today and I see that the modular messaging service account is accessing the mailboxes of the users on the new stores."



We have a ticket open with our Avaya Partner, but they haven't provided a solution yet. I'm hoping someone here will have a suggestion.

Thanks in advance!

 

[texeric]

That error is a generic denial. Check to make sure the MM service account has the correct permissions on this new store/DB, which I'm assuming is on the same Exchange server as those that are working.

Also if your mailbox is moved, meaning moved to another DB (even on the same Exchange server), Storage Group or Exchange server, then features like Call Me, Notify Me and MWI will be broken until the 3 services (Mailbox Monitor, Call Me, and MWI) are restarted.

http://www.theviagroup.com

 

[wheelma2]

Restarting the Mailbox Monitor service (which forced a restart of the Call Me and MWI services also) seems to have fixed the issue.

I was curious if that service needed to be restarted, but I was hesitant since I wasn't really sure what all that service did. Oddly enough, not long after I recieved your reply I also recived the same suggestion from our BP.

Thanks for the advice, much appreciated!