Error when trying to register new Azure Log Analytics connection in Operations Manager 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-2254199%22%20slang%3D%22en-US%22%3EError%20when%20trying%20to%20register%20new%20Azure%20Log%20Analytics%20connection%20in%20Operations%20Manager%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2254199%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20following%20error%20is%20received%20when%20attempting%20a%20new%20Log%20Analytics%20connection%20in%20SCOM%202019.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22An%20error%20occurred%20while%20making%20the%20HTTP%20request%20to%20%3COPINSIGHTS%20url%3D%22%22%3E.%20This%20could%20be%20due%20to%20the%20fact%20that%20the%20server%20certificate%20is%20not%20configured%20properly%20with%20HTTP.SYS%20in%20the%20HTTPS%20case...%22%3C%2FOPINSIGHTS%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222021-04-02_9-09-55.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F269486i547B3A75211DCF56%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%222021-04-02_9-09-55.png%22%20alt%3D%222021-04-02_9-09-55.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EResolution%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EI%20enabled%20TLS%201.2%20support%20using%20the%20script%20provided%20by%20Kevin%20Holman.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fkevinholman.com%2F2018%2F05%2F06%2Fimplementing-tls-1-2-enforcement-with-scom%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fkevinholman.com%2F2018%2F05%2F06%2Fimplementing-tls-1-2-enforcement-with-scom%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnce%20I%20enabled%20TLS1.2%20and%20rebooted%20the%20SCOM%20management%20server%2C%20I%20was%20able%20to%20successfully%20add%20the%20connection%20to%20Log%20Analytics.%20It%20appears%20TLS1.2%20is%20no%20longer%20just%20a%20%22recommendation%22%20for%20communicating%20with%20many%20Azure%20services.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%20Server%202016%20Datacenter%3C%2FP%3E%3CP%3ESystem%20Center%20Operations%20Manager%202019%2C%20UR2%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

The following error is received when attempting a new Log Analytics connection in SCOM 2019.

 

"An error occurred while making the HTTP request to <opinsights URL>. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case..."

2021-04-02_9-09-55.png

Resolution:

I enabled TLS 1.2 support using the script provided by Kevin Holman.

 

https://kevinholman.com/2018/05/06/implementing-tls-1-2-enforcement-with-scom/

 

Once I enabled TLS1.2 and rebooted the SCOM management server, I was able to successfully add the connection to Log Analytics. It appears TLS1.2 is no longer just a "recommendation" for communicating with many Azure services.

 

 

Windows Server 2016 Datacenter

System Center Operations Manager 2019, UR2

 

 

0 Replies