Additional Orchestrator Connector will not start sync

Question

Hi,

in two environments from a customer we have the following issue: A new Connector for Orchestrator can be created but although the Wizard succeeded the Connector never runs.
A previous Connector to Orchestrator works.
When creating the connector the following error is logged in OperationsManager-Log:

The request for management pack identified by version independent identity "50daaf82-06ce-cacb-8cf5-3950aebae0b0" and version dependent identity "e2b58ce4-3472-4b84-ab72-277a4cba7bc3" requested by agent "38b16a62-0816-c832-4d81-aebaa36bbd5d" failed due to the following exception ": Cannot find management pack with version dependent ID e2b58ce4-3472-4b84-ab72-277a4cba7bc3 in the database.".   

"50daaf82-06ce-cacb-8cf5-3950aebae0b0" is the ServiceManager.LinkingFramework.Library. The MP with the other ID do not find. In the export of ServiceManager.LinkingFramework.Library he other ID is not listed.

A new created AD-Connector works here and in a third SCSM environment a new Connector for Orchestrator will start and succeed after creation.

Has anyone an idea to solve this issue?

Regards,
Stefan

Answer 1

Hi,

the Solution was that on the Windows 2012 R2 win SCSM 2016 TLS 1.2 was not forced (https://learn.microsoft.com/en-us/system-center/scom/plan-security-tls12-config?view=sc-om-2019):

# Tighten up the .NET Framework  
$NetRegistryPath = "HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319"  
New-ItemProperty -Path $NetRegistryPath -Name "SchUseStrongCrypto" -Value "1" -PropertyType DWORD -Force | Out-Null  
  
$NetRegistryPath = "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319"  
New-ItemProperty -Path $NetRegistryPath -Name "SchUseStrongCrypto" -Value "1" -PropertyType DWORD -Force | Out-Null  

Regards,
Stefan