When a custom code step encounters a problem, the process worker will usually generate a sequence of related errors that can be found in the Windows application event log. Identifying the sequence is helpful in understanding the problem since the first errors tend to be the most descriptive and closest to the origin of the problem.
Event ID 5402: Failure Compiling/Executing Custom Code.
Version: R70
Article ID: PC000004
Description
Summary
When custom code is compiled in the Job Studio it does not guarantee that the code will execute properly at runtime. A simple spelling mistake can cause a failure that may not be immediately apparent. When this happens there will usually be a sequence of errors occurring at the same interval as the Automation Service’s Process Batch Schedule. The first errors in the sequence will generally contain the most specific and useful information for identifying the source of the problem.
To resolve the custom code issue follow the steps below:
- Check out the job that needs to be addressed.
- Correct the area of custom code that needs to be fixed.
- Check the job back in.
- The system will continuously try to re-process the batch so that once the code is corrected, it will execute properly without further intervention.