Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only
  • 1.  Upgrading JDBC Driver 12.6.1

    Posted 5 days ago

    Has anyone ran into issues using 12.6.1 JDBC Driver on Cognos 11.2.4. 

    After upgrading the driver, we are seeing the following error:

    XQE-DS-0006 Unable to logon to the data source."encrypt" property is set to "true" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: 

    The file 'mssql-jdbc-12.6.1.jre8' was added to the driver folder. 

    We added the file 'mssql-jdbc_auth-12.6.1.x64.dll' to the bin, bin64, and driver folders. 

    We also modified the JDBC connection parameter to: sslProtocol=TLSv1.2;encrypt=false;trustServerCertificate=true

    It does not seem like the connection string parameters are being utilized. Has anyone else experienced this or received this error before? 



    ------------------------------
    E. Johnson
    ------------------------------


  • 2.  RE: Upgrading JDBC Driver 12.6.1

    Posted 5 days ago

    Hi Elisabeth,

    This JDBC driver (v12.6.1) is supported for v11.2.4 FP4 (and later, build 11.2.4-2406211735 and older).

    You also need to make sure you removed previous drivers from <Cognos_Location>/drivers location.

    Best regards,



    ------------------------------
    Patrick Neveu
    BSL Consulting
    IBM Champion
    ------------------------------



  • 3.  RE: Upgrading JDBC Driver 12.6.1

    Posted 5 days ago

    I can confirm we are running 11.2.4-2406211735. 

    The previous driver was removed. 



    ------------------------------
    E. Johnson
    ------------------------------



  • 4.  RE: Upgrading JDBC Driver 12.6.1

    Posted 5 days ago

    Hi Elizabeth,

    For the JDBC Connection Parameters (from the properties of the data source connection in Cognos Admin), you can try solely:

    encrypt=false

    For more info about changes introduced by Microsoft and server certificates, please check out:

    https://www.ibm.com/support/pages/changes-introduced-microsoft-starting-jdbc-driver-version-102

    Thanks and let me know how it goes.



    ------------------------------
    Steve Caputo
    ------------------------------



  • 5.  RE: Upgrading JDBC Driver 12.6.1

    Posted 4 days ago

    Hi Elizabeth!

    We're running the MS JDBC Driver 12.8.1 in our Cognos 11.2.4 FP5 environment without issue.

    I'm assuming you're using SQL Server for your content store?  In which case the _auth dll needs to go in your:

    C:\Program Files\Microsoft SQL Server\MSSQLxx.MSSQLSERVER\MSSQL\Binn folder

    The xx in the path above depends on your version of SQL Server.  We were running SQL 2016 so it was MSSQL13, but now we're running SQL 2022 so it's MSSQL16.

    Then in your Cognos configuration, for each connection to SQL Server (we have 3 - the audit db, content store and notifications) in the database Resource Properties tab, in Advanced properties you need:

     Name                           Value
    trustServerCertificate    true

    Finally, if you're using auditing and have the Audit database in SQL Server, in Administration -> Configuration -> Data Source Connections, on the JDBC tab you need:

    trustServerCertificate=true  down in the JDBC Connection Parameters:

    Hopefully this all helps!

    Regards,

    Wayne



    ------------------------------
    Wayne Westlake
    ------------------------------



  • 6.  RE: Upgrading JDBC Driver 12.6.1

    Posted 4 days ago

    We forgot to apply the connection string parameters to the second data source connection. After added them to the other data source connection, we were able to use the driver without issue. 



    ------------------------------
    E. Johnson
    ------------------------------



  • 7.  RE: Upgrading JDBC Driver 12.6.1

    Posted 4 days ago

    Our Cognos environment has two separate data source connections. We forgot to add the connection string to the second connection. The driver is working as expected now. 



    ------------------------------
    E. Johnson
    ------------------------------