April 27, 2020 at 2:48 pm
If I was experiencing this error, I would first try to create an input file with a single record that caused the error. Creating such a file can be a challenge. Sometimes it is possible to identify the error record by setting a break point in the script's catch block and examining variables when it's hit.
In some cases I've had to resort to a binary search. I.e. run half the records in the file, if no error then run the other half. Repeat with the half that causes the error, and repeat again til one record has been identified that that consistently causes the error.
Using that file, step through the offending script in the debugger to locate the last line executed before control transfers to the catch block.
January 26, 2023 at 9:34 am
I setup logging as mention below https://www.mssqltips.com/sqlservertip/4070/integrated-logging-with-the-integration-services-package-log-providers/
Unfortunately I didn't get an error in the table to suggest what the problem was.
The package runs on the older servers and the difference is the OS version.
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply