Repeated Schannel 36887 Errors - Fatal alert 46

Question

I'm having a strange Schannel error repeatedly on my Exchange SP2 install.  Everything is working properly (webmail/ecp/activesync), but I get repeated Schannel event 36887 errors.  Each error coincides exactly with two Security Audit Success events. 
This is happening on average more than once per minute. 
Schannel Event 36887
The following fatal alert was received: 46.
Microsoft Windows Security  Event 5058:
Key file operation.
Subject:
Security ID: NETWORK SERVICE
Account Name: <servername$>
Account Domain: <mydomain>
Logon ID: 0x3e4
Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: Not Available.
Key Name: <omitted>
Key Type: Machine key.
Key File Operation Information:
File Path: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\<omitted>
Operation: Read persisted key from file.
Return Code: 0x0
Microsoft Windows security event 5061
Cryptographic operation.
Subject:
Security ID: NETWORK SERVICE
Account Name: <servername$>
Account Domain: <mydomain>
Logon ID: 0x3e4
Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: RSA
Key Name: <omitted, same as above event>
Key Type: Machine key.
Cryptographic Operation:
Operation: Open Key.
Return Code: 0x0

Answer 1

These forums are useless. People post a useless answer and then mark it as an answer for themselves. Meanwhile, my EXCHANGE server keeps filling the event log with this error. The error did not occur when the server was set up. No changes were made
to the server except for Windows updates. Ergo, Microsoft did something to cause this error, but they don't want to do anything to fix the error. And why would we discuss this in the IIS forum when it's an Exchange issue? Possibly Exchange is using IIS but
it's still an Exchange issue.
I usually simply disable the chatter and only enable it if I am troubleshooting an error in the registry:
Set-itemproperty HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel -Name
EventLogging -Value 0
As for why that chatter is in the logs in the first place, that I do not know, sorry.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.