question

Hi @kumaravelu-1265,

Do you see this event in the System Log? What makes you think that it is related to SCOM? What TLS Version is currentl configured:

• in SCOM?
  

• on your OS?
  

• on your SCOM DBs?

Can you please go over this post and see if this is also helpful:

A fatal error occurred while creating a TLS client credential. The internal error state is 10013
https://social.technet.microsoft.com/Forums/en-US/fd626e47-9ee7-41c5-b11a-ae696e3b6b5b/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-error-state-is-10013?forum=ws2016

A fatal error occurred while creating a TLS client credential. The internal error state is 10013
https://stackoverflow.com/questions/53121859/a-fatal-error-occurred-while-creating-a-tls-client-credential-the-internal-erro

Please check those out and I am pretty sure that those will help you.

---

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Stoyan Chalakov

@kumaravelu-1265, Research and find a similar issue. in that case, these SCHANNEL 36871 events being logged are due to a configuration on the server itself.

Here is the resolution for that issue for the reference:
1.Made the necessary modifications from the following
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls
Transport Layer Security (TLS) best practices with the .NET Framework.

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
Note: please do a backup before we change any registry key.

2.After these modifications are made to enable .NET to utilize more secure TLS versions a reboot is required.
3.After this is accomplished the SCHANNEL events are no more.

Hope it can help.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

@Crystal-MSFT I think the forum post removed the "\" between Microsoft and .NETFramework. It did just now for me when I attempted to point it out.