File Events fail with U00065006 error after logging change within Event
Article ID: 85102
Updated On:
Products
Issue/Introduction
Error Message :
U00065005 Unable to start event '&01' as user '&02', reason: '&03'.
If a File Event on a UNIX or Windows environment is running for a longer period of time, the trigger may not parse the file system correctly and a message similar to the one above is displayed.
This is caused by the logging turnaround of the Event which takes place to avoid long-term running events with endless reports and statistics entries which will never be recognized by a reorganization run. The turnaround time depends on CHANGE_LOGGING_DAYS in UC_SYSTEM_SETTINGS which is by default 14 days and takes place at midnight.
At the turnaround a new Event is started with the same parent ID. The new task cannot sign in to a user session on the Agent on the OS side, which then returns the stated error message. If the login is on Active Directory, the account may be locked and affect other jobs which use the same account.
On Windows the issue is associated with error message: ErrorCode '1326' - The user name or password is incorrect. Source: LogonUser(BATCH)'.
The issue does not occur if the File events are not running for longer than a few days.
Environment
Cause
Defect
Root Cause: Fileevents do not work after the logging of the event has changed. Error "U00065005 Unable to start event '12345678' as user 'user1', reason: 'corrupt user 'user1' password'." is shown.
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: Released
Fix Version(s):
Component(s): AE Server and Initialdata
Automation Engine 12.1.0 - Available
Automation Engine 12.0.1 - Available
Automation Engine 11.2.4 - Available
Additional Information
Workaround :
Restart the Event (manually or automatically) before the turnaround, that way the turnaround will not take place and the error will not occur.
Feedback
