File events and file checks on post conditions fail resulting in U00065013 Unable to start event error
Article ID: 84698
Updated On:
Products
CA Automic Workload Automation - Automation Engine
AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction
Error Message :
U00065013 Unable to start event '18044556', reason: 'corrupt user 'uc4' password'.
File events and file checks on post conditions fail if you run them without setting ANONYMOUS_FE for the agent.
U00065013 Unable to start event '18044556', reason: 'corrupt user 'uc4' password'.
File events and file checks on post conditions fail if you run them without setting ANONYMOUS_FE for the agent.
Cause
Cause type:
Defect
Root Cause: A problem has been fixed where in Conditions "Check File" dialog now can the user choose an Login object.
Defect
Root Cause: A problem has been fixed where in Conditions "Check File" dialog now can the user choose an Login object.
Environment
OS: All Linux/Unix
OS Version: N/A
OS Version: N/A
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: In Progress
Fix Version(s):
Automation Engine 12.1.1 - Available
Automation Engine 12.2.0 - Planned Release date: 2018-06-19
Automation Engine 12.2.6 - Available
Automation Engine 12.0.4 - Available
Additional Information
Workaround :
1. Set ANONYMOUS_FE = Y in UC_HOSTCHAR_DEFAULT
2. In Client 0, SystemOverview > Users, right-click on the user used to *start*/*kick off* the FileEvent and select Edit. Under "Privileges" check the privilege "File Events: Start without login object specified" and remove LOGIN from FileEvent.
3. Restart the Unix/Linux Agent where the file event would run on.
1. Set ANONYMOUS_FE = Y in UC_HOSTCHAR_DEFAULT
2. In Client 0, SystemOverview > Users, right-click on the user used to *start*/*kick off* the FileEvent and select Edit. Under "Privileges" check the privilege "File Events: Start without login object specified" and remove LOGIN from FileEvent.
3. Restart the Unix/Linux Agent where the file event would run on.
Feedback
Powered by
