SharePoint 2010: User Profiles – You receive an error – "An unexpected error has occurred." when you try to browse to the page to Manage a newly created User Profile Service Application


You create a new User Profile Service Application and try browsing to the Manage link for the User Profile Service Application, this page might fail with the following error,

clip_image001

If you filter on the “User Profiles” category in the ULS Logs, you should see these errors:

UserProfileServiceUserStatisticsWebPart:LoadControl failed,
Exception: System.IO.FileLoadException: The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.InitializeIlmClient(String ILMMachineName, Int32 FIMWebClientTimeOut)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager..ctor(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)
at Microsoft.SharePoint.Portal.WebControls.UserProfileServiceStatisticsWebPartBase.LoadControl(Object sender, EventArgs e)       

UserProfileServiceAudienceStatisticsWebPart:LoadControl failed,
Exception: System.IO.FileLoadException: The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.InitializeIlmClient(String ILMMachineName, Int32 FIMWebClientTimeOut)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager..ctor(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)
at Microsoft.SharePoint.Portal.WebControls.UserProfileServiceStatisticsWebPartBase.LoadControl(Object sender, EventArgs e)

UserProfileServiceImportStatisticsWebPart:LoadControl failed,
Exception: System.IO.FileLoadException: The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.InitializeIlmClient(String ILMMachineName, Int32 FIMWebClientTimeOut)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager..ctor(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)
at Microsoft.SharePoint.Portal.WebControls.UserProfileServiceStatisticsWebPartBase.LoadControl(Object sender, EventArgs e)

This is an expected behaviour if the User Profile Synchronization Service is started on the SharePoint server hosting Central Administration. A recycle of IIS services is required to get this working. This is actually mentioned on the page that is displayed when starting the “User Profile Synchronization Services”.

image


Comments (10)

  1. MarcosPS says:

    Even though I did not head to the ULS logs, I had exactly the same problem with a recently created User Profile Service Application. Even deletng it and recreating it was not enough to overcome that.

    I noticed that the services

    User Profile Service

    User Profile Synchronization Service

    were stopped and started them both. The error message still continued to appear, and eventually, I got it resolved by restarting IIS.

    After IIS restart, the error message had vanished and the page opened as expected.

    Regards from Brazil!

  2. alexander says:

    Thank you very much! You saved my day :)

  3. Blake says:

    Thank you – I feel rather ridiculous now, having created and deleted services 4 times in a row

  4. Kalyan Guin says:

    I did the IISRESET, but still I am getting the same error.

  5. vijgang says:

    @Kalyan – If the call stack is exactly the same and the issue reproduces after creating the UPA, then an iisreset usually fixes it. I have not faced this same issue otherwise.

  6. Ken says:

    Perfect, thank you!

  7. david says:

    just like Kaylan getting this same error over and over….tried even reloading SQL and SPS 3 times.

    Any help would be great.

  8. Kim says:

    Awesome!  Saved me so much time!!! Thanks a million.

    Kim@sitedataview.com

  9. dinesh says:

    Thank you very much!  

  10. David says:

    It appears to also be a known issue with SharePoint 2010 Service Pack 1, getting this issue.

    A Hot-fix package can resolve this, if you are still getting same error after resetting IIS:

    support.microsoft.com/…/2596955