The SQL Connection object is failing: could not be resolved. Reason: 'no_Login_Entry'

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Users may encounter an error when attempting to test a Connection object within the system. Specifically, when clicking the TEST button for a SQL connection, the following error message is displayed:

Detail: 'LOGIN.OBJECT' for connection 'CONN.SQL.CONNECTION' could not be resolved. Reason: 'no_Login_Entry'

Environment

Product: CA Automic Workload Automation - Automation Engine 24.x

Cause

The primary cause of this issue is a configuration mismatch in the Login object. The system cannot resolve the login entry because the Login object is either missing the correct host/agent assignment or is not specifically pointed to the DBService agent required for the connection. 

Resolution

To resolve this error, you must update the Login object to explicitly reference the DBService agent.

1. Open the Login object referenced in the error (e.g., LOGIN.OBJECT).

2. Navigate to the Login tab.

3. Locate the row intended for the database connection.

4. In the Agent/Type column, ensure that the specific DBService agent name is selected or entered.

5. Verify that the Username and Password associated with that agent entry are correct.

6. Save the Login object.

7. Return to the Connection object (CONN.SQL.CONNECTION) and click TEST to verify the fix.

Note: If the "Agent/Type" is set to a generic value or a different host, the "no_Login_Entry" error will persist until it matches the agent executing the job or service.