11 months ago by
The error was due to using an older version of the tool
220.127.116.1151222.0 that has a known issue. It was corrected in the most current version of the tool on the server, confirmed in our earlier tests, your history, and in a rerun today.
The corrected tool version is the one accessed from the tool panel right now
This job was run with a workflow, correct? It should have the tool edited to use the updated version. This will permit successful batch job execution again.
Thanks for sending this in! It helped very much to see the actual history content to resolve what the root cause of the error.