failed-creation-via-web-services  Schema validation failed
Here is my scenario: I am trying to import users from a test AD into the FIM 2010 User Portal (AD DS --> Metaverse --> FIM 2010 Portal). I have four VMs: 1 - DC 2- Exchange 2007 3 - FIM Service and Sync Service (SQL 2008 CU2 Installed) 4 - Portal and Password Reset Portal I am receiving the failed-creation-via-web-services error message when running the Export task on my FIM MA. The AD MA can import and sync successfully. I can vew the contents of the the AD MA Connector Space, the Metaverse, and the FIM MA connector space and see the user objects, all attributes look good. I setup an Inbound Sync Rule as described in this page: http://technet.microsoft.com/en-us/library/ee534915%28WS.10%29.aspx I am using the FIMMA account I setup for the Portal Install as the account used in the FIM MA The exact error from the FIM Event Log is: Microsoft.ResourceManagement.Service: System.Data.ConstraintException: Schema validation failed . 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) Any thoughts would be helpful.
February 2nd, 2010 10:13pm

I did run the powershell script(http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/3ec55d52-df26-4c09-9d92-24716636e460 ) to verify the FIM Agent Account and received the follwowing: Error: A parameter cannot be found that matches parameter name 'onlyBaseResource s'. The FIM MA account name and FIM MA account SID returned valid attribute data though.
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2010 10:28pm

One other thing to note - when I created the FIM MA and added the object type: Person, three mappings were already present in "Configure Attribute Flow" but not mentioned in any of the MS scenario documents. These are: Metaverse Attribute Data Source Attribute <blank> dn <object-id> MVObjectID csObjectID <dn> If I delete them they just come back when I open the agent properties again. Not sure if these are the cause of the Schema Validation Error, thought it was worth mentioning.
February 2nd, 2010 11:03pm

This means, you are not running the latest version of FIM.The parameter was introduced in Update 2 - you should install Update 3.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2010 10:26am

I will get Update 3, but I found that when I remove the EmployeeType attribute from the sync exporting works fine. There was another post indicating the same thing - is there a reason for that attribute causing an issue, or again is it just the Update version?
February 3rd, 2010 6:04pm

No, there is no known issue with EmployeeType.The problem is that most of us are running Updat2 or better - it will be challenging for you to find someone who can verify something for Update 1...Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2010 6:58pm

Can you give us examples what kind of values your employee types are? If I remember correctly, by default there is regular expression and it only takes values such as "Full Time Employee". You Should go to Administration - Scema and edit/delete the regular expression.
February 3rd, 2010 7:43pm

Can you give us examples what kind of values your employee types are? If I remember correctly, by default there is regular expression and it only takes values such as "Full Time Employee". You Should go to Administration - Scema and edit/delete the regular expression. That would make sense as for my lab I had entered the attribute value of "Staff", which would not match up to any expected regular expressions. Thanks for pointing this out. Rob
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2010 8:10pm

No, there is no known issue with EmployeeType.The problem is that most of us are running Updat2 or better - it will be challenging for you to find someone who can verify something for Update 1...Cheers,Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation Plus, in update 3 you should see which attribute is failing in the Identity Manager UI.
February 3rd, 2010 8:36pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics