CA7 Job Fails with Error 1326 "The user name or password is incorrect"
search cancel

CA7 Job Fails with Error 1326 "The user name or password is incorrect"

book

Article ID: 452845

calendar_today

Updated On:

Products

Workload Automation Agent CA 7 Workload Automation ESP dSeries Workload Automation - System Agent (dSeries)

Issue/Introduction

A CA7 job fails during submission to a Windows-based System Agent. The job remains in a SUBERROR state.

Log Evidence: The Agent's transmitter.log or receiver.log shows the following error:

text
 
State SUBERROR Failed SetEnd Status("The user name or password is incorrect.") Cmpc(1326)

The user has already verified that the user ID and password were added correctly via the AGPSWD panel and associated with the job via AGJOB.

Environment

  • Scheduling Manager: CA7 Workload Automation
  • Agent: Workload Automation System Agent (Windows)
  • Operating System: Windows Server

Cause

The Windows System Error 1326 indicates a logon failure. In the context of CA7 and the System Agent, this typically occurs for one of two reasons:

  1. Missing Domain Qualification: The user is a domain account, but the job definition only provides the flat userid without the DOMAIN\ prefix.
  2. Insufficient User Rights: The account does not have the required Windows security policies to allow the Agent to spawn the process as that user.

Resolution

Step 1: Verify User Format in CA7

For jobs running on Windows, the user ID must be qualified if it is a domain account.

  1. Access the job definition in CA7.
  2. Ensure the USER attribute is defined as DOMAIN\userid.
  3. Update the AGPSWD panel to include the same DOMAIN\userid entry with the correct password.

Step 2: Verify Windows User Rights Assignments

The specified user must have the following permissions on the target Windows server:

  1. Open Local Security Policy (secpol.msc).
  2. Navigate to Local Policies > User Rights Assignment.
  3. Ensure the user ID is added to:
    • Allow log on locally
    • Allow log on through Remote Desktop Services (Required for certain interactive sessions or versions).
  4. If the Agent is configured to run as a service under a specific account (other than Local System), ensure that the service account has the "Act as part of the operating system" and "Replace a process level token" rights.

Step 3: Refresh and Test

  1. If permissions were changed, a reboot of the Windows server or a restart of the Agent service may be required to clear cached credentials.
  2. Re-trigger the job from CA7.
  3. Verify in the Agent logs that the conversation now completes successfully without the Cmpc(1326) error.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.

Powered by Wolken Software