title: Can no longer call ASMX service from Classic ASP after TLS 1.2
body: <p>We have a web site that is primarily Webforms, but still contains a body of pages written in Classic ASP, sharing a directory structure. Those classic pages use the asmx services on the asp.net side to pull connection information.  This has been working adequately for years, until recently with our upgrade to TLS 1.2.  Now we get the following error on the <strong>xmlhttp.send DataToSend</strong> statement.</p>
  
  <p>msxml3.dll error '80072efe' 
  The connection with the server was terminated abnormally </p>
  
  <p>My research says that this is the result of calling one Classic page from another Classic page when they occupy the same process or application pool.   But I am calling an ASP.NET ASMX Service, which is a different process and pool...right?</p>
  
  <p>Short of rewriting the classic pages, how do I fix this issue?</p>
  
  <blockquote>
    <p>.NET Framework 4.5.2</p>
    
    <p>IIS 7.5.7600.16385</p>
    
    <p>Windows Server 2008 R2</p>
  </blockquote>
  
  <pre><code>Dim xmlhttp
  Dim DataToSend
  DataToSend="OrigId=XXXXX&amp;OrigPassword=YYYYYY&amp;ConnectionName=" &amp; pConnectionName
  Dim postUrl
  postUrl = "https://" &amp; Request.ServerVariables("server_name") &amp; "/SSLWebServices/ConnectionLookUp.asmx/GetConnectionData"
  Set xmlhttp = server.Createobject("MSXML2.serverXMLHTTP")
  xmlhttp.setOption 2,13056
  xmlhttp.Open "POST",postUrl,false
  xmlhttp.setRequestHeader "Content-Type","application/x-www-form-urlencoded"
  
  xmlhttp.send DataToSend
  
  dim strResponse
  strResponse = xmlhttp.responseText
  </code></pre>