ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Windows Agent crashes when running JOBF where transfer file name includes special characters
Article ID: 84422
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
In the log of the SMgr the agent crashes with the following return code: 3221226505 >>> 0xC0000409
The Windows Agent crashes when running a JOBF job when the transfer file name includes a non-supported character.
For example, if the transfer files contain a colon in its name, which is not supported on Windows (as well as on Windows agent), the Agent will be terminated.
The log of the Service Manager (SMgr) shows the agent crashes with the following return code: 3221226505 >>> 0xC0000409.
JOBF can only proceed with filenames which can be created by the operating system itself.
In the log of the SMgr the agent crashes with the following return code: 3221226505 >>> 0xC0000409
The Windows Agent crashes when running a JOBF job when the transfer file name includes a non-supported character.
For example, if the transfer files contain a colon in its name, which is not supported on Windows (as well as on Windows agent), the Agent will be terminated.
The log of the Service Manager (SMgr) shows the agent crashes with the following return code: 3221226505 >>> 0xC0000409.
JOBF can only proceed with filenames which can be created by the operating system itself.
Cause
Cause type:
By design
Root Cause: JOBF only can proceed with filenames which can be created by the operating system itself.
By design
Root Cause: JOBF only can proceed with filenames which can be created by the operating system itself.
Environment
OS Version: N/A
Resolution
Change filenames or zip the files so that they do not contain any unsupported Windows characters.
Reference
Refer to the Microsoft definition of illegal characters in filenames, which does include the colon:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx
https://support.microsoft.com/en-us/kb/177506
Fix Status: No Fix
Reference
Refer to the Microsoft definition of illegal characters in filenames, which does include the colon:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx
https://support.microsoft.com/en-us/kb/177506
Fix Status: No Fix
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
