none
possile legacy bug RRS feed

  • Question

  • Using the following lines of code in ASP Classic:

     

    Set objRequest = server.createobject("MSXML2.XMLHTTP.6.0")

    With objRequest

    .open "GET", "https://www.khyky.org.gr/doctorapi/", False

    .setRequestHeader "Authorization", "Basic " & Base64Encode

    .send

    'End With

     

    I get the following results:

     

    1. On a pc with Win10 and IIS10 the connection can be easily established and I consume the web service.
    2. On a server pc with win2008R2 or win2012 with IIS 7.5 or IIS8 , respectively, I receive the following error, which can be seen at the attached Failed Request Tracing Log.

     

    All the certificates needed for this connection are correctly  installed, yet the following error takes place : «msxml6.dll error '80004004' Operation aborted»

     

    Now If I change this line of code

    Set objRequest = server.createobject("MSXML2.XMLHTTP.6.0")

    with this one

    Set objRequest = server.createobject("ServerMSXML2.XMLHTTP.6.0")

     

    I receive a different message and the connection cannot be established with any of the above 3 system setups that I’ve described. The error says : «msxml6.dll error ‘80072f0c’ A certificate is required to complete client authentication».

     

    Any advice would be highly appreciated, since I think I might have come across a legacy bug.

     



    Alexander Skordos Network Engineer Gold Certified Professional Geniusnet SA - Hellas

    Tuesday, June 20, 2017 7:19 AM

All replies

  • Hi Alexandros,

    This forum discusses and asks questions about .NET Framework Base Classes, Since your issue is more related to classic asp, I would suggest that you could post your issue on classic asp forum for suitable support.

    http://forums.devshed.com/asp-programming-51/

    Thanks for your understanding.

    Best regards,

    Cole Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, June 20, 2017 9:26 AM