Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > SharePoint 2010 Forums > SharePoint 2010 - Setup, Upgrade, Administration and Operation > FIMSynchronizationService and Sharepoint 2010 August Update

Answered FIMSynchronizationService and Sharepoint 2010 August Update

    •  
      Tuesday, October 19, 2010 6:50 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi to everyone. I have a question i hope someone here can help.

      I recentlly install the update from August 2010 for SharePoint 2010 and the User Profile stop working.

      I did some research but i couldn't find a solution.

      I notice in my Sharepoint console a pop-up message like this:

      "System.ServiceModel.EndPointNotFoundException in OWSTimer.exe 7756"

      and did a debug to this error and found the following exception

      {"Could not connect to http://vlaba-sh00:5725/ResourceManagementService/MEX. TCP error code 10061:
       No connection could be made because the target machine actively refused it 192.168.0.205:5725. "}

      looking at the service i found that the Forefront Identity Manager Synchronization (miiserver.exe) couldnt be started.

      every time i started its stop with the following message:

      The service: Forefront Identity Manager Synchronization (miiserver.exe)

      - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      - <System>
        <Provider Name="FIMSynchronizationService" />
        <EventID Qualifiers="49152">6211</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-10-19T18:37:32.000000000Z" />
        <EventRecordID>385757</EventRecordID>
        <Channel>Application</Channel>
        <Computer>vlaba-sh00.latam.com</Computer>
        <Security />
        </System>
        <EventData />
        </Event>


      The service was unable to start because the version of the database does not match the version of the product.
      Event 6211

      also had this event:

      - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      - <System>
        <Provider Name="Forefront Identity Manager" />
        <EventID Qualifiers="0">3</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-10-19T18:37:56.000000000Z" />
        <EventRecordID>385758</EventRecordID>
        <Channel>Application</Channel>
        <Computer>vlaba-sh00.latam.com</Computer>
        <Security />
        </System>
      - <EventData>
        <Data>Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManagerException: Forefront Identity Management Service does not support workflows of type 'Microsoft.ResourceManagement.Workflow.Activities.SequentialWorkflow, Microsoft.ResourceManagement, Version=4.0.2450.5, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.</Data>
        </EventData>
        </Event>

      both version for miiserver.exe and Microsoft.ResourceManagement.Service.dll are 4.0.2450.11.

      I think the update fix didnt update the values of SyncDB database for the Identity Manager.

      Well, i don't know how to fix this problem. If someone can help me i will appreciate it.

      A big hug for all of you and thanxs for advance.

       

       

    Answers

    • Wednesday, November 10, 2010 4:13 PM
       
       Answered
      Sign In to Vote
      4
      Sign In to Vote

      I've hit the same issue before. I was able to resolve it in my environment by stopping and restarting the User Profile Synchronization Service in the farm.

      Steps:

      1. Central Admin>System Settings>Manage Services on Server (select the server where the User Profile Service is running)
      2. Stop the User Profile Service
      3. Stop the User Profile Synchronization Service (you will be prompted that this will deprovision the service)
      4. Once the services have stopped, Start the User Profile Service again
      5. Start the User Profile Synchronization Service again (you will be prompted to enter the password for the User Profile Service's svc account) -note1: this service can take a little while to restart; note2: if it does not restart successfully, restart the server and try again (this has worked for me)
      6. Once complete, the User Profile Service and User Profile Synchronization service should show as Started, and the 2 corresponding FIM services on the server should be running again

      From that point on, my errors went away.

       
    • Tuesday, April 12, 2011 9:32 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      I can confirm that this solution works, however my situation was a little different:

      RTM was installed, Sharepoint configured and sites form MOSS 2007 copied to it.
      Then cumulative update February 2011, build 5126, was applied to Sharepoint 2010.

      After that the Profile Service was running, but the Profile Synchronization Service was disabled.
      If I enabled the service and tried to start it, it failed with "The service was unable to start because the version of the database does not match the version of the product".

      I followed the above, except step 3 because this service was disabled and not running.
      After step 5 both services were running according to Windows Services, but Central Administration showed the Profile Synchronization Service as "Starting". Access to User Profile Service Application in Central Administration failed.

      But after a reboot of the server, profile import works again.

       

    All Replies

    • Wednesday, November 10, 2010 4:13 PM
       
       Answered
      Sign In to Vote
      4
      Sign In to Vote

      I've hit the same issue before. I was able to resolve it in my environment by stopping and restarting the User Profile Synchronization Service in the farm.

      Steps:

      1. Central Admin>System Settings>Manage Services on Server (select the server where the User Profile Service is running)
      2. Stop the User Profile Service
      3. Stop the User Profile Synchronization Service (you will be prompted that this will deprovision the service)
      4. Once the services have stopped, Start the User Profile Service again
      5. Start the User Profile Synchronization Service again (you will be prompted to enter the password for the User Profile Service's svc account) -note1: this service can take a little while to restart; note2: if it does not restart successfully, restart the server and try again (this has worked for me)
      6. Once complete, the User Profile Service and User Profile Synchronization service should show as Started, and the 2 corresponding FIM services on the server should be running again

      From that point on, my errors went away.

       
    • Tuesday, April 12, 2011 9:32 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      I can confirm that this solution works, however my situation was a little different:

      RTM was installed, Sharepoint configured and sites form MOSS 2007 copied to it.
      Then cumulative update February 2011, build 5126, was applied to Sharepoint 2010.

      After that the Profile Service was running, but the Profile Synchronization Service was disabled.
      If I enabled the service and tried to start it, it failed with "The service was unable to start because the version of the database does not match the version of the product".

      I followed the above, except step 3 because this service was disabled and not running.
      After step 5 both services were running according to Windows Services, but Central Administration showed the Profile Synchronization Service as "Starting". Access to User Profile Service Application in Central Administration failed.

      But after a reboot of the server, profile import works again.

       
    • Tuesday, April 19, 2011 7:53 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Thank you, I've hit the same error after march 2011 CU update for Sharepoint 2010 and got it fixed.
       
    • Friday, May 06, 2011 3:43 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Same here. After March 2011 CU I had the same issue.  Fixed by above answer and Peters slight modifications. 

       

       
    • Sunday, July 31, 2011 12:17 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      this worked for me, thanks!
       
    • Sunday, July 31, 2011 3:54 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      It's a good practice to always export MIIS encryption key which is located in <root directory drive>\Program Files\Microsoft Office Servers\14.0\Synchronization Service\Bin before adding any CU or hotfix. To export the key you need to type this:

      miiskmu.exe /e <Path>

      Where <Path> is the path and file name for the exported key

      Then you can import the key again after applying the CU. This need to be done before backing up User Profile Service service application databases also. The key should be imported before restore.

      Note: If you do not export and then import the key correctly, the Synchronization Service will not start

       

      Regards

      Henrik A. Halmstrand
      http:/www.sharepointrevealed.com
      http://getspconfig.codeplex.com