Error: CAUAJM_E_10032 Unable to create server object for host

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent

Issue/Introduction

This article addresses the CAUAJM_E_10032 error, which commonly occurs when the Workload Automation AE (AutoSys) Web Client (WCC) fails to establish communication with the Workload Automation server. This communication breakdown is frequently triggered by a failure in the CSAM (Common Services Application Manager) listener, which prevents legitimate connection requests from processing. This article provides steps to diagnose and resolve this issue by ensuring proper file permissions for the CSAM broker socket.

Scenario:

$ autoping -m <hostname>
CAUAJM_W_00002 Listener could not be started on port [0]. Proceeding... [msgSocket::msgSocket(server socket)(): 16: Device or resource busy] 
CAUAJM_E_50033 Error initializing tx subsystem: CAUAJM_E_10032 Unable to create server object for host [hostname]. 

 

WebUI (WCC) is displaying an error message when running any query in the Quick View Window:

• CAUAJM_E_10032 Unable to create server object for host [hostname].
• E139012 Autosys error response:CAUAJM_E_10032 Unable to create server object for host [hostname].
• E131003 Error loading the job:E180010 Failed to establish a connection to AutoSys Application Server.

Environment

• Product: Autosys Workload Automation (AE)
• Platform: Linux/Unix
   

Cause

The error occurs because the .csam_broker file (located in the CSAM SockAdapter directory) lacks the required write permissions for the Unix user or group. This restriction prevents the CSAM listener from creating the necessary socket, leading to the "Device or resource busy" error in the WCC logs.

Resolution

Follow these steps to update the file permissions and restore communication:

1. Log in to the server where WCC is installed.
2. Navigate to the CSAM SockAdapter directory (the default path is typically /opt/CA/SharedComponents/Csam/SockAdapter/): cd /opt/CA/SharedComponents/Csam/SockAdapter/
3. Verify the current permissions for the .csam_broker file: ls -la .csam_broker
4. Apply the necessary permissions to allow write access for the group: chmod o+w .csam_broker
5. Restart the CSAM and WCC services to apply the changes.
6. Attempt to validate the instance again within the WCC interface to confirm the connection is restored.

Additional Information

If the issue persists after updating permissions, collect the WCC and CSAM logs and review them for any secondary errors.

For the latest updates, or to speak with a customer representative, see Contact Support. Scroll to the bottom of the page and click on the respective region.

Subscribe to this article to receive an email notification whenever there is an update. For details on how to manage these notifications, please see Subscribe to a Broadcom knowledge article."