SQL Error when running SSIS from Agent

Question

I am working on a project to sync a few tables from a Firebird database to a Microsoft SQL Database using the Import wizard/Scheduled job and am receiving the below error code on 1/5 tables that I am trying to sync.

"The step did not generate any output. The return value was unknown. The process exit code was 255. The step failed."

The other 4 tables are working properly when run both from SSIS and from the agent. The 1 table having issues is working fine when I execute it from the SSIS console, however when I execute the schedule job it always fails on this step.

I have tried the script in both 32 and 64 bit modes, and verified that all of the SSIS packages are being run with the same credentials.

Not sure what else to test so I thought I would see if anybody had any suggestions on this.

Answer 1

I have read through those articles and the first one seems to deal with a different error code (255 vs -1073741502), I have also ruled out all of the points in the second document above as it is working against the same data source, with the same settings on a different table.

What I have found is that this will work when connecting to another data source with the same table structure, I then added some retries to this scheduled task step and I now get a success after 3 or 4 retries.

I am thinking it is potentially an issue with the actual source data table since it is working on my similar data sets.

Here is an article where the person found that a similar issue was with the ODBC connector to Oracle, the problem seems almost the same as mine: https://stackoverflow.com/questions/11619564/weird-ssis-error-process-exit-code-255

I am going to try with the retries added in and see how it performs for the next couple weeks.

Answer 2

Hi @Jeremy ,

The error message is a bit hard for us to narrow down the issue.

Could you please use Process Monitor to check if that could give us any details about the error?

You may also check the Event Viewer to do some more analyze.

Here are two links which mentioned the same error, you may take a carefully reference to.

ssis-package-fails-with-error-the-step-did-not-generate-any-output-the-return-value-was-unknown

ssis-package-doesnt-run-when-called-job-step

Regards，

Zoe

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.