Fail to open Control-M Module account confguration on Control-M Configuration Manager (CCM) with 'Error: Failed to create or connect to Container' popup

Knowledge Article

Article Number

000234982

Old Article Number

000036483

Article Type

Solutions to a Product Problem

Title

Fail to open Control-M Module account confguration on Control-M Configuration Manager (CCM) with 'Error: Failed to create or connect to Container' popup

Summary

Fail to open Control-M Module account confguration on Control-M Configuration Manager (CCM) with 'Error: Failed to create or connect to Container' popup

Product

Control-M for IBM InfoSphere DataStage

Component

Control-M for IBM InfoSphere DataStage

Applies to

All versions of Control-M for IBM InfoSphere DataStage

Problem

- When trying to create a Control-M for IBM InfoSphere Datastage Account in the Control-M Configuration Manager (CCM), get this error:
- Error: Failed to create or connect to Container

- Debug 4 logs on Control-M/Agent show:
0203 13:57:01:421 AS:ErrorSet: Container connect retries exceeded
0203 13:57:01:421 AS:ErrorSet: Failed to create or connect to Container. Container connect retries exceeded
0203 13:57:01:422 AS:Error: 'Failed to create or connect to Container. Container connect retries exceeded'
0203 13:57:01:423 AS:error occured: rc = 2, message: Failed to create or connect to Container. Container connect retries exceeded
0203 13:57:01:423 AS:AG_DSECT_send_error_dsect

Cause

The Control-M/Agent could not start or connect to the BMC Control-M for IBM InfoSphere DataStage container

Solution

- Do ensure that the Control-M Module job is not submitted during the New Day Procedures
- Control-M/Agent will require some time ( usually 1 - 2 minutes) to perform Control-M/Agent Cleanup during New Day Procedure

1. Verify that the full path to the BMC Control-M for IBM InfoSphere DataStage was used in the configuration command after install:

./ctmdatastage_container setds '<FULL_PATH_TO_DATASTAGE_EXE_DIR>'

2. Verify that the container is not running:

  ps -aef |grep java

3. Check for default port 38780 to see if it is already in use:
Unix:

netstat -an |grep 38780

Windows:

netstat -an | find "38780"

Attachment(s):