Support-Info: (SharePoint UPA) FIM Services don’t start: Error creating com objects. Error code: -2147467259

PRODUCTS INVOLVED

  • Microsoft SharePoint 2013
  • Microsoft SharePoint 2013 User Profile Synchronization Application (UPA)
    • Microsoft Forefront Identity Manager 4.0.2450.51
  • Microsoft SQL Server 2012 Service Pack 3
  • TLS v1.0 is Disabled
  • TLS v1.2 is Enabled

 

PROBLEM SCENARIO DESCRIPTION

In this specific issue, the two Forefront Identity Manager Services associated with the SharePoint UPA would not start. The failed starts, did provide exceptions documented in the Application Event Log.  Attempts were made to start these services via Central Administration as well as the Services MMC.  Once you attempt to start the services and they fail, go to the Application and System Event Logs looking for information on the cause of the issue.

 

NOTE While this specific issue documented here is for the SharePoint UPA, this information may apply to other builds of the FIM/MIM Synchronization Service as it is more in reference to the security move to TLS v1.2.

 

APPLICATION EVENT LOG: Source: Forefront Identity Manager Synchronization Service
The server encountered an unexpected error and stopped.

“BAIL: MMS(17552): sql.cpp(252): 0x80004005 (Unspecified error)

BAIL: MMS(17552): storeimp.cpp(234): 0x80004005 (Unspecified error)

ERR: MMS(17552): server.cpp(373): Failed to connect to the database User Profile Service Application_SyncDB_

BAIL: MMS(17552): server.cpp(374): 0x80004005 (Unspecified error)

BAIL: MMS(17552): server.cpp(3860): 0x80004005 (Unspecified error)

BAIL: MMS(17552): service.cpp(1539): 0x80004005 (Unspecified error)

ERR: MMS(17552): service.cpp(988): Error creating com objects. Error code: -2147467259. This is retry number 0.

BAIL: MMS(17552): clrhost.cpp(283): 0x80131022

BAIL: MMS(17552): scriptmanagerimpl.cpp(7670): 0x80131022

BAIL: MMS(17552): server.cpp(251): 0x80131022

BAIL: MMS(17552): server.cpp(3860): 0x80131022

BAIL: MMS(17552): service.cpp(1539): 0x80131022

ERR: MMS(17552): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 1.

BAIL: MMS(17552): clrhost.cpp(283): 0x80131022

BAIL: MMS(17552): scriptmanagerimpl.cpp(7670): 0x80131022

BAIL: MMS(17552): server.cpp(251): 0x80131022

BAIL: MMS(17552): server.cpp(3860): 0x80131022

BAIL: MMS(17552): service.cpp(1539): 0x80131022

ERR: MMS(17552): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 2.

BAIL: MMS(17552): clrhost.cpp(283): 0x80131022

BAIL: MMS(17552): scriptmanagerimpl.cpp(7670): 0x80131022

BAIL: MMS(17552): server.cpp(251): 0x80131022

BAIL: MMS(17552): server.cpp(3860): 0x80131022

BAIL: MMS(17552): service.cpp(1539): 0x80131022

ERR: MMS(17552): service.cpp(988): Error creating com objects. Error code: -2146234334. This is retry number 3.

BAIL: MMS(17552): service.cpp(1002): 0x80131022

Forefront Identity Manager 4.0.2450.51”

 

 

APPLICATION EVENT LOG: Source: Forefront Identity Manager Service
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. (D:\Program Files\Microsoft Office Servers\15.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)

 

CAUSE

  • Support for TLS v1.2 was not installed on this client/application machine

 

RESOLUTION

 

  • In this specific scenario, the Hotfix(QFE) for SQL Server Native Client 11.0 was installed and successfully working. To resolve this scenario, the Hotfix(QFE) for SQL Server Native Client 10.0 had to be installed.

 

ADDITIONAL INFORMATION

  • We did utilize a UDL file to test the connection to SQL Server.
    • OleDB Failed
    • Native Client 10.0 Initially failed until the QFE was installed
    • Native Client 11.0 initially succeeded because the QFE was installed.

 

TROUBLESHOOTING LINKS:

NOTE These are some links that I reviewed during the course of this issue, that lead me to believe it was an issue with SQL Server connectivity

 

 

 

 

 

 

 

 

Keywords Iamsupport sharepoint upa -2147467259