Maximo

 View Only

  • 1.  Connecting JDBC driver to MSSQL 2019 server

    Posted Fri January 26, 2024 04:00 AM

    Hi everyone, I'm not sure if this is a good group for our problem. I hope that you can help us.

    We have a problem connecting with JDBC driver to MSSQL 2019 server. Tried with many combinations and solutions but always same error. Also tried with SQLJDBC41 driver but same again. Java version is 7. The print screen of our problem. Does anyone have any idea?



    ------------------------------
    Dario Stjepanović
    ------------------------------


  • 2.  RE: Connecting JDBC driver to MSSQL 2019 server

    Posted Mon January 29, 2024 01:37 AM
    Edited by Johann Rumpl Mon January 29, 2024 01:37 AM

    Hi Dario,

    I'm not familiar with Integration composer, but the error message is something I've seen too often in the Maximo space recently.

    The current fix which works (for Maximo 7.6.1.3) can be found here: https://www.ibm.com/support/pages/maximo-asset-management-upgrade-7613-fails-microsoft-sql-server-database-0
    As you can see the idea is to add an "encrypt=false" parameter to the JDBC connect string. If you're lucky enough to have access to the JDBC string it will be worth a try.

    The second option which worked with previous Versions of Maximo down to 6.2 is to update a specific security setting in the Windows Registry of the SQL Server:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\Diffie-Hellman]

    "ServerMinKeyBitLength"=dword:00000800

    Source: https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2016/3174644

    It is not the most elegant and high secure option, but in certain cases we had no other choice.

    Hope this helps



    ------------------------------
    Johann Rumpl
    Maximo Senior Consultant
    EAM Swiss GmbH
    Steinmaur
    Switzerland
    ------------------------------

    Original Message


  • 3.  RE: Connecting JDBC driver to MSSQL 2019 server

    Posted Mon January 29, 2024 03:37 AM

    Dear Johann,

    Thank You for your answer. We will try both options and see if we get lucky.



    ------------------------------
    Dario Stjepanović
    ------------------------------

    Original Message


  • 4.  RE: Connecting JDBC driver to MSSQL 2019 server

    Posted Mon January 29, 2024 04:52 AM

    Hi Dario,

    You're welcome - I forgot to mention that the registry key might be set to 004 or 000 to make it work. If I remember correctly, it also required a Server restart to become effective.

    Cheers

    Johann



    ------------------------------
    Johann Rumpl
    Maximo Senior Consultant
    EAM Swiss GmbH
    Steinmaur
    Switzerland
    ------------------------------

    Original Message


  • 5.  RE: Connecting JDBC driver to MSSQL 2019 server

    Posted Mon January 29, 2024 01:37 PM

    You always want to follow this chart: https://learn.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix?view=sql-server-ver15#sql-version-compatibility

    SQL Server 2019 was not supported by Microsoft until JDBC driver 7.4. Starting with JDBC driver 7, you must be on 1.8 or higher and you are using Java 1.7. You would also need to make sure you update to a newer java version in addition to a newer JDBC driver which may cause issues with integration composer. 

    There's not a great solution here because the product team won't support something the vendor won't support. I think you need to evaluate patching Control Desk and the integration composer. 



    ------------------------------
    Steven Shull
    ------------------------------

    Original Message


  • 6.  RE: Connecting JDBC driver to MSSQL 2019 server

    Posted Tue January 30, 2024 07:13 AM

    Dear Steven,

    Thank You again, You help us with your advice.

    We have upgraded ITIC, Java and JDBC driver. Now everything is fine.

    But, now we have new issue. When we start "Open Existing Mapping" in ITIC we get blank screen, we do not see existing mapping that we already created.
    When we go to "Delete Mapping" we see them all.

    Thank You in advance.


    ------------------------------
    Dario Stjepanović
    ------------------------------

    Original Message


  • 7.  RE: Connecting JDBC driver to MSSQL 2019 server

    Posted Tue January 30, 2024 08:23 AM

    You would need to open a support case. It looks like you might have upgraded the integration composer component without upgrading Control Desk. MAXUPG is showing 7.6.1.0 when it should show 7.6.1.3 when on 7.6.1.5 of Control Desk. Integration Composer is showing 7.6.1.5 which is the latest release. A difference in versions might be a problem. I have only ever used the version of integration composer shipped with my version of Control Desk. And I know there have been a few enhancements made to the integration composer over those releases which might be impacting the operation of the application. 



    ------------------------------
    Steven Shull
    ------------------------------

    Original Message