TLS 1.0 & 1.1 disable procedure for OMWV (DVWeb) 11.5
search cancel

TLS 1.0 & 1.1 disable procedure for OMWV (DVWeb) 11.5


Article ID: 113343


Updated On:


Output Management Document Viewer Output Management Web Viewer


We have a Windows 2008 R2 Enterprise SP1 Server running SQL Server 2008 R2. Our security team disabled TLS 1.0 and 1.1 on the server and it caused OMWV to fail to display web pages. We were able to back out the change, but due to mandates we must remove these from the server. We do not have HTTPS enabled or bound. It is a straight HTTP delivered web page. How do we properly remove the protocols where OMWV still works? Are there settings in IIS? Are there patches required for SQL?


Component: DVWEB


Not a Web Viewer or even a CA issue. SSL/TLS 1.0/1.1 would not have been introduced by Web Viewer or CCIPC. Customer restored functionality in the environment by turning on FIPS 140-2 compliance in Microsoft. They ran GP updates to enable FIPS and presumes this reset the secure connection for Web Viewer, the Web Viewer AdminTool, and CCIPC. The action appears to have allowed the unsecure connections to succeed. Having proved successful on a Windows 2012 Server, the same change on a Windows 2008 Server was not.
The solution for   was to:
Go to : 
Download the 2008 R2 Client tools. 
Create the new DSN using the new SQL ODBC driver and use it to logon to the Admin tool. Change the DSN there, and bring up Web Viewer!