none
Error at Creating a new Profile Sychronization connection

    Question

  • At creating a new profile synchronization connection I got an error "Unable to process Create message".

    In Log:

    Microsoft.ResourceManagement.WebServices.Faults.ServiceFaultException: Unable to process Create message     bei Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.CreateResource()     bei Microsoft.ResourceManagement.WebServices.ResourceManager.CreateResource()     bei Microsoft.Office.Server.UserProfiles.DirectoryServiceConnection.UpdateInternal() 990178d1-8697-477d-9cf3-4f56977c6c96
    SharePLeaving Monitored Scope (Request (POST:http://badwlrz-swmoss2:2010/_layouts/EditDSServer.aspx?ApplicationID=951cd8f4%2D3e56%2D4f5b%2Da5c1%2D81422e7fb8fe)). Ausführungszeit=2820,89790741561 990178d1-8697-477d-9cf3-4f56977c6c96
    SharePEntering monitored scope (Request (GET:http://badwlrz-swmoss2:2010/_layouts/error.aspx?ErrorText=Unable%20to%20process%20Create%20message&ErrorCorrelationId=990178d1%2D8697%2D477d%2D9cf3%2D4f56977c6c96)) 
    SharePName=Request (GET:http://badwlrz-swmoss2:2010/_layouts/error.aspx?ErrorText=Unable%20to%20process%20Create%20message&ErrorCorrelationId=990178d1%2D8697%2D477d%2D9cf3%2D4f56977c6c96) 9faad186-b74e-4654-9aff-b90adc3a3d0d
    SharePSite=/ 9faad186-b74e-4654-9aff-b90adc3a3d0d


    In Event:

    ForefrontIdentity Manager

    System.InvalidOperationException: Retrieve schema failed

    event-id: 3

    Microsoft.ResourceManagement.Service: System.InvalidOperationException: Retrieve schema failed
       bei Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.Create(String typeName, IList`1 createParameters, Guid creator, Guid cause)
       bei Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.ProcessInputRequest(RequestType request)
       bei Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.ProcessInputRequest(RequestType request)
       bei Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request)
       bei Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request)
       bei Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey)
       bei Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request)
       bei Microsoft.ResourceManagement.WebServices.ResourceManagementService.Create(Message request)

    Tuesday, August 03, 2010 3:22 PM

Answers

  • I'v solved this problem, which is actually our AD problem. We have a mix AD DS (2003 & 2008), which perhaps doen't support SP well. I'v tried with other AD DS 2008. It works. 

    • Marked as answer by hulu0808 Friday, August 06, 2010 2:44 PM
    Friday, August 06, 2010 2:43 PM

All replies

  • Seem to be the same error as described in this thread http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/17e5dc47-8b02-4078-b15e-a9f4a44f5776 . Does any of replies in that thread work for you?

    Thursday, August 05, 2010 8:07 AM
    Moderator
  • Unfortunately I have not found the solution from this thread. At us the account for sync is the member of Farm Admin and local Admin. And the profile sync service is also started. In Dialog of creating connection it can connect with AD. I can see the structur of AD and choose the container of it. But as I click the submit I take the error.
    Thursday, August 05, 2010 9:21 AM
  • Thanks for quick feedback! What about the Replicating Directory Changes permission? I don't know if it can be related to your error message. Just check major cause first.
    Thursday, August 05, 2010 10:14 AM
    Moderator
  • I'v solved this problem, which is actually our AD problem. We have a mix AD DS (2003 & 2008), which perhaps doen't support SP well. I'v tried with other AD DS 2008. It works. 

    • Marked as answer by hulu0808 Friday, August 06, 2010 2:44 PM
    Friday, August 06, 2010 2:43 PM
  • FYI, you need to use the NetBIOS name of your domain.  I was using the FQDN and changed to the NetBIOS and it worked.
    Friday, August 24, 2012 12:53 AM