Network subsystem is unusable ошибка

How to fix the Runtime Code 0x800CCC40 WINSOCK_WSASYSNOTREADY

Symptoms of Code 0x800CCC40 — WINSOCK_WSASYSNOTREADY

Runtime errors happen without warning. The error message can come up the screen anytime Microsoft Outlook is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(For illustrative purposes only)

Causes of WINSOCK_WSASYSNOTREADY — Code 0x800CCC40

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.

OK, I am about to launch myself off a bridge!!

First I had troubles being able to send e-mails with attachments using Synapse and the SMTPSend unit, but eventually got that working and posted this thread in response : http://forum.lazarus.freepascal.org/index.php/topic,27222.msg168096.html#msg168096

Then I wanted to add the ability to FTP connect and send files using an encrypted FTP service like sFTP. To do that, I needed to use a  a Pascal variant of cryptlib (http://cryptlib.sogot.de/crypas.html), add another DLL (cl32.dll), added blcksock unit, and finally SimpleSFTP from http://synapse.ararat.cz/files/contrib/sftp.zip.

After much struggling and fiddling, I eventually got standard FTP to work and although I am yet to test my sFTP connection, I have some compiled code that should hopefully work. I accept that Cryptlib is not officially part of Lazarus and Freepascal so this probably my fault, but it was the only way I could find to use encrypted sFTP with my program (http://forum.lazarus.freepascal.org/index.php/topic,27488.msg169927.html#msg169927) in the lack of any other built in solution.

So, celebrating my progress with FTP and sFTP, I then returned to refine my e-mail issuing code but what do I find? Now that won’t work again, because, as far I can tell, Cryptlib is somehow conflicting with ssl_openssl.

Whenever I get to the login code, the login fails.

...
function TForm1.SendMail(User, Password, MailFrom, MailTo, SMTPHost, SMTPPort: string;
  MailData: string): Boolean;   
 try
    sl.text:=Maildata;
    SMTP.UserName   := User;
    SMTP.Password   := Password;
    SMTP.TargetHost := SMTPHost;
    SMTP.TargetPort := SMTPPort;
    SMTP.AutoTLS    := false;
    SMTP.FullSSL    := true;

Routing through the debugger I find the following:

function TTCPBlockSocket.GetErrorDescEx: string;
begin
  Result := inherited GetErrorDescEx;
  if (FLastError = WSASYSNOTREADY) and (self.SSL.LastError <> 0) then
  begin
    Result := self.SSL.LastErrorDesc; 
      // Result = «Network subsystem is unusable, 10091» and
      // self.SSL.LastErrorDesc = «Received TLS alert message: Decode error»
  end;
end; 

http://wiki.rocrail.net/doku.php?id=win32-socket-error states «WSASYSNOTREADY  10091  : Returned by WSAStartup(), indicating that the network subsystem is unusable».

According to https://www.openssl.org/docs/ssl/SSL_alert_type_string.html, decode error means : A message could not be decoded because some field was out of the specified range or the length of the message was incorrect. This message is always fatal.

Further Googling implies this is an issue with Cryptlib, which I have to use for FTP. If I take it out, e-mail will work but FTP will not.

I have re-downloaded the DLL’s from http://indy.fulgan.com/SSL/ (ssleay32.dll and libeay32.dll)

I am at a loss.