I have been trying to sync our AD info with FIM and have found the following error when trying to carry out the FIMMA Export: Fault Reason: The request message contains errors that prevent processing the request. Fault Details: &lt;RepresentationFailures xmlns="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;&lt;AttributeRepresentationFailure&gt;&lt;AttributeType&gt;ObjectSID&lt;/AttributeType&gt;&lt;AttributeValue&gt;&lt;/AttributeValue&gt;&lt;FailureMessage&gt;The specified attribute value must be unique for this Resource Type.&lt;/FailureMessage&gt;&lt;AttributeFailureCode&gt;ValueViolatesUniqueness&lt;/AttributeFailureCode&gt;&lt;/AttributeRepresentationFailure&gt;&lt;/RepresentationFailures&gt; I have also checked the event viewer and have found the following error is logged at the same time of the import? - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft.ResourceManagement" /> <EventID Qualifiers="0">3</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-11-15T15:24:33.000000000Z" /> <EventRecordID>26</EventRecordID> <Channel>Forefront Identity Manager</Channel> <Computer>FIM2010.XXXXX.XXXX.XXX</Computer> <Security /> </System> - <EventData> <Data>Requestor: urn:uuid:fb89aefa-5ea1-47f1-8890-abe7797d6497 Microsoft.ResourceManagement: Microsoft.ResourceManagement.WebServices.Exceptions.InvalidRepresentationException: Exception of type 'Microsoft.ResourceManagement.WebServices.Exceptions.InvalidRepresentationException' was thrown. at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception) at Microsoft.ResourceManagement.Data.Exception.DataAccessExceptionManager.ThrowException(SqlException innerException) at Microsoft.ResourceManagement.Data.DataAccess.ProcessRequest(RequestType request) at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.ProcessInputRequest(RequestType request) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey, Boolean isRedispatch) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request) at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Create(Message request)</Data> </EventData> </Event> And: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft.ResourceManagement" /> <EventID Qualifiers="0">3</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-11-15T15:24:33.000000000Z" /> <EventRecordID>25</EventRecordID> <Channel>Forefront Identity Manager</Channel> <Computer>FIM2010.corporate.ggha.co.uk</Computer> <Security /> </System> - <EventData> <Data>Microsoft.ResourceManagement.WebServices.Exceptions.InvalidRepresentationException: Exception of type 'Microsoft.ResourceManagement.WebServices.Exceptions.InvalidRepresentationException' was thrown.</Data> </EventData> </Event> any ideas? ThanksJames Bulgo Snr ICT Officer Linc Cymru Housing Association

James- The answer is in that first paste. What's happening is that you are exporting the same user to FIM more than once or at least you already have a user in FIM with the same objectSid. Is it possible you manually created an administrator account and now you're trying to export the actual user from AD to FIM? See my boldfacing below. Fault Details: &lt;RepresentationFailures xmlns="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;&lt;AttributeRepresentationFailure&gt;&lt;AttributeType&gt;ObjectSID&lt;/AttributeType&gt;&lt;AttributeValue&gt;&lt;/AttributeValue&gt;&lt;FailureMessage&gt;The specified attribute value must be unique for this Resource Type.&lt;/FailureMessage&gt;&lt;AttributeFailureCode&gt;ValueViolatesUniqueness&lt;/AttributeFailureCode&gt;&lt;/AttributeRepresentationFailure&gt;&lt;/RepresentationFailures&gt;My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Hi Brian Thank you for your reply. I hadnt thought that i had created an admin account manually. However, the account failing to be exported is the domain admin account which was used to install FIM 2010. Im now suspecting that FIM 2010 creates an Admin account based on the current logged in user as this account is the only one that can access the portal! Would that be correct? Another issue is no other user can login to the portal. I can logon to the sharepoint site but not onto the identity manager portal itself. It just returns an unexpected error! any ideas of what i may have missed? James Bulgo Snr ICT Officer Linc Cymru Housing Association

Yes it created a user account for the user which you used to install the portal. What I would do is go in the Sync Engine and pull up the admin account in the MV search. Disconnect the user object that is trying to be provisioned to the FIM MA and then go in the joiner and manually link your existing FIM object to the MV object connected to your AD account.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

HI Brian Totally lost on this bit! Ive gone to the MV Search and found the person account in question - removed the user object (i think) but cannot work out how to link the existing FIM object to the AD account? Thanks in advanceJames Bulgo Snr ICT Officer Linc Cymru Housing Association

Hi Brian Thanks for your answer it pointed me in the right direction! In the end i removed the MA's and connector spaces and recreated after moving the admin account from the OU and reimported from the AD with no issues! on the other issue about user's not being able to access the portal! this was solved by adding accountName to the attribute flow for the FIMMA agent! (Its missing from the documentation on how to sync users from active directory domain services) Thanks for all your help and assistanceJames Bulgo Snr ICT Officer Linc Cymru Housing Association