search cancel

AE locks up when user attempts login resulting in U0051000 ‘Time out’ error

book

Article ID: 88093

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
U0051000 Error in function 'connect(xxx.xxx.xxx)':'Time out' (error code: '110')
U0051000 Error in function 'connect(xxx.xxx.xxx)':'Connection refused' (error code: '111')

The Automation Engine (AE) locks up when users, belonging to a certain problematic LDAP domain, attempt to log in.

Investigation

The WP logs show this type of error.

Example: 
20170403/003629.122 - U0051000 Error in function 'connect(xxx.xxx.xxx)':'Time out' (error code: '110') 
20170403/003630.237 - U0003205 Logon of 'FirstName LastName' ('User/Domain'), client: '0000' accepted by host 'xxxxxxxxx'. Client version = '10.0.6+build.509', type='Dialog' (connection='*CP005#00000197', index='051'). 
20170403/003630.261 - U0003434 Server routine 'UCUSER_R/ANMELD2' required '3' minutes and '10,327' seconds for processing. 

Environment

OS Version: N/A

Cause

Cause type:
Configuration
Root Cause: U0027001 Cannot load library 'xuc4pass.so' for exit 'XUC4PASS', error code '0'. Password Exit is implemented. There is an issue with the load library.

Resolution

Upgrade to the latest Automation Engine version, which uses the LDAPS/KERBEROS through the new JWP.
With this new implementation, the PWP is not locked because the LDAP check is done by another process through the Kerberos or LDAPS.


Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
1. Restart the engine

OR  

2. Disable the LDAP connection for the users connected to the problematic LDAP domain