locked
User Profile Synchronization Service stuck on starting RRS feed

  • Question

  • I found Ali Mazaheri's blog post on configuring User Profile Service Application and am stuck on step 4 because the Forefront Identity Management Synchronisation and Forefront Identity Manager Service are not started. The later is set to disabled. When I try and set them both to automatic and start them I get these errors in the event log.
    Haven't got a clue...this is a SharePoint 2010 Enterprise Server Beta 2 build with SQL 2008 SP1 + CU3 and AD Domain Controller on a single virtual machine.
    I've also checked out the MSDN article but no mention of issues here.

    Log Name:      Application
    
    Source:        Microsoft Resource Management Service
    
    Date:          18/11/2009 6:54:10 PM
    
    Event ID:      0
    
    Task Category: None
    
    Level:         Error
    
    Keywords:      Classic
    
    User:          N/A
    
    Computer:      SPS2010.sps.spdevwiki.com
    
    Description:
    
    Service cannot be started. System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection' threw an exception. ---> System.Configuration.ConfigurationErrorsException: Required attribute 'externalHostName' not found. (C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe.Config line 29)
    
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
    
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeO...
    
    Event Xml:
    
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    
      <System>
    
        <Provider Name="Microsoft Resource Management Service" />
    
        <EventID Qualifiers="0">0</EventID>
    
        <Level>2</Level>
    
        <Task>0</Task>
    
        <Keywords>0x80000000000000</Keywords>
    
        <TimeCreated SystemTime="2009-11-18T10:54:10.000000000Z" />
    
        <EventRecordID>4708</EventRecordID>
    
        <Channel>Application</Channel>
    
        <Computer>SPS2010.sps.spdevwiki.com</Computer>
    
        <Security />
    
      </System>
    
      <EventData>
    
        <Data>Service cannot be started. System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory' threw an exception. ---&gt; System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---&gt; System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection' threw an exception. ---&gt; System.Configuration.ConfigurationErrorsException: Required attribute 'externalHostName' not found. (C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe.Config line 29)
    
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
    
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeO...</Data>
    
      </EventData>
    
    </Event>
    
    
    
    Log Name:      Application
    
    Source:        Forefront Identity Manager
    
    Date:          18/11/2009 6:54:10 PM
    
    Event ID:      3
    
    Task Category: None
    
    Level:         Error
    
    Keywords:      Classic
    
    User:          N/A
    
    Computer:      SPS2010.sps.spdevwiki.com
    
    Description:
    
    Microsoft.ResourceManagement.Service: System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection' threw an exception. ---> System.Configuration.ConfigurationErrorsException: Required attribute 'externalHostName' not found. (C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe.Config line 29)
    
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
    
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
    
       at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
    
       at System.Configuration.ConfigurationManager.GetSection(String sectionName)
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection..cctor()
    
       --- End of inner exception stack trace ---
    
       at Microsoft.ResourceManagement.Policy.PolicyApplicationManager..ctor()
    
       --- End of inner exception stack trace ---
    
       at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
    
       at System.Activator.CreateInstance[T]()
    
       at Microsoft.ResourceManagement.Utilities.SingletonObjectBase`1.get_Instance()
    
       at Microsoft.ResourceManagement.Utilities.DefaultSingletonObjectClassFactory`2.CreateInstance()
    
       at Microsoft.ResourceManagement.Utilities.ClassFactoryManager.CreateInstance[T]()
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory..cctor()
    
       --- End of inner exception stack trace ---
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory..ctor()
    
       at Microsoft.ResourceManagement.WindowsHostService.OnStart(String[] args)
    
    Event Xml:
    
    <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="2009-11-18T10:54:10.000000000Z" />
    
        <EventRecordID>4707</EventRecordID>
    
        <Channel>Application</Channel>
    
        <Computer>SPS2010.sps.spdevwiki.com</Computer>
    
        <Security />
    
      </System>
    
      <EventData>
    
        <Data>Microsoft.ResourceManagement.Service: System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory' threw an exception. ---&gt; System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---&gt; System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection' threw an exception. ---&gt; System.Configuration.ConfigurationErrorsException: Required attribute 'externalHostName' not found. (C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe.Config line 29)
    
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
    
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
    
       at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
    
       at System.Configuration.ConfigurationManager.GetSection(String sectionName)
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection..cctor()
    
       --- End of inner exception stack trace ---
    
       at Microsoft.ResourceManagement.Policy.PolicyApplicationManager..ctor()
    
       --- End of inner exception stack trace ---
    
       at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean&amp; canBeCached, RuntimeMethodHandle&amp; ctor, Boolean&amp; bNeedSecurityCheck)
    
       at System.Activator.CreateInstance[T]()
    
       at Microsoft.ResourceManagement.Utilities.SingletonObjectBase`1.get_Instance()
    
       at Microsoft.ResourceManagement.Utilities.DefaultSingletonObjectClassFactory`2.CreateInstance()
    
       at Microsoft.ResourceManagement.Utilities.ClassFactoryManager.CreateInstance[T]()
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory..cctor()
    
       --- End of inner exception stack trace ---
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceHostFactory..ctor()
    
       at Microsoft.ResourceManagement.WindowsHostService.OnStart(String[] args)</Data>
    
      </EventData>
    
    </Event>
    
    
    
    Log Name:      Application
    
    Source:        Microsoft.ResourceManagement.ServiceHealthSource
    
    Date:          18/11/2009 6:54:10 PM
    
    Event ID:      2
    
    Task Category: None
    
    Level:         Error
    
    Keywords:      Classic
    
    User:          N/A
    
    Computer:      SPS2010.sps.spdevwiki.com
    
    Description:
    
    The Forefront Identity Manager Service could not bind to its endpoints.  This failure prevents clients from communicating with the Web services.
    
    
    
    A most likely cause for the failure is another service, possibly another instance of Forefront Identity Manager Service, has already bound to the endpoint.  Another, less likely cause, is that the account under which the service runs does not have permission to bind to endpoints.
    
    
    
    Ensure that no other processes have bound to that endpoint and that the service account has permission to bind endpoints.  Further, check the application configuration file to ensure the Forefront Identity Manager Service is binding to the correct endpoints.
    
    Event Xml:
    
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    
      <System>
    
        <Provider Name="Microsoft.ResourceManagement.ServiceHealthSource" />
    
        <EventID Qualifiers="0">2</EventID>
    
        <Level>2</Level>
    
        <Task>0</Task>
    
        <Keywords>0x80000000000000</Keywords>
    
        <TimeCreated SystemTime="2009-11-18T10:54:10.000000000Z" />
    
        <EventRecordID>4706</EventRecordID>
    
        <Channel>Application</Channel>
    
        <Computer>SPS2010.sps.spdevwiki.com</Computer>
    
        <Security />
    
      </System>
    
      <EventData>
    
        <Data>The Forefront Identity Manager Service could not bind to its endpoints.  This failure prevents clients from communicating with the Web services.
    
    
    
    A most likely cause for the failure is another service, possibly another instance of Forefront Identity Manager Service, has already bound to the endpoint.  Another, less likely cause, is that the account under which the service runs does not have permission to bind to endpoints.
    
    
    
    Ensure that no other processes have bound to that endpoint and that the service account has permission to bind endpoints.  Further, check the application configuration file to ensure the Forefront Identity Manager Service is binding to the correct endpoints.</Data>
    
      </EventData>
    
    </Event>
    
    
    
    Log Name:      Application
    
    Source:        Forefront Identity Manager
    
    Date:          18/11/2009 6:54:09 PM
    
    Event ID:      3
    
    Task Category: None
    
    Level:         Error
    
    Keywords:      Classic
    
    User:          N/A
    
    Computer:      SPS2010.sps.spdevwiki.com
    
    Description:
    
    System.Configuration: System.Configuration.ConfigurationErrorsException: Required attribute 'externalHostName' not found. (C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe.Config line 29)
    
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
    
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
    
       at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
    
       at System.Configuration.ConfigurationManager.GetSection(String sectionName)
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection..cctor()
    
    Event Xml:
    
    <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="2009-11-18T10:54:09.000000000Z" />
    
        <EventRecordID>4705</EventRecordID>
    
        <Channel>Application</Channel>
    
        <Computer>SPS2010.sps.spdevwiki.com</Computer>
    
        <Security />
    
      </System>
    
      <EventData>
    
        <Data>System.Configuration: System.Configuration.ConfigurationErrorsException: Required attribute 'externalHostName' not found. (C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe.Config line 29)
    
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
    
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
    
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
    
       at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
    
       at System.Configuration.ConfigurationManager.GetSection(String sectionName)
    
       at Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection..cctor()</Data>
    
      </EventData>
    
    </Event>
    
    

    SharePoint Solution Architect, Perth Australia - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - Readify - http://wss.made4the.net/- http://www.sharepointdevwiki.com/
    • Edited by Jeremy Thake Wednesday, November 18, 2009 11:11 AM added links and more info on environment
    • Moved by Serge Luca [MVP]MVP Tuesday, August 17, 2010 6:47 PM (From:SharePoint 2010 - General Questions and Answers)
    Wednesday, November 18, 2009 11:05 AM

Answers

All replies

  • I had an exact problem...
    What account does your User Profile Service Application run under?  Try putting this account in the Administrator group. 

    I was able to get the ForeFront and everything woking this morning, and I had the service account in the Administrators group.  But then I got a message by the SharePoint Analyser complaining that having a service account in the administrator group may pose a security risk.  Then I moved the service account from Administrators to Power Users.  Since then I couldn't get the "User Profile Synchronization Service" working. 

    After different configuration for 2 hours, I put the account back to Administrator group, reboot and bang, the service is started............

    Not 100% sure that this is the correct way of doing this, but it works for me.

    Let me know if this works for you.

    Wilson | SharePoint Egg's Blog
    Wednesday, November 18, 2009 2:57 PM
  • Is the server R2?  Until the WCF hotfix is available, you should use Windows Server 2008.

    Wednesday, November 18, 2009 6:24 PM
  • The errors above are from R2 yes.

    But no I get these errors after building a Windows Server 2008 one too.

    When I try and start the Forefront Identity Synchronization Manager Windows Service (running as a Active Directory domain account - the SharePoint farm account, which I set as domain admin just to see if that fixed it) in the event viewer I get the error below.

    Just a little more background the other Forefront Identity Windows service is set to disabled and 'log on' is as Local System. These are the defaults that were setup. Neither will start even if I switch them to automatic and try and start.


    Log Name:      Application
    Source:        FIMSynchronizationService
    Date:          19/11/2009 10:40:29 AM
    Event ID:      6324
    Task Category: (3)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    The description for Event ID 6324 from source FIMSynchronizationService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 0.
    ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 1.
    ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 2.
    ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 3.
    BAIL: MMS(2564): service.cpp(991): 0x80040e37
    Forefront Identity Manager 4.0.2450.5

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="FIMSynchronizationService" />
        <EventID Qualifiers="49152">6324</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T02:40:29.000000000Z" />
        <EventRecordID>3122</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 0.
    ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 1.
    ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 2.
    ERR: MMS(2564): sql.cpp(5580): Query (select count(*) from [mms_management_agent]) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_management_agent'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(4114): 0x80040e37
    ERR: MMS(2564): sql.cpp(5580): Query (select fixed_schema_version_number from [mms_server_configuration] ) performed with error
    ERR: MMS(2564): sql.cpp(5633): Invalid object name 'mms_server_configuration'.
    ERR: MMS(2564): sql.cpp(5641): hrError: 0x80040e37, dwMinor: 208
    ERR: MMS(2564): sql.cpp(5796): SQL error: 42S02, native: 208
    BAIL: MMS(2564): sql.cpp(2897): 0x80040e37
    BAIL: MMS(2564): sql.cpp(2738): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(2485): 0x80040e37
    BAIL: MMS(2564): storeimp.cpp(293): 0x80040e37
    ERR: MMS(2564): server.cpp(294): Failed to connect to the database  on SPS
    BAIL: MMS(2564): server.cpp(295): 0x80040e37
    BAIL: MMS(2564): server.cpp(3518): 0x80040e37
    BAIL: MMS(2564): service.cpp(1528): 0x80040e37
    ERR: MMS(2564): service.cpp(977): Error creating com objects. Error code: -2147217865. This is retry number 3.
    BAIL: MMS(2564): service.cpp(991): 0x80040e37
    Forefront Identity Manager 4.0.2450.5</Data>
      </EventData>
    </Event>


    SharePoint Solution Architect, Perth Australia - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - Readify - http://wss.made4the.net/- http://www.sharepointdevwiki.com/
    Thursday, November 19, 2009 2:58 AM
  • I tried adding to the admin group with no luck. THe Forefront Identity Synchronisation Manager Windows Service just won't start.
    SharePoint Solution Architect, Perth Australia - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - Readify - http://wss.made4the.net/- http://www.sharepointdevwiki.com/
    Thursday, November 19, 2009 2:59 AM
  • Ok, so as we were discussing on Twitter :-)... If you've previously tried to synch using a non-farm admin account (this is what had happened in my case) your User Profile Synchronization Service in the Services on Server section of CA might be stuck in the status of 'starting'. A reboot or IISRESET won't kill it. Instead, you'll need to use PowerShell to kill it by using the cmdlet 'stop-spserviceinstance. <svcname>'. Then, make sure you're logged in as the farm admin account and go back and try again. You need to check permissions on the Forefront management services too. If you've patched your server (have you also rebooted it) and you're still seeing issues with the FF svcs not starting then it sounds like a permissions problem.
    Thursday, November 19, 2009 3:38 AM
  • The SharePoint Blog team has posted a article on how to do this. The only step I think i'm missing is being logged in as the Farm account on the box when I start the service, as I'm in as the setup account. Will try later and post results here.

    Thanks Kathy for your help too. Busy at work so can't test right now ;-)
    SharePoint Solution Architect, Perth Australia - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - Readify - http://wss.made4the.net/- http://www.sharepointdevwiki.com/
    • Proposed as answer by PetkaRUS Friday, July 9, 2010 8:21 PM
    Thursday, November 19, 2009 5:16 AM
  • Kathy, that would be awesome, IF stop-spserviceinstance took a "string"  it takes GUID my dear....

    CJG
    Thursday, November 19, 2009 5:40 AM
  • OK, so I didn't have to stop it using PowerShell. I shut down and restarted...the only change I had made was giving the service account domain admin rights (why the ____ not I say!). SO you are right, that must have been a security thing.

    On restart the User Profile Service Application has started for both, and looking at the Windows Services they are both started too.

    Now if I go into the User Profile Service Application configuration page and click on Configure Synchronization Connections I get an error on that page.

    "An error occurred while accessing the SQL Server database or the SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administor."

    Don't you just LOVE those errors...go "contact yourself"!

    Looking in the Event Viewer there was an error:

    "The Forefront Identity Manager Service cannot connect to the SQL Database Server."

    Anyways, reading the requirements for Forefront Identity  Manager Service on their site, it looks like this service account requires admin rights to SQL. I added my service account as 'sysadmin' role.

    I then stopped and started the "User Profile Service" and "User Profile Synchronization Service" service applications using the SharePoint 2010 Central Administration | System Settings | Manage services on server. The sync service took a while to come off of "starting" and went to "started" BUT...in the event log I get this below:




    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:18:41 PM
    Event ID:      1015
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Failed to connect to server. Error: 0x80070005
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1015</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:41.000Z" />
        <EventRecordID>3337</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>0x80070005</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:18:41 PM
    Event ID:      1001
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM' failed during request for component '{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}'
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:41.000Z" />
        <EventRecordID>3336</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:18:41 PM
    Event ID:      1004
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1004</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:41.000Z" />
        <EventRecordID>3335</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}</Data>
        <Data>C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:18:41 PM
    Event ID:      1015
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Failed to connect to server. Error: 0x80070005
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1015</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:41.000Z" />
        <EventRecordID>3334</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>0x80070005</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:18:41 PM
    Event ID:      1001
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM' failed during request for component '{9AE4D8E0-D3F6-47A8-8FAE-38496FE32FF5}'
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:41.000Z" />
        <EventRecordID>3333</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{9AE4D8E0-D3F6-47A8-8FAE-38496FE32FF5}</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:18:41 PM
    Event ID:      1004
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1004</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:41.000Z" />
        <EventRecordID>3332</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}</Data>
        <Data>C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft Resource Management Service
    Date:          19/11/2009 7:18:36 PM
    Event ID:      0
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Service started successfully.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft Resource Management Service" />
        <EventID Qualifiers="0">0</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:36.000Z" />
        <EventRecordID>3331</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Service started successfully.</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft.ResourceManagement.ServiceHealthSource
    Date:          19/11/2009 7:18:36 PM
    Event ID:      22
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    The Forefront Identity Manager Service cannot connect to the SQL Database Server.

    The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.

    Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft.ResourceManagement.ServiceHealthSource" />
        <EventID Qualifiers="0">22</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:18:36.000Z" />
        <EventRecordID>3330</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The Forefront Identity Manager Service cannot connect to the SQL Database Server.

    The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.

    Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.</Data>
      </EventData>
    </Event>


    SharePoint Solution Architect, Perth Australia - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - Readify - http://wss.made4the.net/- http://www.sharepointdevwiki.com/
    Thursday, November 19, 2009 11:22 AM
  • After reading the post instructions, one thing I hadn't tried was logging in as the farm account (rather than the setup account) and stopping and starting the service...I now get another set of errors which main one seems to be:

    "The Forefront Identity Manager Service cannot connect to the SQL Database Server. "

    Below is full event log dump:

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          19/11/2009 7:30:20 PM
    Event ID:      8306
    Task Category: Claims Authentication
    Level:         Error
    Keywords:     
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    An exception occurred when trying to issue security token: The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. .
    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>8306</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>47</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:30:20.487Z" />
        <EventRecordID>3378</EventRecordID>
        <Correlation />
        <Execution ProcessID="2696" ThreadID="3828" />
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
        <Data Name="string0">The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          19/11/2009 7:30:20 PM
    Event ID:      8306
    Task Category: Claims Authentication
    Level:         Error
    Keywords:     
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    An exception occurred when trying to issue security token: The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. .
    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>8306</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>47</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:30:20.460Z" />
        <EventRecordID>3377</EventRecordID>
        <Correlation />
        <Execution ProcessID="2696" ThreadID="3828" />
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
        <Data Name="string0">The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          19/11/2009 7:30:20 PM
    Event ID:      8306
    Task Category: Claims Authentication
    Level:         Error
    Keywords:     
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    An exception occurred when trying to issue security token: The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. .
    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>8306</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>47</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:30:20.443Z" />
        <EventRecordID>3376</EventRecordID>
        <Correlation />
        <Execution ProcessID="2696" ThreadID="3828" />
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
        <Data Name="string0">The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          19/11/2009 7:30:20 PM
    Event ID:      8306
    Task Category: Claims Authentication
    Level:         Error
    Keywords:     
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    An exception occurred when trying to issue security token: The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. .
    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>8306</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>47</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:30:20.399Z" />
        <EventRecordID>3375</EventRecordID>
        <Correlation />
        <Execution ProcessID="2696" ThreadID="3828" />
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
        <Data Name="string0">The HTTP service located at https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc is too busy. </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          19/11/2009 7:30:20 PM
    Event ID:      8306
    Task Category: Claims Authentication
    Level:         Error
    Keywords:     
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    An exception occurred when trying to issue security token: An error occurred while receiving the HTTP response to https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details..
    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>8306</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>47</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:30:20.194Z" />
        <EventRecordID>3374</EventRecordID>
        <Correlation ActivityID="{7585A6D9-C645-417B-BEA8-D4F9A55B82E2}" />
        <Execution ProcessID="2696" ThreadID="4120" />
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
        <Data Name="string0">An error occurred while receiving the HTTP response to https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:29:23 PM
    Event ID:      1015
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Failed to connect to server. Error: 0x80070005
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1015</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:23.000Z" />
        <EventRecordID>3373</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>0x80070005</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:29:23 PM
    Event ID:      1001
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM' failed during request for component '{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}'
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:23.000Z" />
        <EventRecordID>3372</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:29:23 PM
    Event ID:      1004
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1004</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:23.000Z" />
        <EventRecordID>3371</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}</Data>
        <Data>C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:29:23 PM
    Event ID:      1015
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Failed to connect to server. Error: 0x80070005
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1015</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:23.000Z" />
        <EventRecordID>3370</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>0x80070005</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:29:23 PM
    Event ID:      1001
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM' failed during request for component '{9AE4D8E0-D3F6-47A8-8FAE-38496FE32FF5}'
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:23.000Z" />
        <EventRecordID>3369</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{9AE4D8E0-D3F6-47A8-8FAE-38496FE32FF5}</Data>
        <Data>(NULL)</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MsiInstaller
    Date:          19/11/2009 7:29:23 PM
    Event ID:      1004
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          NETWORK SERVICE
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Detection of product '{20140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1004</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:23.000Z" />
        <EventRecordID>3368</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>{20140000-104C-0000-1000-0000000FF1CE}</Data>
        <Data>PeopleILM</Data>
        <Data>{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}</Data>
        <Data>C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe</Data>
        <Data>(NULL)</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft Resource Management Service
    Date:          19/11/2009 7:29:18 PM
    Event ID:      0
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Service started successfully.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft Resource Management Service" />
        <EventID Qualifiers="0">0</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:18.000Z" />
        <EventRecordID>3367</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Service started successfully.</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft.ResourceManagement.ServiceHealthSource
    Date:          19/11/2009 7:29:17 PM
    Event ID:      22
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    The Forefront Identity Manager Service cannot connect to the SQL Database Server.

    The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.

    Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft.ResourceManagement.ServiceHealthSource" />
        <EventID Qualifiers="0">22</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:17.000Z" />
        <EventRecordID>3366</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The Forefront Identity Manager Service cannot connect to the SQL Database Server.

    The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.

    Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        FIMSynchronizationService
    Date:          19/11/2009 7:29:03 PM
    Event ID:      2001
    Task Category: (6)
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    The service was started successfully.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="FIMSynchronizationService" />
        <EventID Qualifiers="16384">2001</EventID>
        <Level>4</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:03.000Z" />
        <EventRecordID>3365</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          19/11/2009 7:29:02 PM
    Event ID:      5084
    Task Category: Server
    Level:         Information
    Keywords:      Classic
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Setting database option PARAMETERIZATION to FORCED for database User Profile Service Application_SyncDB_8b155eb9fa1e4b6d8697576fa4c74994.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSSQLSERVER" />
        <EventID Qualifiers="16384">5084</EventID>
        <Level>4</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:02.000Z" />
        <EventRecordID>3364</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
        <Data>PARAMETERIZATION</Data>
        <Data>FORCED</Data>
        <Data>User Profile Service Application_SyncDB_8b155eb9fa1e4b6d8697576fa4c74994</Data>
        <Binary>DC1300000A0000000400000053005000530000004900000055007300650072002000500072006F00660069006C0065002000530065007200760069006300650020004100700070006C00690063006100740069006F006E005F00530079006E006300440042005F00380062003100350035006500620039006600610031006500340062003600640038003600390037003500370036006600610034006300370034003900390034000000</Binary>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          19/11/2009 7:29:02 PM
    Event ID:      5084
    Task Category: Server
    Level:         Information
    Keywords:      Classic
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Setting database option COMPATIBILITY_LEVEL to 90 for database User Profile Service Application_SyncDB_8b155eb9fa1e4b6d8697576fa4c74994.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSSQLSERVER" />
        <EventID Qualifiers="16384">5084</EventID>
        <Level>4</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:02.000Z" />
        <EventRecordID>3363</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
        <Data>COMPATIBILITY_LEVEL</Data>
        <Data>90</Data>
        <Data>User Profile Service Application_SyncDB_8b155eb9fa1e4b6d8697576fa4c74994</Data>
        <Binary>DC1300000A0000000400000053005000530000004900000055007300650072002000500072006F00660069006C0065002000530065007200760069006300650020004100700070006C00690063006100740069006F006E005F00530079006E006300440042005F00380062003100350035006500620039006600610031006500340062003600640038003600390037003500370036006600610034006300370034003900390034000000</Binary>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-Windows-LoadPerf
    Date:          19/11/2009 7:29:01 PM
    Event ID:      1002
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Performance counters for the FIMSynchronizationService (Forefront Identity Manager Synchronization Service) service are already in the registry, no need to reinstall. This only happens when you install the same counter twice. The second time install will generate this event.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-LoadPerf" Guid="{122EE297-BB47-41AE-B265-1CA8D1886D40}" EventSourceName="LoadPerf" />
        <EventID Qualifiers="16384">1002</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:29:01.000Z" />
        <EventRecordID>3362</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <UserData>
        <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="LoadPerf">
          <param1>FIMSynchronizationService</param1>
          <param2>Forefront Identity Manager Synchronization Service</param2>
          <binaryDataSize>4</binaryDataSize>
          <binaryData>E9120000</binaryData>
        </EventXML>
      </UserData>
    </Event>

    Log Name:      Application
    Source:        Microsoft Resource Management Service
    Date:          19/11/2009 7:28:31 PM
    Event ID:      0
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Service stopped successfully.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft Resource Management Service" />
        <EventID Qualifiers="0">0</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:28:31.000Z" />
        <EventRecordID>3361</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Service stopped successfully.</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        FIMSynchronizationService
    Date:          19/11/2009 7:28:30 PM
    Event ID:      2002
    Task Category: (6)
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SPS.sp.spdevwiki.com
    Description:
    The service was stopped successfully.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="FIMSynchronizationService" />
        <EventID Qualifiers="16384">2002</EventID>
        <Level>4</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:28:30.000Z" />
        <EventRecordID>3360</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security />
      </System>
      <EventData>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-Windows-CertificateServicesClient
    Date:          19/11/2009 7:27:06 PM
    Event ID:      1
    Task Category: None
    Level:         Information
    Keywords:     
    User:          SP\sp_admin
    Computer:      SPS.sp.spdevwiki.com
    Description:
    Certificate Services Client has been started successfully.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-CertificateServicesClient" Guid="{73370bd6-85e5-430b-b60a-fea1285808a7}" />
        <EventID>1</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-19T11:27:06.868Z" />
        <EventRecordID>3359</EventRecordID>
        <Correlation />
        <Execution ProcessID="5804" ThreadID="5992" />
        <Channel>Application</Channel>
        <Computer>SPS.sp.spdevwiki.com</Computer>
        <Security UserID="S-1-5-21-416680604-3529024251-3629583212-1110" />
      </System>
      <EventData>
      </EventData>
    </Event>


    SharePoint Solution Architect, Perth Australia - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - Readify - http://wss.made4the.net/- http://www.sharepointdevwiki.com/
    Thursday, November 19, 2009 1:20 PM
  • Hello, I am experiencing a similar issue.

    I create a new User Profile Service which works fine, then go to start profile synchronization in Services on Server.

    In the ULS logs I get this:

    11/20/2009 08:10:16.68     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Portal Server          User Profiles                     9i1s    Medium      UserProfileApplication.SynchronizeMIIS: Begin setup for 'UP'.    14b84313-b7d9-4da5-b388-e18b9b003cf3
    11/20/2009 08:10:16.69     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Portal Server          User Profiles                     9i2a    Medium      ILM Configuration: Configuring database...    14b84313-b7d9-4da5-b388-e18b9b003cf3
    11/20/2009 08:10:16.72     WebAnalyticsService.exe (0x086C)            0x0E10    Web Analytics Services            Component Controller              c2es    Medium      Executing the Web Analytics component Logging Extraction.     
    11/20/2009 08:10:16.75     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Portal Server          User Profiles                     9i1w    Medium      ILM Configuration: Error 'ERR_CONFIG_DB'.    14b84313-b7d9-4da5-b388-e18b9b003cf3
    11/20/2009 08:10:16.75     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Portal Server          User Profiles                     9sip    High        UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_CONFIG_DB     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result)     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage2()     at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).    14b84313-b7d9-4da5-b388-e18b9b003cf3
    11/20/2009 08:10:16.75     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Portal Server          User Profiles                     9i1u    Medium      UserProfileApplication.SynchronizeMIIS: End setup for 'UP'.    14b84313-b7d9-4da5-b388-e18b9b003cf3
    11/20/2009 08:10:16.75     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Foundation             Topology                          8xqz    Medium      Updating SPPersistedObject ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob. Version: 29794 Ensure: False, HashCode: 34172749, Id: 639c6b56-9449-4682-91ff-5db77c1ff5cd, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()     at Microsoft.SharePoint.Administration.SPJobDefinition.Update()     at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)      14b84313-b7d9-4da5-b388-e18b9b003cf3
    11/20/2009 08:10:16.80     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Foundation             Monitoring                        b4ly    Medium      Leaving Monitored Scope (Timer Job ProfileSynchronizationSetupJob). Execution Time=189.072633533033    14b84313-b7d9-4da5-b388-e18b9b003cf3
    11/20/2009 08:10:16.80     OWSTIMER.EXE (0x0AEC)                       0x133C    SharePoint Foundation             Topology                          8dyx    High        Deleting the SPPersistedObject, ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob.    14b84313-b7d9-4da5-b388-e18b9b003cf3



    If I then go into the User Profile Management and add my AD entry to it, it is able to find my AD and I am able to select OU's from the picker. I select everything from the top, hit Save and it doesn't save. In the ULS logs it has:

    11/20/2009 08:17:50.86     w3wp.exe (0x1050)                           0x0CF8    SharePoint Portal Server          User Profiles                     f3be    High        EditDSServer._LoadAndCommitConnectionInfoFromForm(): System.ArgumentException: MOSS MA not found.     at Microsoft.Office.Server.UserProfiles.DirectoryServiceConnection.UpdateInternal()     at Microsoft.Office.Server.UserProfiles.Connection.<Update>b__0()     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)     at Microsoft.Office.Server.UserProfiles.Connection.Update()     at Microsoft.Office.Server.UserProfiles.DirectoryServiceConnection..ctor(ConnectionManag...    7371f970-e468-44c3-a26c-8cfa97465859
    11/20/2009 08:17:50.86*    w3wp.exe (0x1050)                           0x0CF8    SharePoint Portal Server          User Profiles                     f3be    High        ...er ds, ConnectionType type, String displayName, String server, Int32 port, Boolean useSSL, String accountDomain, String accountUsername, SecureString accountPassword, String userIdAttribute, String providerName, List`1 preferredDomainControllers, List`1 namingContexts, String spsClaimProviderTypeValue, String spsClaimProviderIdValue)     at Microsoft.Office.Server.UserProfiles.ConnectionManager.AddActiveDirectoryConnection(String displayName, String server, Boolean useSSL, String accountDomain, String accountUsername, SecureString accountPassword, List`1 preferredDomainControllers, List`1 namingContexts, String spsClaimProviderTypeValue, String spsClaimProviderIdValue)     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.EditDSServer._LoadAndCommitConnectionInfoFromForm(Boolean fNewConn...    7371f970-e468-44c3-a26c-8cfa97465859
    11/20/2009 08:17:50.86*    w3wp.exe (0x1050)                           0x0CF8    SharePoint Portal Server          User Profiles                     f3be    High        ...ection).    7371f970-e468-44c3-a26c-8cfa97465859

    The synchronization service is still stuck at Starting

    Has anyone else had similar problems?

    Thanks
    Thursday, November 19, 2009 9:52 PM
  • A few people have mentioned their user profile service getting stuck on 'starting'. You can stop the service by using PowerShell stop-spserviceinstance. But first of all you'll need to get the GUID of the service. To do this, use the PowerShell cmdlet get-spserviceinstance and then grab the user profile synchronization service GUID. However, by simply stopping the service might not resolve your current issues.

    I've added a post to my blog on my experiences of setting up user profile synchronization service along with instructions on how to stop the 'starting' service using PowerShell. http://www.kathyhughes.com/blog/Lists/Posts/Post.aspx?ID=14.
    Saturday, November 21, 2009 12:05 AM
  • I've posted a full step by step of building entire virtual machine over at www.sharepointadminwiki.com with all the steps to get user profiles working...next stop "My Sites".
    http://www.sharepointdevwiki.com/display/spadmin2010/Install+SharePoint+2010+Public+Beta+on+Standalone+Windows+Server+2008

    Thanks for your help on this...as you stated, it works fine when you do everything as domain admin...the moment you start adding service accounts it gets extremely wobbly. So "bad practice" for now ;-) heh it's only beta!
    SharePoint Solution Architect, Perth Australia - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - Readify - http://wss.made4the.net/- http://www.sharepointdevwiki.com/
    • Marked as answer by Jeremy Thake Saturday, November 21, 2009 7:54 AM
    Saturday, November 21, 2009 7:54 AM
  • I had this problem as well. What solved it for me was to add my farm account to the local administrators group, reboot server, then start it again.

    However, I also tried logging in as the identity running the central administration website but then I couldn't see the "Manage services on farm" menu item. So something tells me this is a security issue.

    Right now I'm running with my farm account as local administrator on the server.

    Tuesday, February 16, 2010 5:30 PM
  • System.TypeInitializationException: The type initializer for 'Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection' threw an exception. ---> System.Configuration.ConfigurationErrorsException: Required attribute 'externalHostName' not found. (C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe.Config line 29)

     

     

    how to config the externalHostName?


    http://www.dreamingcatstudio.com
    • Proposed as answer by Kurt Boswood Friday, July 9, 2010 3:33 AM
    Tuesday, May 18, 2010 9:49 PM
  • Let me start by saying oops, didn't mean to click the "Propose as Answer".

    I too had the exact same problem (Sharepoint 2010 RTM) and have spent days trying to fix the "User Profile Service Application"...

    These are the steps i took to resolve the problem (hope this helps others):

    Notes:
    Log file Location:
    "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS"

    ForeFront Synchronization Service Manager:
    "C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe"

     

    Step1:

    Check the “Forefront Identity Manager Synchronization Service” in windows services and start.

    If the service does not start, check the registry in the following location and make sure the Server / SQLInstance fields are correct

    HKLM\CurrentControlSet\Services\FIMSynchronizationService\Parameterss

    If the details are correct, make sure the service is logging in with sharepoint farm administrator account (the account used to installed sharepoint)

    e.g.          domain\sharepoint
                   

    If the above still does not work, check the database name is correct in the registry (same location) – DBNAME (REG_SZ)

     

    Once the service starts, run “miisclient.exe” (link above) and check the service is connecting to the database 

     

    Step2:

    If the sharepoint service “User Profile Synchronization Service” says “Starting” and doesn’t change, Launch sharepoint management shell (powershell)

    run: Get-SPServiceInstance

    PS C:\Users\sharepoint> Get-SPServiceInstance

    TypeName                         Status   Id
    --------                         ------   --
    Managed Metadata Web Service     Online   da428754-70d3-4002-a70f-6973b101e054
    User Profile Synchronization ... Provis.  43aeee2e-92db-407c-9f28-64edcabdf11d
    Business Data Connectivity Se... Online   ca22c5d2-bb31-4d8e-a8df-ca5c4cd00493
    Secure Store Service             Online   c05255e9-5f75-49c6-87f3-546474fad754
    Claims to Windows Token Service  Disabled 445efc95-ad31-4bf4-89f8-fe07ca05cd64
    Microsoft SharePoint Foundati... Online   cec96048-94b8-43e2-85ca-3daf4c87c060
    PerformancePoint Service         Online   67d77331-22b0-4a09-bf09-d0a4e5d469fe
    Application Registry Service     Online   44a3bf84-9898-4d47-8529-d390b2549e05
    Microsoft SharePoint Foundati... Online   42fe18c0-56d3-442d-8bdb-f2298188ca51
    etc...

     

    Stop-SPServiceInstance “ID” e.g. Stop-SPServiceInstance 43aeee2e-92db-407c-9f28-64edcabdf11d

    Go back to the "Central Admin" website and check the "User Profile Synchronization Service" under "Manage services on server" and make sure the service is now stopped (in red)

     

    Run:  Get-SPServiceApplicationPool

    If the “UserProfileService Application” app pool does not exist, create a new app pool by running the following:

    New-SPServiceApplicationPool

    Type the name of the service app (UserProfileServiceApplication)
    Type the user account (domain\username) ** account must exist in sharepoint and must be the “Farm Admin Service account” (the one sharepoint was installed with)

    Confirm the application pool is created by running “Get-SPServiceApplicationPool”

     

    Note: If the “UserProfileServiceApplication” app pool did not exist, you can try starting the “User Profile Synchronization Service” from sharepoint central admin.

     

     Step3:

    from the command prompt, run: cliconfg.exe

    Enable “named pipes” and “TCP/IP” (if not already there)

     

     

     

    Step4:

    We need to remove and re-create the “User Profile Service Application” (last resort)

    BACKUP THE SQL DATABASES IF THE PROFILE INFO IS IMPORTANT:
    User Profile Service Application_SocialDB_xxxxxxxxx
    User Profile Service Application_ProfileDB_xxxxxxxxxx
    User Profile Service Application_SyncDB_ xxxxxxxxx

     

    Go to “Manage Service Applications”, click on “User Profile Service Application” (off to the right, not on the text) and click “Delete” from the ribbon. (tick the box to delete the Databases if your willing to lose profile information, otherwise leave them - unticked)

    Recycle IIS (run from command prompt: IISRESET.exe) – just for the sake of it

     

    Go to “Manage Service Applications” and click on “New” from the ribbon and click “User Profile Service Application”

    The name should be “User Profile Service Application”, click the “Use existing Application Pool” and use the “UserProfileServiceApplication”

    For the databases, either name them as you see fit, or enter the names of the previous databases

    Select the Profile Synchronization Instance (the relevant server)
    Name the mysite website (
    http://mysitexxx.xxxx.xxx.gov.au:80)

    Click Finish

    Fingers crossed, refresh the web page and click the “User Profile Service Application” and you should be able to get in.


    if all else fails, check the logs and find out what is failing (Category: User Profiles), either that or copy and paste the correlation id error message from the sharepoint website and search the logfile for the correlation ID

     

    Additional Notes:

    Make sure you have the app pool (Service Aoolication Pool - UserProfileServiceApplication) and the set to the same service account as the "Farm account" (can be changed under "Security", Configure Service Accounts"

    you can also try changing the "Sharepoint Web Service Default" app pool the the farm admin account

     

    hope this helps someone out there,

     

    Kurt.

     

    • Proposed as answer by Kurt Boswood Friday, July 9, 2010 3:57 AM
    Friday, July 9, 2010 3:56 AM
  • All step is not work!!.. I'm so frustrated..
    Thursday, July 22, 2010 4:57 AM
  • Similar issue.  DB name registry value not found.  Service doesn't start.  Error about file not found.
    Friday, July 23, 2010 2:37 AM
  • Permission Required: 1. User Profile Sync account 2. Directory Sync account User Profile Sync Account: This account requires the following permissions for provisioning: Farm Account (timer service account) · Local Admin (for duration of sync provisioning) · Logged on as the account during provisioning · Member of Pre-Windows 2k compatibility group Directory Sync Account: The directory sync (dir sync) account is responsible for authenticating\enumerating against a directory server in order to sync changes. This account requires specific permissions to a directory server in order to read and “sometimes” write to a directory. http://support.microsoft.com/kb/303972
    Tuesday, July 27, 2010 3:38 AM
  • I solved the problem.

    I didn't start "User Profile Syncronization Service". I started only "User Profile Service".

    I could not aware of existence "User Profile Syncronization Service". It's title is translated to my languaget(Korean) but "User Profile Service" is not Translated.

    Tuesday, July 27, 2010 7:09 AM
  • Hi,

    I had the same problem with the "User Profile Synchronization Service stuck on starting". I find the way to finally stop it...here it is:

    1. Open the Sharepoint 2010 Management Shell
    2. Type the command : get-spserviceinstance
    3. You will have a list of all service instance in your farm
    4. Copy to the clipboard the ID of the "User Profile Synchronization Service"
    5. Type the command : Stop-SPServiceInstance [InstanceID]
    6. It will ask you if you want to stop the service
    7. Say Yes, and the service will be Stopped

    For the setup of the User Profiel Application Service look at this doc: http://www.harbar.net/articles/sp2010ups.aspx

    Cheers,

    David

    Wednesday, August 11, 2010 1:13 PM
  • Ditto on following the Harbar instructions TO THE LETTER. We did so today after experiencing frustrations w/ the User Profile Service and were successful in getting it all working.

    The one note: For Profile Sync, if you're running HTTPS/Secure, BE SURE you use sps3s:// rather than sps3:// in your Profile Search setup.

    Wednesday, August 11, 2010 3:01 PM
  • Let me start by saying oops, didn't mean to click the "Propose as Answer".

    I too had the exact same problem (Sharepoint 2010 RTM) and have spent days trying to fix the "User Profile Service Application"...

    These are the steps i took to resolve the problem (hope this helps others):

    Notes:
    Log file Location:
    "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS"

    ForeFront Synchronization Service Manager:
    "C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe"

     

    Step1:

    Check the “Forefront Identity Manager Synchronization Service” in windows services and start.

    If the service does not start, check the registry in the following location and make sure the Server / SQLInstance fields are correct

    HKLM\CurrentControlSet\Services\FIMSynchronizationService\Parameterss

    If the details are correct, make sure the service is logging in with sharepoint farm administrator account (the account used to installed sharepoint)

    e.g.          domain\sharepoint
                   

    If the above still does not work, check the database name is correct in the registry (same location) – DBNAME (REG_SZ)

     

    Once the service starts, run “miisclient.exe” (link above) and check the service is connecting to the database 

     

    Step2:

    If the sharepoint service “User Profile Synchronization Service” says “Starting” and doesn’t change, Launch sharepoint management shell (powershell)

    run: Get-SPServiceInstance

    PS C:\Users\sharepoint> Get-SPServiceInstance

    TypeName                         Status   Id
    --------                         ------   --
    Managed Metadata Web Service     Online   da428754-70d3-4002-a70f-6973b101e054
    User Profile Synchronization ... Provis.  43aeee2e-92db-407c-9f28-64edcabdf11d
    Business Data Connectivity Se... Online   ca22c5d2-bb31-4d8e-a8df-ca5c4cd00493
    Secure Store Service             Online   c05255e9-5f75-49c6-87f3-546474fad754
    Claims to Windows Token Service  Disabled 445efc95-ad31-4bf4-89f8-fe07ca05cd64
    Microsoft SharePoint Foundati... Online   cec96048-94b8-43e2-85ca-3daf4c87c060
    PerformancePoint Service         Online   67d77331-22b0-4a09-bf09-d0a4e5d469fe
    Application Registry Service     Online   44a3bf84-9898-4d47-8529-d390b2549e05
    Microsoft SharePoint Foundati... Online   42fe18c0-56d3-442d-8bdb-f2298188ca51
    etc...

     

    Stop-SPServiceInstance “ID” e.g. Stop-SPServiceInstance 43aeee2e-92db-407c-9f28-64edcabdf11d

    Go back to the "Central Admin" website and check the "User Profile Synchronization Service" under "Manage services on server" and make sure the service is now stopped (in red)

     

    Run:  Get-SPServiceApplicationPool

    If the “UserProfileService Application” app pool does not exist, create a new app pool by running the following:

    New-SPServiceApplicationPool

    Type the name of the service app (UserProfileServiceApplication)
    Type the user account (domain\username) ** account must exist in sharepoint and must be the “Farm Admin Service account” (the one sharepoint was installed with)

    Confirm the application pool is created by running “Get-SPServiceApplicationPool”

     

    Note: If the “UserProfileServiceApplication” app pool did not exist, you can try starting the “User Profile Synchronization Service” from sharepoint central admin.

     

     Step3:

    from the command prompt, run: cliconfg.exe

    Enable “named pipes” and “TCP/IP” (if not already there)

     

     

     

    Step4:

    We need to remove and re-create the “User Profile Service Application” (last resort)

    BACKUP THE SQL DATABASES IF THE PROFILE INFO IS IMPORTANT:
    User Profile Service Application_SocialDB_xxxxxxxxx
    User Profile Service Application_ProfileDB_xxxxxxxxxx
    User Profile Service Application_SyncDB_ xxxxxxxxx

     

    Go to “Manage Service Applications”, click on “User Profile Service Application” (off to the right, not on the text) and click “Delete” from the ribbon. (tick the box to delete the Databases if your willing to lose profile information, otherwise leave them - unticked)

    Recycle IIS (run from command prompt: IISRESET.exe) – just for the sake of it

     

    Go to “Manage Service Applications” and click on “New” from the ribbon and click “User Profile Service Application”

    The name should be “User Profile Service Application”, click the “Use existing Application Pool” and use the “UserProfileServiceApplication”

    For the databases, either name them as you see fit, or enter the names of the previous databases

    Select the Profile Synchronization Instance (the relevant server)
    Name the mysite website (
    http://mysitexxx.xxxx.xxx.gov.au:80)

    Click Finish

    Fingers crossed, refresh the web page and click the “User Profile Service Application” and you should be able to get in.


    if all else fails, check the logs and find out what is failing (Category: User Profiles), either that or copy and paste the correlation id error message from the sharepoint website and search the logfile for the correlation ID

     

    Additional Notes:

    Make sure you have the app pool (Service Aoolication Pool - UserProfileServiceApplication) and the set to the same service account as the "Farm account" (can be changed under "Security", Configure Service Accounts"

    you can also try changing the "Sharepoint Web Service Default" app pool the the farm admin account

     

    hope this helps someone out there,

     

    Kurt.

     

    erm... just a heads up for anyone using sql instances for their sharepoint db's... as I have just wasted 1.5 days scratching my head trying to get this to work.:

    http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/6d467dd8-dc2b-4191-8b5c-6bcf61448fb5

     

    Tuesday, August 17, 2010 3:22 PM
  • ok - done some more digging and think this is now fixed in a hotfix: http://support.microsoft.com/kb/983497/
    Tuesday, August 17, 2010 4:07 PM
  • I must say that I was not successful in getting my User Profile Synchronization Service to start, it was always in 'Starting' & the FIM Synchronization Service on the server never would start. But in the above article, in Step#1, The mention to look into the Registry for FIM & check the DB did the trick.

     

    I was able to get the FIM services to start and got on my way to setup new profile connections.

     

    Thanx Kurt for the direction.

    • Proposed as answer by Gr8Work Thursday, October 21, 2010 5:20 PM
    Thursday, October 21, 2010 5:15 PM
  • What should the correct DBName be? Mine is:

    DBName           REG_SZ              User Profile Service Application_SyncDB_3f3844ba5bc34f9e9e7d55b2e161c8b1.

     

    Is this what the DBName is supposed to look like or is it simply something like 'SyncDB'

    Monday, December 6, 2010 4:53 PM
  • Hi
    Go to SQL Server 2008 R2 server manager.
    look at the databases
    there is one which starts :- User profile Service Application_SyncDB  <followed by a GUID>

    This is the database name which should be in the Registry key.

    Regards

    Nigel

    Friday, December 10, 2010 4:37 PM
  • It worked it worked....my long time issue "stucking on starting.." solved.

    This is what i did in all

    1. Stopped the Service using powershell command stop-spserviceinstance <guid>

    2. followed Kurt's direction here - Made the forefront services start off...Enabled TCP/IP and Named Pipes as he had mentioned in Step 3..

    And Magic...user profile started....

    Happy Lady!

    Thursday, February 24, 2011 9:14 AM
  • yeah this working. I love you, Kurt! tnx!
    Friday, October 5, 2012 4:08 AM