4 Replies Latest reply on Jun 10, 2019 8:56 AM by Malusi Khoza

    TSCO Moviri SCOM extractor failing

    Malusi Khoza
      Share:|

      Hi all,

      just want to check if anyone can assist with the below issue:

       

      Our database systems are configured to only use Windows authentication. We have an integration user created with Win Authentication.

       

      • Moviri Integrator Version 6.2.00 for TrueSight Capacity Optimization - Microsoft SCOM
      • TSCO 11.5
      • SCOM - 2016
      • SQL Server 2016

       

      TSCO ETL Log:

      BCO_ETL_ERR011: Detected an abnormal ETL termination. Reason: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'XXXXXX'. ClientConnectionId:7dba0969-dcd6-4e36-9b31-fbec06eea03b

      at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:217)
      at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:251)
      at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:81)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:3077)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:2360)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$100(SQLServerConnection.java:43)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:2346)
      at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:6276)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1793)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1404)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1068)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:904)
      at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:451)
      at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1014)
      at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
      at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
      at com.neptuny.cpit.etl.DBInterface.connect(DBInterface.java:225)
      at ETL.extractor.SCOMDWME.connect(SCOMDWME.java:244)
      at com.neptuny.cpit.etl.Engine.start(Engine.java:133)
      at com.neptuny.cpit.etl.ETLrun.main(ETLrun.java:167)

       

      SQL Server Log:

      Login failed for user 'XXXXXX'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: XXXXXXXX]

       

      User is setup to use Windows authentication but looks like on task execution; it's picked up as SQL authentication instead. We've doubled checked the user properties. Through SQL Server Management studio; the use can access the data base with Windows authentication, no issues.

      The extractor supports both SQL and Win authentication.

       

      Any guidance would be appreciated.

        • 1. Re: TSCO Moviri SCOM extractor failing
          Maria Riccelli

          Andrea Gallo can you please take a quick look to this thread? I think Malusi should be opening a support case.

          Thanks,

          MB

          • 2. Re: TSCO Moviri SCOM extractor failing
            Andrea Gallo

            Hello Malusi,

            to make sure that the Moviri Integrator for SCOM (as well as any other Database extractor to a Microsoft SQL Server Database) uses the Windows Authentication, please configure the "Connection Parameters" section as the following:

             

            • Datasource type: Custom datasource
            • Database type: Other database
            • Database User: <USER> (without the user domain)
            • Database Password: <Password>
            • JDBC Driver: net.sourceforge.jtds.jdbc.Driver
            • JDBC URL: jdbc:jtds:sqlserver://<HOSTNAME>:<PORT>;instance=<INSTANCENAME>;domain=<DOMAIN>

             

            For example, if your user is [domain]\[user], please configure as the following

             

            • Database User: [user]
            • JDBC URL: jdbc:jtds:sqlserver://<HOSTNAME>:<PORT>;instance=<INSTANCENAME>;domain=[domain]

             

            More information about the jTDS JDBC url are available here jTDS JDBC Driver http://jtds.sourceforge.net/faq.html#urlFormat

            Depending on you environment configuration, you may have to add additional properties to support the Windows Authentication (e.g. useNTLMv2=true).

             

            I am at your disposal for any additional question or information. Please open a ticket to BMC Support or to email moviri_integrations@moviri.com if you would like to continue this conversation outside the context of the BMC communities.

             

            Thanks!

            Best Regards

            Andrea

            1 of 1 people found this helpful
            • 3. Re: TSCO Moviri SCOM extractor failing
              Malusi Khoza

              Thank you Andrea,

              I will test setup the integration according to your suggestions and provide feedback.

               

              Regards

              • 4. Re: TSCO Moviri SCOM extractor failing
                Malusi Khoza

                Thank you again Andrea for the guidance, it was very helpful.

                I used this option and had to leave the "Database name" blank otherwise it was crashing with the error:

                 

                BCO_ETL_ERR011: Detected an abnormal ETL termination. Reason: java.sql.SQLException: Server XXXXXXX.domain has no instance named INSTANCE NAME.

                at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(http://ConnectionJDBC2.java:281)
                at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(http://ConnectionJDBC3.java:50)
                at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
                at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
                at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
                at com.neptuny.cpit.etl.DBInterface.connect(DBInterface.java:225)
                at ETL.extractor.SCOMDWME.connect(SCOMDWME.java:244)
                at com.neptuny.cpit.etl.Engine.start(Engine.java:133)
                at com.neptuny.cpit.etl.ETLrun.main(ETLrun.java:167)