troubleshooting Question

SP2010- Application Error MSG :: FIMSynchronizationService

Avatar of Cyber IT
Cyber ITFlag for United States of America asked on
Microsoft SharePointWindows Server 2008
7 Comments2 Solutions6881 ViewsLast Modified:
I keep getting the following TWO error messages in the Application Logs.  Can someone help me through this?  Thanks!

Log Name:      Application
Source:        FIMSynchronizationService
Date:          8/5/2011 4:00:03 PM
Event ID:      6208
Task Category: Database
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sharepoint.site.org
Description:
The server encryption keys could not be accessed.
 
 User Action
 Verify that the service account has permissions to the following registry key:
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service
 
 If the problem persists, run setup and restore the encryption keys from backup.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="FIMSynchronizationService" />
    <EventID Qualifiers="49152">6208</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-08-05T20:00:03.000000000Z" />
    <EventRecordID>335910</EventRecordID>
    <Channel>Application</Channel>
    <Computer>sharepoint.site.org</Computer>
    <Security />
  </System>
  <EventData>
    <Binary>0B000980</Binary>
  </EventData>
</Event>



Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          8/5/2011 4:01:33 PM
Event ID:      2137
Task Category: Health
Level:         Error
Keywords:      
User:          SDI\_ps20
Computer:      sharepoint.site.org
Description:
The SharePoint Health Analyzer detected an error.  One or more services have started or stopped unexpectedly.
The following services are managed by SharePoint, but their running state does not match what SharePoint expects: FIMSynchronizationService.  This can happen if a service crashes or if an administrator starts or stops a service using a non-SharePoint interface.  If SharePoint-managed services do not match their expected running state, SharePoint will be unable to correctly distribute work to the service.
SharePoint was unable to automatically repair this error.

To stop or start a service managed by SharePoint, use the SharePoint service management interface in the SharePoint Central Administration Site.  If a service has crashed, restart the service manually on the affected servers by running "net start [service name]" from a command prompt. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142683".

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
    <EventID>2137</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2011-08-05T20:01:33.803128900Z" />
    <EventRecordID>335911</EventRecordID>
    <Correlation ActivityID="{00E970CF-9B3B-4983-BE37-926CD7812DDE}" />
    <Execution ProcessID="3780" ThreadID="3860" />
    <Channel>Application</Channel>
    <Computer>sharepoint.site.org</Computer>
    <Security UserID="S-1-5-21-4002134116-3653569873-328754059-5405" />
  </System>
  <EventData>
    <Data Name="string0">One or more services have started or stopped unexpectedly.
The following services are managed by SharePoint, but their running state does not match what SharePoint expects: FIMSynchronizationService.  This can happen if a service crashes or if an administrator starts or stops a service using a non-SharePoint interface.  If SharePoint-managed services do not match their expected running state, SharePoint will be unable to correctly distribute work to the service.
SharePoint was unable to automatically repair this error.

To stop or start a service managed by SharePoint, use the SharePoint service management interface in the SharePoint Central Administration Site.  If a service has crashed, restart the service manually on the affected servers by running "net start [service name]" from a command prompt. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142683".
</Data>
  </EventData>
</Event>
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 2 Answers and 7 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros