Asked by:
Frequent Event ID 36888 Windows Schannel errors in the Event Viewer

Question
-
Went to the Event Viewer and found 154 occurances of the following error:
"A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 70. The Windows SChannel error state is 105."
Anyone else see these? Doesn't seem to impact anything that I can see.Sunday, March 4, 2012 9:02 PM
All replies
-
Yeah I've also been getting them ever since I did a "System Refresh" (Win8 CP) this morning. Never noticed them before that. Someone posted elsewhere that they seem to occur immediately following the installation of a new Metro app. I can confirm this. I also notice that these errors (source: "schannel") are always preceded by a couple seconds by this information level event:
"The Software Protection service entered the running state."
So the problem might be with SP. I'll post back if I come up with anything else, but help on this would be appreciated. As noted above - nothing seems to be functionally impacted... I just hate seeing all those red errors in event viewer!
EDIT: I notice now that there are several other events that trigger the Schannel error besides Software Protection: Windows Installer or Windows Update entering the running state also trigger the error.
- Edited by samurai12 Thursday, March 8, 2012 5:16 PM
Wednesday, March 7, 2012 2:32 AM -
Disabling logging with the information here worked for me:
- Proposed as answer by Arthur XieModerator Thursday, March 8, 2012 8:22 AM
Wednesday, March 7, 2012 7:31 AM -
Thanks rseiler - this would indeed seem to be the solution to seeing all those damned red errors in Event Viewer. But it doesn't so much fix the problem (if indeed there is one- I still see no effect on my systems functionality) as prevent notifications about it from appearing.
Oh well -- thus begins my learning curve re: schannel. Probably not the most exciting Google Search session i'll ever have.
Cheers.
Thursday, March 8, 2012 5:23 PM -
Have at it and report back, but I've learned to pick my battles with Event Viewer. In this case, I saw enough comments along the lines of it being benign and safely ignored, that I realized that I've got a good reason for taking the easy way out.Thursday, March 8, 2012 5:34 PM
-
I also have it and it (windows consumer preview) and it appears to be a port permissions problem with a malware app firewall (ESET)Monday, March 19, 2012 4:13 AM
-
Ok I got the problem solved - on my system at least (running Windows 8 Consumer preview) … I stumbled into this solution while trouble shooting a different (DCOM) error message that I kept getting:
In Group Policy Editor (run: gpedit.msc), went to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enabled "allow local activation security check exemptions"
No more Schannel or DCOM errors now!
Of course, i'm not suggesting this as a cure-all --- from what I've read on other forums, these schannel errors are quite common and are probably generated as a result of many possible different conflicts -- this is just what worked for me. But if anyone is also getting the ton of DCOM errors along with the schannel errors, it's worth a try. Hope this helps.
Cheers.
Friday, March 30, 2012 11:35 PM -
I am using Windows 8 Consumer Preview 64-bit edition, after installing couple of Metro Apps from store i start getting DCOM and Schannel error messages.
Soon after whenever i try to log in into a site or take remote of a computer the credentials pop up would freeze.
i tried the solution provided by samurai12 it worked for me. No more DCOM and Schannel errors as of now..\m/
Thursday, May 10, 2012 5:23 AM -
I'm running Windows 8 Pro RTM and getting something similar..
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
Saturday, August 18, 2012 11:43 AM -
I'm running Windows 8 Pro RTM and getting something similar..
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
Copy that. Same here (Win8 Ent RTM 64Bit). And right after that the whole system freezes. I can easily reproduce this by using an application trying to communicate via TLS (eg Skype). Crashes every time. Nothing works. No mouse, no keyboard. Not even switching caps lock.
Rather annoying for an RTM ...
Monday, August 27, 2012 7:53 AM -
I'm running Windows 8 Pro RTM and getting something similar..
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
I am getting the EXACT same error on the same build.
As far as I can tell, it has no impact on system performance or functionality. I do hope, however, that a fix is in the works to deliver via Windows Update.
Josh Amacker
Wednesday, August 29, 2012 5:56 AM -
Another apparent solution to add to the ones in this thread, disabling "Use TLS 1.0" in IE's Advanced Options. Not sure if that's a good idea or not but thought I'd add it here.
Wednesday, August 29, 2012 6:27 AM -
I'm running Windows 8 Pro RTM and getting something similar..
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51. The Windows SChannel error state is 900.
I am getting the EXACT same error on the same build.
As far as I can tell, it has no impact on system performance or functionality. I do hope, however, that a fix is in the works to deliver via Windows Update.
Josh Amacker
Ditto. Enterprise RTMTechwest Resources
Friday, September 7, 2012 8:48 PM -
same. datacenter 2012, stand-alone server (no domain join)Tuesday, September 11, 2012 5:13 PM
-
Just started seeing this on Windows 8 RTM, and it's paired with losing connectivity to network resources on a Windows 2008 domain. Explorer windows will lock up for several minutes, but Internet access seems unaffected. A reboot cleared up the problem for the time being.
Wednesday, October 3, 2012 8:38 PM -
seeing this too and it appears to be dropping wifi connections
Saturday, December 8, 2012 2:23 AM -
Ok I got the problem solved - on my system at least (running Windows 8 Consumer preview) … I stumbled into this solution while trouble shooting a different (DCOM) error message that I kept getting:
In Group Policy Editor (run: gpedit.msc), went to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enabled "allow local activation security check exemptions"
No more Schannel or DCOM errors now!
Of course, i'm not suggesting this as a cure-all --- from what I've read on other forums, these schannel errors are quite common and are probably generated as a result of many possible different conflicts -- this is just what worked for me. But if anyone is also getting the ton of DCOM errors along with the schannel errors, it's worth a try. Hope this helps.
Cheers.
Thank you! This worked!
I too like to remove the underlying problem rather than hide it.
Saturday, December 15, 2012 6:25 PM -
Same situation with Win 7 Pro, whether use IE8 or IE9. Thank you.
Thursday, January 3, 2013 5:59 AM