Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Unable to update Mailbox SD in the DS. Mailbox Guid: bfde47cd-f7c3-4ec0-992c-0701669a4d86. Error Code 0x8004010f
|English: This information is only available to subscribers. An example of English, please!|
|Concepts to understand:|
What is a GUID?
What is the role of the Microsoft Exchange Information Store service?
What is the Mailbox SD?
From a newsgroup post: "This error implies that the account that you are using does not have permissions on the DC to change the user account information in the AD. In order to migrate mailboxes you should have mailbox permissions plus DS permissions to modify the user accounts in the AD. Verify the permissions of the Exchange and domain controller (DC) servers."
There could be several error codes registered with this event:
- Error code 0x8004010f
- Error code 0x80040102
Following the articles mentioned before may return 0 matches, in this case the user account doesn't exist in the domain for the mailbox GUID. In my case I'd deleted the user from the active directory which caused it to be marked for deletion in the Exchange server (a red cross appears next to accounts marked this way).
To clear the mailbox - From the System Manager, Admin groups/<site>/servers/<servername>/first storage group/mailboxes, you can either right-click the mailbox and purge to remove the mailbox immediately or run the cleanup agent, check the event log for results of the mailbox cleanup.
We had this event after renaming a user account and changing the password. After deleting the mailbox from the user and reconnected it, POP3 worked again and the event disappeared.
As per Microsoft: "This event indicates a problem with the directory permissions of a particular mailbox. The user could be having problems accessing their account". See MSEX2K3DB for additional information about this event.
Mohammed Athif Khaleel
This behavior may occur after you modify permissions on a mailbox. See ME322308 and ME555433 for information about this event.
Check Mailbox rights (Active directory Users & computers, Exchange Advanced, Mailbox rights). Check the user has rights to the mailbox.
This may happen for a mailbox that is not associated with a user or the user account is disabled. In my case I purged old mailboxes and the warning is gone.
|Private comment: Subscribers only. See example of private comment|
|Links: ME322308, ME555433, MSEX2K3DB, Error code 0x8004010f, Error code 0x80040102|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated