The SQL service instances that are not working are connected to a SQL 2012 server.
Adding a test SQL service instance against the same SQL 2016 server as the K2 database works. (provider: SSL Provider, error: 0 - The client and server cannot communicate, because they do not possess a common algorithm.) Symptoms IssueĪfter migrating K2 4.7 to a new Windows 2016 server and upgrading to K2 5.3, SQL SmartObjects execution started to fail with:Ī connection was successfully established with the server, but then an error occurred during the login process. This article is not considered official documentation for K2 software and is provided "as is" with no warranties. The content may include typographical errors and may be revised at any time without notice. This article was created in response to a support issue logged with K2. K2 blackpearl Cumulative Updates and Fixpacks. K2 Five Cumulative Updates and Fixpacks. In System variables select path and click EditĪdd the SQL driver path to beginning of the path like %SystemRoot%\system32 %SystemRoot% %SystemRoot%\System32\Wbem %SYSTEMROOT%\System32\WindowsPowerShell\v1. Go to control panel – system – advance system settingsĬlick on Advance tab – click on Environment Variables You may need to update the PATH on your windows server, to have the new driver folder first in path – so it is used by Cognos Planning. You can check the version of SQL driver you have, by going to the DOS prompt, and enter commando: You may need to reboot the servers to make the change take affect.Īnd if that does not help – install a later SQL driver on you cognos planning server, download from Microsoft and install. If that does not help then add this value on the SQL server in registry TCP/IP Registry Values That Harden the TCP/IP Stack ( Windows 2003 Servers ) On both your SQL server and Cognos Planning server update the registry with this values, to turn off TLS 1.2 usage: Best practice is to set the cognos planning services system path to a separate folder, then can you easy find the log files for cognos planning.Įrror = SSL Provider: An existing connection was forcibly closed by the remote host.Įrror = Client unable to establish connection The cognos planning publish process stop at different BCP jobs, and you can find the errors in the -out file. It can work, but most of the time the publish fail. When doing a large publish from inside Contributor Administration Console (CAC) to a SQL 2017 server an a different computer, you get a error at random times.
0 kommentar(er)
