DB011/DB02 - How to configure the 360Suite database with SQL Server AD Domain account

DB011/DB02 - How to configure the 360Suite database with SQL Server AD Domain account

Symptom

When configuring the database in the Web Platform Administration Console with a AD Domain account for SQL Server, you encounter one of the following errors :
- DB012: Could not find driver
- DB011: This driver is not configured for integrated authentication,

Environment

  • Web Platform
  • Windows
  • Linux
  • SQL Server

Cause

The Web Platform Tomcat service account must be the SQL Service Domain account that accesses the database.
The JTDS driver must be used and the JDBC URL must contain useNTLMv2=true and domain=yourdomain

Resolution

1. Set up the JTDS driver

  1. Download the latest JTDS driver from: https://sourceforge.net/projects/jtds/
  2. Unzip the package and copy-paste the jtds-1.x.x.jar in a location where it will not be deleted.
  3. During the installation (or update, if an existing installation) of the Web Platform, when the wizard prompts to enter the JDBC location for the database, click Browse to select the jtds-1.x.x.jar file.


2. Set up the Tomcat Service Account

  1. Stop the Web Platform Tomcat Service (360Suite4xxx).
  2. Under the Log On properties, click Browse to enter/select the SQL Service AD Domain account.
  3. Click OK.


3. Retrieve the ntlmauth.dll file

  1. The file is available in the JTDS driver package downloaded from: https://sourceforge.net/projects/jtds/ and unzipped.
  2. Depending on the deployment and JVM architecture, select either the 32-bit (x86) or the 64-bit (x64) version. NB: The Java shipped with the Web Platform TOmcat is 64-bit.
Note: the JVM provided as part of the 360 Web Platform installation package is 64-bit. If you're unsure, then use the following steps to find out the version and architecture of Java used.



4. Add the Microsoft DLLs to the Web Platform Java location

  1. Take a copy of the ntlmauth.dll (for x64) and a copy of the mssql-jdbc_auth-9.4.1.x64.dll. The latter file can be obtained by download the MS SQL JDBC driver package
  2. Paste them in the location 360Suitexxx/jdk8[...]/bin

5. Configure the Web Platform database

  1. Access the 360Suite Administration Console: http://<server>[:<port>]/360.suite/admin
  2. In the “Database configuration“ block, configure as follows:
    Database: SQL Server (then, select the appropriate version).
    URL: jdbc:jtds:sqlserver://<server>:<port>/<database_name>;useNTLMv2=true;domain=<domain_name>
    Windows Authentication: Selected.
    Advanced configuration: Not selected.
  3. Click Save.


Keywords

integrate security Azure

Product

Product or Product version

  • 360 Web Platform

Languages

  • English US
  • English UK
  • French

    • Related Articles

    • How to expand Dataprovider SQL Query column in 360Eyes database

      Symptom When running 360Eyes Impact Analysis Reports (such as Report 52), users observe that the SQL query stored in the 360eyes_REPORTS.unx / Eye Document / Dataprovider / Dataprovider Sql Queryfield is incomplete, partial or truncated. This often ...

    • How to configure SQL Server with Windows Authentication

      Symptom When trying to configure a SQL Server database using Windows Authentication as part of the 360eyes database configuration, the following error is returned: "The driver is not configured for integrated authentication". Environment 360Eyes ...

    • How to install 360Eyes on SQL Server on Azure

      Symptom Installing 360Eyes using SQL Server on Azure. Environment 360Eyes SAP BusinessObjects Enterprise XI 3.1 SAP BusinessObjects Business Intelligence 4.0 SAP BusinessObjects Business Intelligence 4.1 SAP BusinessObjects Business Intelligence 4.2 ...

    • DB006 : Could not acquire change log lock

      Symptoms When saving the database configuration in the 360Suite Administration Console, the following error message appears: DB006 : Could not acquire change log lock Cause When the application is upgraded, the database structure is updated (new ...

    • "DB003: No suitable driver found" when configuring 360Suite databases

      Symptoms When configuring 360Suite main database. When configuring 360Eyes database. When trying to create a 360Cast SQL source. When trying to create a 360View SQL Query. In any of these situations, when the database type was selected, the following ...