This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 40%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Hi,
I have a console application which connects to docuemntum (OpenText D2) system using DFS Dlls to run queries and get data. The application runs fine in our olders VMs (OS Win Server 2012 R2).
However the same application does not run on a recently created VM (OS Windows Server 2019). I am getting an error
"System.ServiceModel.Security.SecurityNegotiationException: Could not establish secure channel for SSL/TLS with authority '<documentum end point url>'. ---> System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel."
I have downloaded the certificate by opening the documentum end point url on browser and installed it on Trusted Root Store. I have also tried completely disabling the certificate from code like below.
ServicePointManager.ServerCertificateValidationCallback = new RemoteCertificateValidationCallback(OnValidateCertificate);
ServicePointManager.Expect100Continue = true;
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls
| SecurityProtocolType.Tls11
| SecurityProtocolType.Tls12
| SecurityProtocolType.Ssl3;
Any idea what could be going wrong. Is it something at OS level that i need to check, because as I mentioned earlier the app is working in Server 2012 but not in Server 2019.
Please help!!
Br
Sagar
A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.
SSL3 is no longer supported and should be disabled on Server 2019. You need to use tls 1.2 or 1.1
Try changing code to
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls
| SecurityProtocolType.Tls11
| SecurityProtocolType.Tls12;
You of course need to make sure TLS 1.1 or 1.2 is enabled on <documentum end point url>
HI @Ken Tucker
Thanks for your response. Actually I tried all combination of code and nothing is working. Strange thing is that the same code works on Server 2012 machine without even using any TLS in the code. DO you think is it something related to OS?
Br
Sagar
Couple of things come to mind. If you can I would use an ssl checker on the domain and see what it says. Maybe it will give you some suggestions. As for the server 2012 are you sure it has been patched for the poodle and heartbleed ssl vulnerabilities?
Yes Server 2012 is patched with latest updates. One thing I noticed is that if I open the URL in IE 11 it straight away denies that.. but opens in Chrome and Edge. This is strange for me.