The Cognos server is using SQL 2014
The data is on a serpent sever and the customer updated the data server to SQL 2017( I know Cognos does not support however there were other reasons that the user HAD to use this version
Now the regular connection is working
However the JDBC connection fails, Initially, I had several issues with JAVA but they were all sorted and I am using Java 7
I also followed the next solutions
https://www.ibm.com/support/pages/dpr-err-2002-error-when-testing-dynamic-query-mode-connection-cognos-administration
and
http://www-01.ibm.com/support/docview.wss?uid=swg21636329
and
http://www-01.ibm.com/support/docview.wss?uid=swg21340020
So "Initial JVM heap size for the query service (MB)"
"JVM heap size limit for the query service (MB)" have the correct values
And the Queue time limit of report service in seconds has been doubled and tripled
I also eliminated the option of a second instance
However, I still get the error message:
DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit.
Any ideas about what can be done?
Quote from: barmorris on 26 Nov 2019 03:08:58 PM
The Cognos server is using SQL 2014
The data is on a serpent sever and the customer updated the data server to SQL 2017( I know Cognos does not support however there were other reasons that the user HAD to use this version
Now the regular connection is working
However the JDBC connection fails, Initially, I had several issues with JAVA but they were all sorted and I am using Java 7
I also followed the next solutions
https://www.ibm.com/support/pages/dpr-err-2002-error-when-testing-dynamic-query-mode-connection-cognos-administration
and
http://www-01.ibm.com/support/docview.wss?uid=swg21636329
and
http://www-01.ibm.com/support/docview.wss?uid=swg21340020
So "Initial JVM heap size for the query service (MB)"
"JVM heap size limit for the query service (MB)" have the correct values
And the Queue time limit of report service in seconds has been doubled and tripled
I also eliminated the option of a second instance
However, I still get the error message:
DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit.
Any ideas about what can be done?
Hi,
So you had no issues when using SQL Server 2014 but the change to SQL Server 2017 has introduced this issue? Have you checked that the Microsoft JDBC jar file you are using on the Cognos server for your SQL Server connection is compatible with SQL Server 2017? What specific jar file are you using currently?
You're correct that SQL Server 2017 isn't a supported data source in Cognos 10. The last builds of 10.2.2 only support up to SQL Server 2016. You might find it simply won't work.
Good luck!
MF.
I would try JDBC driver 6.2.
It is supposed to work with both 2014 and 2017 SQL Servers:
mssql-jdbc-6.2.2.jre8.jar
mssql-jdbc-6.2.2.jre7.jar
See MS SQL version compatibility:
https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-ver15 (https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-ver15)