Application log at one of my Exchange servers is full of the following events: Event Type: ErrorEvent Source: MSExchangeISEvent Category: General Event ID: 9528Date: 03/12/2007Time: 15:23:16User: N/AComputer: EXCHNOD03Description:The SID S-1-5-32-544 was found on 7 users in the DS, so the store cannot map this SID to a unique user.The users involved are:/DC=com/DC=domain/DC=subdomain2/CN=Builtin/CN=Administrators/DC=com/DC=domainCN=Builtin/CN=Administrators/DC=com/DC=domain/DC=subdomain1/CN=Builtin/CN=Administrators/DC=com/DC=domain/DC=subdomain3/CN=Builtin/CN=Administrators/DC=com/DC=domain/DC=subdomain5/CN=Builtin/CN=Administrators/DC=com/DC=domain/DC=subdomain4/CN=Builtin/CN=Administrators/DC=com/DC=domain/DC=subdomain6/CN=Builtin/CN=Administrators Please use the Exchange Active Directory Cleanup utility to merge the duplicate objects together. ...this is a little bit confusing for me as it is obvious that builtin Administrators group has the same SID in every domain. Does anyone had similar problem and knows how to resolve it?

I am seeing the exact same thing but am not sure at this point what is going on or how to resolve it. It does seem to be related to Public Folder replication however (http://msexchangeteam.com/archive/2006/01/17/417611.aspx). Did you ever find a solution to the problem.

Here's a link to a tech center article that discusses this event id error: http://technet.microsoft.com/en-us/library/bb267016.aspx Let me know if this works for you.

Did you ever get a resolution to this as I have something very similar happening and would be interested in hearing how?

I did not find a solution but have not noticed any adverse effects either.

Hi Guys, Today I faced the same above problem but it was for two users. After that I checked both users MSexchangesid through adsiedit.msc and knew that both user MSexchangesid was the same. Then I checked the properties of both users and knew that one user was maked disabled on server but other one was active. In my case I have deleted the mailbox of disabled user. It will automatic remove the msexchangesid data from server because after removing the exchange attributes there will not exchange attributes will be available. In your case, i think there will be few user who will be active. Kindly try to re-create the mailbox of duplicate object. 1. extract the mails in .pst file using exmerge.exe. 2. delete the mailbox of user. 3. Create new mailbox on different store. 4. Merge the extracted .pst file in user mailbox using exmerge.exe. I hope it will help you and will solve your problem. Thanks

This could be coz of unresolved SID's in AD.Use OABInteg tool to get rid of them.Pretty handy tool : http://support.microsoft.com/default.aspx/kb/907792http://blogs.msdn.com/dgoldman/archive/2006/04/15/new-version-of-oabinteg-post-to-the-web.aspxRatish

Hi Guys,Today I faced the same above problem but it was for two users. After that I checked both users MSexchangesid through adsiedit.msc and knew that both user MSexchangesid was the same. Then I checked the properties of both users and knew that one user was maked disabled on server but other one was active. In my case I have deleted the mailbox of disabled user. It will automatic remove the msexchangesid data from server because after removing the exchange attributes there will not exchange attributes will be available.In your case, i think there will be few user who will be active. Kindly try to re-create the mailbox of duplicate object.1. extract the mails in .pst file using exmerge.exe.2. delete the mailbox of user.3. Create new mailbox on different store.4. Merge the extracted .pst file in user mailbox using exmerge.exe.I hope it will help you and will solve your problem.Thanks

Did you resolve that issue? We got the same error on one of our exchang servers.

We are experiencing the same issue... Since the "users" are actually Builtin Active Directory Groups... I'm kinda stuck here !!!I've searched the internet for a resolution to this issue for days... no luck so far ! Event Viewer Application logs is RED !!!Thanks for posting a solution for this. The SID S-1-5-32-544 was found on 2 users in the DS, so the store cannot map this SID to a unique user.The users involved are:/DC=ca/DC=********/CN=Builtin/CN=Administrators/DC=ca/DC=********/DC=****/CN=Builtin/CN=Administrators