Batch utility fails with U00003590 ... Login failed for user 'USER_NAME'

Products

• CA Automic Workload Automation - Automation Engine
• Automic SaaS
• CA Automic One Automation

Issue/Introduction

When running a utility (like revision report) in batch mode from the command line, the following error appears in the log:

20240918/180218.485 - U00029112 UCUDB - Length of the DB-History area: 100
20240918/180218.563 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 13a6020  DB-HDBC: 13a6100
20240918/180218.563 - U00003591 UCUDB - DB error info: OPC: 'SQLDriverConnect' Return code: 'ERROR'
20240918/180218.563 - U00003592 UCUDB - Status: '28000' Native error: '18456' Msg: 'Login failed for user 'USER_NAME'.'
20240918/180218.579 - U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR   ', '28000', 'Login failed for user 'USER_NAME'.'
20240918/180218.579 - U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR   ', '28000', 'Login failed for user 'USER_NAME'.'

Version 24 will show a slightly different message:

20241007/163819.772 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 324706e0  DB-HDBC: 32470e10
20241007/163819.772 - U00003591 UCUDB - DB error info: OPC: 'SQLDriverConnectUtf8' Return code: 'ERROR'
20241007/163819.772 - U00003592 UCUDB - Status: '28000' Native error: '18456' Msg: 'Login failed for user '[username]'.'
20241007/163819.772 - U00003590 UCUDB - DB error: 'SQLDriverConnectUtf8', 'ERROR   ', '28000', 'Login failed for user '[username]'.'
20241007/163819.772 - U00003590 UCUDB - DB error: 'SQLDriverConnectUtf8', 'ERROR   ', '28000', 'Login failed for user '[username]'.'
20241007/163819.772 - U00003590 UCUDB - DB error: 'SQLDriverConnectUtf8', 'ERROR   ', '28000', 'Login failed for user '[username]'.'

Environment

Version: Any

Resolution

This error message:

U00003590 UCUDB - DB error: 'SQLDriverConnect', 'ERROR   ', '28000', 'Login failed for user 'USER_NAME'.'

is pointing to an issue with the user that's being used in the ini file's sqlDriverConnect= setting.  This could be that the password set in the PWD= parameter is incorrect or perhaps the System ODBC connection does not exist on the server where the Revision report is being run.  

Please re-enter the password in plain text into the the PWD= parameter within the sqlDriverConnect= setting in the utility ini file and see if that resolves this issue:

sqlDriverConnect=ODBCVAR=SNNNNNRN,DSN=ODBC_CONNECTION_NAME;UID=USER_NAME;PWD=???

Note: If the password is encrypted using the ucybcryp tool, the first two characters may need to have dashes input manually

If not, check with the DBA that the System ODBC connection from the sqlDriverConnect exists on the same server where the utility is being run and that the test connection on it works successfully.  A DBA can also look to see if there is anything in the SQL Server logs that could show if an incorrect login is happening.