April 19, 2011 at 6:41 am
I receive this randon error in a DTS Package I have.
The step did not generate any output. The return value was unknown. The process exit code was 128.
Does anyone know what causes this and how I can get it resolved? I appreciate any assistance. Thank you.
April 20, 2011 at 12:31 am
Do you mean Integrations Services package or DTS package? Because there are a lot of differences between them.
What task generated this error? Is this the only error message that you got?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 20, 2011 at 6:01 am
I mean SSIS Pacakge, I apologize. The error log does not state was task generated the error and yes this was the only error I received.
April 20, 2011 at 6:15 am
Is it a possibilty to run the package in BIDS?
Did you run the package through a SQL Server Agent job? Maybe you can check the job history...
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 20, 2011 at 6:22 am
It is being ran through a SQL Server Agent job. I can re-run through BIDS put I can't re-create the error. I received it last night and restarted the job and everything worked fine.
April 20, 2011 at 6:29 am
That makes it kind of hard to troubleshoot 🙂
Nothing peculiar in the job history?
The issue could be caused by an offline database, a network error ... Something that is out of your control.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 20, 2011 at 6:33 am
Nothing peculiar at all in the job history. It actually has failed 2 days in a row now. Then we restart it and it works fine. Could it possibly be lock on the table at that time?
April 20, 2011 at 6:35 am
tchovanec 65734 (4/20/2011)
Nothing peculiar at all in the job history. It actually has failed 2 days in a row now. Then we restart it and it works fine. Could it possibly be lock on the table at that time?
It could be. If the table is locked, the queries can't run. It can also be a deadlock.
You could try to run Profiler at the same time when the job runs, so you can see what is actually going on.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply