Current Revision posted to Content Management Wiki by Nilay Jadwani on 5/17/2019 1:37:55 PM
Before moving to TLS 1.2 please make sure your SQL server supports TLS 1.2 protocol and perform upgrade if needed:
https://support.microsoft.com/en-us/help/3135244/tls-1.2-support-for-microsoft-sql-server
Please make sure "SQL server Native Client 11.0" driver is available in "ODBC Data Source Administrator".
- Load certificate on the server that the clients will be connecting to. This would need to be the server that is in your ProjectWise Network Control Panel.
- Modify the dmskrnl.cfg to enable encryption and start PW Integration server in secure mode
- Uncomment SecureConnection=1
- Enter the cert name here: SecureCertificateCommonName=CNfromCertificate)
- Download this application: https://www.nartac.com/Products/IISCrypto/Download
- Once installed Run IIS Crypto GUI version2.0, and select TLS 1.2 and make sure TLS 1.0 and TLS 1.1 are unselected (for both client and server sections).
- Hit apply
- Reboot the server this task was performed on.
- Re-create your ODBC connection using "SQL server Native Client 11.0" driver if it's an old driver or you will receive database communication error.
Note:
- The above information applies to the CONNECT Edition only. Select Series versions require TLS1.0
- Direct connections using OleDb does not still support TLS 1.2. So all connections need to be changed to ODBC. That means if Orchestration Framework was earlier connected with Direct Connection, Orch. Service might not run. Change Orch. Framework connection to ODBC in dbsetup.exe and re-run your Orch. service