Cannot connect using https / msxml3.dll error '80072f8f' A security error occurred

Hello Everyone,

So I am a little perplexed.  I have an ASP site running on Win2003 / IIS6.  The ASP site makes an https connection to a WebMethods middle tier to transfer data.  The code has been working for over a year and over the weekend something happened and how I am getting an error.  I wrote an diagnostic program to see what was going on and I seem to be getting the following error:

msxml3.dll error '80072f8f'
A security error occurred

Can anyone please tell me why I am getting this error and What I need to do to fix it?  The server is managed by a third party, I am just develop the code. the code seems to work when I use http but not https.  So its definitely something with the exchange of the digital certificates.

Thanks in advance for your help.

Who is Participating?
KozelaAuthor Commented:
Ok.  So here is the story.  Apparently, Windows Update KB980436 (MS10-049) was installed and it changed the was SSL/TLS works.  As a result, my application stoped working.  The Update should have left the server in compatibility mode, so it should have been transparent to my application.  However, it was not.  To get around the problem, we had the add the following keys to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL with a DWORD value of 1


Adding these keys and a DWORD value of 1 makes the application go into compatibility mode.  Addind a DWORD value of 0 makes it go into Strict Mode.

Thanks for all the help.
KozelaAuthor Commented:

Thank you for the feedback.  The application has been working for over a year.  I am also using MSXML2.ServerHTTP.  So I am not sure this is applicable.

How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

It could be possible the error arrived due recently windows update on the Server. you should check the url
KozelaAuthor Commented:
The URL is correct.  Any other ideas?
Do you specify the port number in URL? Any chances that it was changed recently?
KozelaAuthor Commented:
The URL does have the port number but has not changed.  Thanks.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.