This content has been marked as final. Show 1 reply
Which version and release are you using? 220.127.116.11 version upto the .305 release has this trouble, if i still remember well.
.306 solves this issue.
The only thing that could work is by breaking up the number of records into smaller chunks.
One more thing which can try is ... Running the script from Batch client and see if the log file captures it. not sure about this one though if the log will capture the error records. Try out one record which you think would error out and see if the log file captures it.