locked
Problems with the FIM synchronization service RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    The user profile syncrhonization in sharepoint 2010 worked just fine for a few weeks. Suddenly the service wasn't available and after two days of troubleshooting, I decided to recreate and reconfigure the user profile service application. Everything worked just fine for a few hours and suddenly, again problems.The forefront idendity services has now the status disabled (Forefront Identity Manager service and forefront synchronization service) and I can't get them running.

    When I start the 'User Profile Synchronization Service' sharepoint service in the central administration I receive following error:

    The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server 'sqlserviceaccount'. The target name used was MSSQLSvc/sqlserverfqdn:1433. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (domain.com) is different from the client domain (domain.com), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

    When this error occurs in the eventviewer, the value of the SQLInstance registry key disapears (registry key located in HKL>SYSTEM>Currentcontrolset>services>fimsynchronizationservice>parameters)

    I'm out of ideas and some fresh ideas would be much appreciated.

    My setup is a one sharepoint 2010 server and one sql server 2008 R2. The sharepoint farm has a named instance on the sql server.

    thx

     

     

    Thursday, July 1, 2010 1:15 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Bils

    The issue you are encountering is a known issue that can occur when a SQL Named Instance is used.  It will be addressed in a future Cumulative Update.  For the meantime you can implement the workaround below to get the User Profile Synchronization Service started again.

     

    1. Open Registry Editor and navigate to the SQLInstance value located at HKLM\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters

    2. Open the SQLInstance value and type in your SQL Server name\Instance.  Do not hit OK yet.

    3. Open Central Admin and browse to Manage Services on Server. 

    4. Start User Profile Synchronization Service.

    5. Immediately after starting the User Profile Synchronization Service go back to the registry and click OK to add the SQLInstance value typed in step 2.

     

    *Please note: you may have to attempt the steps above more than once before the User Profile Synchronization Service will start successfully.

     

    Reagrds,

    Hiran
    Microsoft Online Community Support
    Tuesday, July 13, 2010 10:24 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Bils

    The issue you are encountering is a known issue that can occur when a SQL Named Instance is used.  It will be addressed in a future Cumulative Update.  For the meantime you can implement the workaround below to get the User Profile Synchronization Service started again.

     

    1. Open Registry Editor and navigate to the SQLInstance value located at HKLM\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters

    2. Open the SQLInstance value and type in your SQL Server name\Instance.  Do not hit OK yet.

    3. Open Central Admin and browse to Manage Services on Server. 

    4. Start User Profile Synchronization Service.

    5. Immediately after starting the User Profile Synchronization Service go back to the registry and click OK to add the SQLInstance value typed in step 2.

     

    *Please note: you may have to attempt the steps above more than once before the User Profile Synchronization Service will start successfully.

     

    Reagrds,

    Hiran
    Microsoft Online Community Support
    Tuesday, July 13, 2010 10:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Bils

    The issue you are encountering is a known issue that can occur when a SQL Named Instance is used.  It will be addressed in a future Cumulative Update.  For the meantime you can implement the workaround below to get the User Profile Synchronization Service started again.

     

    1. Open Registry Editor and navigate to the SQLInstance value located at HKLM\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters

    2. Open the SQLInstance value and type in your SQL Server name\Instance.  Do not hit OK yet.

    3. Open Central Admin and browse to Manage Services on Server. 

    4. Start User Profile Synchronization Service.

    5. Immediately after starting the User Profile Synchronization Service go back to the registry and click OK to add the SQLInstance value typed in step 2.

     

    *Please note: you may have to attempt the steps above more than once before the User Profile Synchronization Service will start successfully.

     

    Reagrds,

    Hiran
    Microsoft Online Community Support

    Any ideas as to when this is going to be fixed? as its affecting us too, and I have spent 1.5 days trying to figure out this problem so far until I read this thread

    Sam

    Tuesday, August 17, 2010 3:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    ok - think I have found the hotfix: http://support.microsoft.com/kb/983497/
    Tuesday, August 17, 2010 4:07 PM