Cognos Controller

 View Only
  • 1.  MS SQL Server Developer Edition

    Posted Thu July 09, 2020 03:55 PM

    I am trying to install 10.4.2 controller and while configuring the content store on a SQL 2016 Developer edition, I get the Content Manager connection fail error. The error is

    [Content Manager database connection]
    [ ERROR ] The database connection failed.
    [ ERROR ] Content Manager is unable to connect to the content store. Verify that the database connection properties in the configuration tool are correct and that when you test the connection, the test is successful.

    I am able to telnet to the server and so the communication is not a problem. Does anyone know if this is a known issue with developer edition or is there something else that I have to do.

    The Cognos Analytics bundle release is 11.0.13 and I have also copied the correct jar files also to the drivers folder. I have searched all the knowledge base articles also but could not find anything linked to this and all other solutions. 

    Thank you.

    Kamlesh Lakhiani


  • 2.  RE: MS SQL Server Developer Edition

    IBM Champion
    Posted Fri July 17, 2020 09:34 AM
    Hi Kamlesh,

    I have seen this kind of behaviour before with SQL Server. It is usually that the TCP-IP protocol is disabled on the SQL Server Service.

    To enable TCPIP follow the steps below:
    1. Open SQL Server Configuration Manager
    2. Expand "SQL Server Network Configuration" and click on "Protocols for MSSQLSERVER"
    3. Right click on "TCP/IP" and choose "Enable"
    4. Click "OK" on the Warning that the service will have to be restarted
    5. Click on "SQL Server Services"
    6. Right click on "SQL Server (MSSQLSERVER) and choose "Restart"

    These were the steps for SQL Server 2014 but I think it should be identical with 2016. To test it simply test your Content Store connection.

    Another tip I have from a recent install of 10.4.2 for me I forgot to add the SQL Server JDBC Authentication jar file to the bin64 directory and I was using a SQL Server Windows Authentication as my Content Store type. Took me a while to figure that one out.


    Andrew Copeland

  • 3.  RE: MS SQL Server Developer Edition

    Posted Thu September 10, 2020 03:09 AM
    sql 2016 could also be enforcing a TLS 1.2 connection, that you may need to work around.