Support for Windows Products
Support for Windows Products
How To Fix Error Code 36870
If you have Error Code 36870 then we strongly recommend that you download and run this (Error Code 36870) repair tool.
Symptoms & Summary
Error Code 36870 and other critical errors can occur when your Windows operating system becomes corrupted. Opening programs will be slower and response times will lag. When you have multiple applications running, you may experience crashes and freezes. There can be numerous causes of this error including excessive startup entries, registry errors, hardware/RAM decline, fragmented files, unnecessary or redundant program installations and so on.
In order to fix your error, it is recommended that you download the 'Error Code 36870 Repair Tool'. This is an advanced optimization tool that can repair all the problems that are slowing your computer down. You will also dramatically improve the speed of your machine when you address all the problems just mentioned.
Recommended: In order to repair your system and Error Code 36870, download and run Reimage. This repair tool will locate, identify, and fix thousands of Windows errors. Your computer should also run faster and smoother after using this software.
File Size 746 KB
Compatible Windows XP, Vista, 7 (32/64 bit), 8 (32/64 bit), 8.1 (32/64 bit) Windows 10 (32/64 bit)
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove
From My Forums Answered by: MS Win 2008 R2 zip code 36870 - Event ID 36870 Schannel Error Windows Server > Windows Server General Forum Question the error code returned from the cryptographic module is 0x8009030d 0 Sign in to vote Hello to everyone. From several months, only in working days, I have in the event log System
of the Domain Controller (MS Win 2008 R2) this error: "A fatal error occurred when attempting to access the SSL client credential private key. The error code returned from the cryptographic module is 0x8009030d. The internal error state is 10003." Event ID 36870 Source Schannel The
message appears twenty times about every 3 hours (only during working hours 08:00AM-08:00PM). Considering that it appears only during working hours I think it's an error of a client (all with MS Windows 7 Professional 32bit): do you have a tip for me? Thank you. Best regards. Alessandro Sunday, November 27, 2011 9:14 PM Reply | Quote Answers 2 Sign in to vote Hi, to resolve this issue you can follow the steps in this link it can help you: http://www.zerohoursleep.com/2010/11/a-fatal-error-occurred-when-attempting-to-access-the-ssl-server-credential-private-key/ Oussama Oueslati | System Engineer | vNext Consulting Edited by Oussama Oueslati Sunday, November 27, 2011 10:48 PM Marked as answer by Rick TanModerator Friday, December 02, 2011 2:34 AM Sunday, November 27, 2011 10:47 PM Reply | Quote 0 Sign in to vote Hi Alessandro, Thank you for your post. Try the Schannel 36872
of my Windows 2000 webserver while upgrading a Digital ID for "a fatal error occurred when attempting to access the tls server credential private key" Secure Email certificate.Event Type: ErrorEvent Source: SchannelEvent Category: NoneEvent ID: 36870Date:
7/11/2007Time: 1:50:10 PMUser: N/AComputer: Description: A fatal error occurred when attempting to access the SSL client event id 1057 credential private key. The error code returned from the cryptographic module is 0xffffffff. Strange thing was that it happened only on a few of the Windows 2000 servers https://social.technet.microsoft.com/Forums/en-US/17e96c48-2a1c-4fc1-8138-c1fb90f7035e/ms-win-2008-r2-event-id-36870-schannel-error?forum=winservergen in our web farm.To explain, we use a browser certificate to encrypt a small subset of transactions on our website. Verisign calls this a "Digital ID for Secure Email." During our yearly update of the certificate, we encountered the Schannel error shown above. Customers on our website would then a failure when they hit a webserver http://www.techanswerguy.com/2007/07/event-id-36870-schannel-error.html showing evidence of the problem. Again, not all webservers showed the problem, only a subset.After four hours of troubleshooting and googling, I stumbled upon a post that suggested to look at the permissions on the following directory:C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeysSomehow, when the certificate got updated earlier that morning, the administrator and Everyone user had lost ALL their privileges to Read, Write or Modify files in that directory. Because this was a Severity One condition for our web application, I decided to take the easy road and give Administrator and Everyone Read/Read&Execute/List/Write permissions on that directory.This solved the problem and allowed the customers to complete the transaction; however, it didn't tell us the cause of why installing the new certificate changed the permissions on the MachineKeys directory. I am still researching this. If I find out why this happened, I will update this post. Posted by Cacasodo at 11:23 AM Labels: digital id for secure email, error, schannel, windows 2000 If you appreciated this answer..conside
acting … weird. There were issues with the OWA site loading, and some bizarre event log messages http://peter-kline.com/?p=87 regarding SChannel errors. I began investigating these by opening the IIS http://lokna.no/?p=581 console and looking at the bindings for HTTPS, which appeared good. And then I clicked OK … the server slowed significantly (wrote thousands of messages to the event log), and then I received this message: A specified logon session does not exist. It may already code 36870 have been terminated. (Exception from HRESULT: [...]) At this moment, IIS went down. Knowing this message can happen because of a certificate validity issue, I checked the certificates console and found the certificates showed valid, with private keys in place. The event log yielded Schannel #36870 messages reading: A fatal error occurred when attempting to access the event id 36870 SSL server credential private key. The error code returned from the cryptographic module is 0x8009030D. The internal error state is 10001. Some quick Google-fu yielded the potential that my private keys were missing, or had some access issues. There are many articles out there to deal with this, such as this one at MSDN or this MS KB Article. But it's a bit lacking for Server 2012. Here's some stuff to know: Some articles reference C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA, while others reference C:\Users\All Users\Application Data\Microsoft\Crypto\RSA. The one above references C:\ProgramData\Microsoft\Crypto\RSA. On Server 2012, these are all hard links to one another. I had issues making this fix without first stopping the Cryptographic Services service first. The article wants you to confirm that Administrators has Full Control of the MachineKeys folder, and that Everyone has the following individual permissions: - List Folder/Read Data, Read Attributes, Read Extended Attributes, Create Files/Write Data, Create Folders/Append Data, Write Attributes, Write Extended Attributes, Read Permissions None of the articles discuss inherita
windows update 2011.03.24 in Windows 2008 | 1 comment Problem After patching one of our SQL servers it was acting strange. Suddenly, the reporting services service refused to service https requests, and the SCOM monitoring agent refused to start. The error message from the reporting server website as reported by opera was “Secure connection: fatal error 552”. This could be translated to either “Requested file action aborted, storage allocation exceeded”, which is an FTP status code, or "552 - Unknown authentication service call-back", which is a more likely explanation. An examination of the event logs on the server revealed some certificate related messages from the SCOM agent: Log Name: Operations Manager Source: HealthService Date: 17.03.2011 17:26:55 Event ID: 7029 Task Category: Health Service Level: Error Keywords: Classic User: N/A Computer: ########## Description: The Health Service was detected that the private key for secure data processing has been removed or is invalid. The certificate and key will be regenerated. Log Name: Operations Manager Source: HealthService Date: 17.03.2011 17:26:55 Event ID: 7022 Task Category: Health Service Level: Error Keywords: Classic User: N/A Computer: ########## Description: The Health Service has downloaded secure configuration for management group ##########, and processing the configuration failed with error code Cannot find the certificate and private key for decryption.(0x8009200B). Log Name: Operations Manager Source: HealthService Date: 17.03.2011 17:26:55 Event ID: 1220 Task Category: Health Service Level: Error Keywords: Classic User: N/A Computer: ########## Description: Received configuration cannot be processed. Management group "##########". The error is Cannot find the certificate and private key for decryption.(0x8009200B). When we tried to restart the service, the following event occured: Log Name: Operations Manager Source: OpsMgr Connector Date: 23.03.2011 09:07:33 Event ID: 21021 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ########## Description: No certificate could be loaded or created. This Health Service will not be able to communicate with other health services. Look for previous events in the event log for more detail. We also tried to assign a new HTTPS certificate to MSSQL Reporting services, which raised the following events: Log Name: System Source: Schannel Date: 23.03.2011 10:19:09 Event ID: 36870 Task Category: None Level: Error Keywords: ClassicNo related pages.
There are many reasons why Error Code 36870 happen, including having malware, spyware, or programs not installing properly. You can have all kinds of system conflicts, registry errors, and Active X errors. Reimage specializes in Windows repair. It scans and diagnoses, then repairs, your damaged PC with technology that not only fixes your Windows Operating System, but also reverses the damage already done with a full database of replacement files.
A FREE Scan (approx. 5 minutes) into your PC's Windows Operating System detects problems divided into 3 categories - Hardware, Security and Stability. At the end of the scan, you can review your PC's Hardware, Security and Stability in comparison with a worldwide average. You can review a summary of the problems detected during your scan. Will Reimage fix my Error Code 36870 problem? There's no way to tell without running the program. The state of people's computers varies wildly, depending on the different specs and software they're running, so even if reimage could fix Error Code 36870 on one machine doesn't necessarily mean it will fix it on all machines. Thankfully it only takes minutes to run a scan and see what issues Reimage can detect and fix.
A Windows error is an error that happens when an unexpected condition occurs or when a desired operation has failed. When you have an error in Windows, it may be critical and cause your programs to freeze and crash or it may be seemingly harmless yet annoying.
A stop error screen or bug check screen, commonly called a blue screen of death (also known as a BSoD, bluescreen), is caused by a fatal system error and is the error screen displayed by the Microsoft Windows family of operating systems upon encountering a critical error, of a non-recoverable nature, that causes the system to "crash".
One of the biggest causes of DLL's becoming corrupt/damaged is the practice of constantly installing and uninstalling programs. This often means that DLL's will get overwritten by newer versions when a new program is installed, for example. This causes problems for those applications and programs that still need the old version to operate. Thus, the program begins to malfunction and crash.
Computer hanging or freezing occurs when either a program or the whole system ceases to respond to inputs. In the most commonly encountered scenario, a program freezes and all windows belonging to the frozen program become static. Almost always, the only way to recover from a system freeze is to reboot the machine, usually by power cycling with an on/off or reset button.
Once your computer has been infected with a virus, it's no longer the same. After removing it with your anti-virus software, you're often left with lingering side-effects. Technically, your computer might no longer be infected, but that doesn't mean it's error-free. Even simply removing a virus can actually harm your system.
Reimage repairs and replaces all critical Windows system files needed to run and restart correctly, without harming your user data. Reimage also restores compromised system settings and registry values to their default Microsoft settings. You may always return your system to its pre-repair condition.
Reimage patented technology, is the only PC Repair program of its kind that actually reverses the damage done to your operating system. The online database is comprised of over 25,000,000 updated essential components that will replace any damaged or missing file on a Windows operating system with a healthy version of the file so that your PC's performance, stability & security will be restored and even improve. The repair will deactivate then quarantine all Malware found then remove virus damage. All System Files, DLLs, and Registry Keys that have been corrupted or damaged will be replaced with new healthy files from our continuously updated online database.
Downloads in July: 361,927
Download Size: 746KB
To Fix (Error Code 36870) you need to follow the steps below:
Download Error Code 36870 Repair Tool
Click the "Scan" button
Click 'Fix All' and the repair is complete.
Windows Operating Systems:
Compatible with Windows XP, Vista, Windows 7 (32 and 64 bit), Windows 8 & 8.1 (32 and 64 bit), Windows 10 (32/64 bit).