search cancel

JWP won't start | U00003590 UCUDB ... 'S0001', 'Login failed for user

book

Article ID: 201654

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

using windows authentication for sql server, we are unable to start the JWP's in service dialogue of automation engine.

More info on error from JWP log:

20201016/140455.920 - 32     U00003611 DB OPEN executed. Return Code = '18456'
20201016/140455.920 - 32     U00003590 UCUDB - DB error: 'S0001', 'Login failed for user '[DOMAIN]\[USERNAME]'. ClientConnectionId:3bec2d86-e1e4-49ac-81aa-d6e645f7f55a', '18456', 'com.microsoft.sqlserver.jdbc.SQLServerException'
20201016/140455.920 - 32     U00032031 Error when connecting to Database

Cause

This was caused by the incorrect user starting the JWP process or the fact that the necessary mssql-jdbc_auth-*.dll associated to the JDBC driver being used was missing.

Environment

Release : 12.x and 21.x

Component : AUTOMATION ENGINE

Database: MS SQL Server with IntegratedSecurity=true (Windows authentication) 

Resolution

Logging directly into the server that housed the JWPs as the user who connects to the database and starting the JWP from command line allowed the JWP to start successfully.  This showed that the incorrect user was being used to start the process from the servicemanager.  Two options:

1) Start the servicemanager as the user who logs into the database

2) In the ServiceManagerDialog, right-click the JWP, go to Properties, and put in the username, domain, and password for the "log on as" information.

 

In another context, the issue was due to the fact that the library mssql-jdbc_auth-10.2.0.x64.dll associated to mssql-jdbc-10.2.0.jre8.jar had not been copied to the <aeserver>\bin\lib folder.

This is explained in the documentation here:

Note: When you install the JDBC driver and have to use Windows authentication, you must also copy the sqljdbc_auth.dll file to the BIN directory of the Automation Engine.