IBM Support

PI21743: UNABLE TO CONNECT TO RESULTS DATABASE USING JTDS AND NATIVE LIBRARY

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Use JTDS with native library to a MS SQL database from AS
    Physical View and hence validate the connection details.
    Now use those same details for the project database connection
    and test the connection.  This issue occurs:
    [CRRIT4226E] The following error occurred in connecting to the
    database:I/O Error: SSO Failed: Native SSPI library not loaded.
    Check the java.library.path system property.
    (Note that the native library is on the system path, and we have
    validated this from AS Physical View.)
    

Local fix

  • Use username and password credentials to avoid use of native
    library when connecting to MS SQL results database.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of Rational Integration Tester and Microsoft SQL   *
    * Server                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If a user attempts to use the jTDS driver to connect to      *
    * Microsoft SQL Server for both the project Results Database   *
    * AND a physical database in the project AND they use the      *
    * single-sign-on (SSO) options, then Rational Integration      *
    * Tester may fail to connect to one or both of the databases.  *
    * Typically a user will see the following error at some point  *
    * during this process:                                         *
    *                                                              *
    * [CRRIT4226E] The following error occurred in connecting to   *
    * the database:I/O Error: SSO Failed: Native SSPI library not  *
    * loaded.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The problem was caused by load conflict across the two databases
    when the native Windows dll was loaded to manage the single
    sign-on process. Rational Integration Tester has been modified
    at version 8.6.0.2 to remove this conflict and users can now use
    jTDS/SSO for a Results Database and a database for testing at
    the same time in the same project.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI21743

  • Reported component name

    RATL INTEGRA TE

  • Reported component ID

    5725G79IT

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-10

  • Closed date

    2015-01-02

  • Last modified date

    2015-01-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RATL INTEGRA TE

  • Fixed component ID

    5725G79IT

Applicable component levels

  • R800 PSN

       UP

  • R801 PSN

       UP

  • R850 PSN

       UP

  • R851 PSN

       UP

  • R860 PSY

       UP



Document information

More support for: Rational Test Workbench

Software version: 8.6

Reference #: PI21743

Modified date: 02 January 2015