Not a question - thought to submit a possible solution for people.
From what I can tell this error is thrown by .NET in three instances.
Your code is calling a web service that is referenced HTTPS but there isn't a certificate.
Your code is calling a web service that is referenced HTTPS but uses a certificate that your code client doesn't trust.
Your code is calling a web service that is referenced HTTPS but the server name on the certificate does not match the web service server.
I can't help with #1 except to ask why you're referencing HTTPS on a server that doesn't seem to need it (i.e. no cert).
I can't help with #3. It'd have to be fixed at the source (certificate has to match server name, common problem when using CNAMES or alternate domains).
#2, I found some funky behavior on Server 2008 R2 and thought to share my findings.
Previously, XP/2000/2003/NT world, and ma ...
Go to the complete details ...