ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

MSSQL job failed due to a login failed for the user

book

Article ID: 41337

calendar_today

Updated On:

Products

DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Issue: 

The MSSQL_JOB job was defined with the USER parameter in order to override the value set in the <database_name>.properties file.

Upon the job submitting, the error "Login failed for user" was return, however the same user/password defined in the <>.properties file allowed successful job execution. 

Environment:  

CAWA EE (ESP), CAWA Agent for MS SQL server

Cause: 

The cause of the issue was that the USER parameter in the job was defined with accordance to the Windows domain user name notation, i.e. <domain name>\<user name>, i.e.

USER MyDomain\MyUser

However,  jTDS driver does not recognize the domain included in the user name, i.e. it does not read the <domain> as a domain from the <domain>\<username> but takes entire clause as the username.  Hence, the user account read as 'MyDomain\MyUser' would be definitely wrong. 

 

Resolution/Workaround:

Change the job definition, and instead of having

USER MyDomain\MyUser

set it as

USER MyUser

DOMAIN MyDomain

 

 

Environment

Release: DSWAHA01300-12-Workload Automation DE-High Availability
Component: