moved exchange 2010 mailbox to another database active on another mailbox server, now getting error
hi
i have a DAG setup spread over 3mbx servers with mailbox server 1 and 2 spreading the active load (half mailbox are active on mbx server 1 and the other half on mbx server 2, mbx server 3 is in the DR site for DR purposes.
each mbx server has its own enterprise vault (v9.0.2) account and all was working fine till i moved a mailbox from 1 storage database (uk-db-01 to uk-db-04) to another which is active on a different mbx server. i now get the below error
Eventlog:
ComputerName=UK-EVAULT. User=Not specified Logfile=Symantec Enterprise Vault Type=Warning EventType=2 SourceName=Enterprise Vault Category=19 CategoryString=Archive Task EventCode=3357 EventID=-2147218147 TimeGenerated=20120208120004.000000-000 TimeWritten=20120208120004.000000-000 Message=This mailbox cannot be processed until the Exchange provisioning task has processed the corresponding user's details. Ensure that a provisioning group includes this user and run the provisioning task.
To disable these warnings, set the 'HideMissingPolicyInfoErrors' registry value to 1. See the documentation for further details.
Mailbox: /o=COMPANY/ou=LONDON/cn=RECIPIENTS/cn=USER
Message store: CN=UK-DB-01,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=accel,DC=com
For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp
how do i resolve this, should i disable the mailbox for archiving under mbx server 1 and then enable for mbx server 2 or is there a more elegant way.
best regards

Comments
is the EV system mailbox part
is the EV system mailbox part of a provisioning group? have you run the provisioning task like it says since failing over the database?
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
yes it is, i just manually
yes it is, i just manually ran the provisioning task and the mailbox now shows as enabled on the correct mbx server. the tasks runs every day at midnight so that is why i did not think about running it manually. will see if the error stops appearing at midnight
thanks!
i would enable the second
i would enable the second scheduled run of the provisioning task so that if anything like this happens again for some reason, you wont have to wait 24 hours.
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com
i moved the mailbox last week
i moved the mailbox last week so provisioning task had more than 5 days to pick up the changes.
no more errors at midnight,
no more errors at midnight, so manually running the provisioning task solved the issue.
Would you like to reply?
Login or Register to post your comment.