ADDM: Microsoft SQL Server credentials fail with error: The user is not associated with a trusted SQL Server connection

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Discovery


    COMPONENT:

    BMC Atrium Discovery and Dependency Mapping


    APPLIES TO:

    BMC Atrium Discovery and Dependency Mapping



    PROBLEM:

     

    The Microsoft SQL Server SI is created with Port and Instance attributes, however the extended database discovery fails with:

    Error: SQL Provider: Unable to open a connection to the database: Login failed for user 'xxxxx"'. The user is not associated with a trusted SQL Server connection

    A credential test of the Microsoft SQL Server credential fails with:

    SQL Provider: Unable to open a connection to the database: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

    The following driver is being used: Microsoft SQL Server (jTDS Driver 1.2.2)
     

     


    SOLUTION:

     

    Legacy ID:KA346284

      

    How to set up Microsoft SQL Server credentials?

    Microsoft SQL Server credentials (Using sa username/password)
    =====================================================

    - In these cases, make sure that the SQL Server is configured to mixed mode (to support both Windows authentication & SQL Server authentication)

    - If set properly, then this works most of the time.

    - Failures are noticed if customer specification can only support Windows Authentication:

    Setting up Microsoft SQL Server credentials (Windows Authentication Mode):
    ==============================================================

    In Discovery -> Discovery Credentials -> Microsoft SQL Server -> (credential name) -> Credential Details:

    1) Use jTDS driver
    2) In DB credential use Windows account (eg Administrator/T1deway!2)
    3) In Additional JDBC Parameters Add "domain=BMCLAB" - (Compare it with NIS/Windows Domain value from the Host View)

      

    Test the DB Credential test with the above configuration. This should fix the problem.

    If the problem persists, add the following entry to "Additional JDBC Parameters" in the second line:

    useNTLMv2=true

    If still having a problem, please send the tw_svc_integrations_sql.log to Support for further diagnosis.
     

     


    Article Number:

    000085751


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles