I have a SSIS job that has been running for about 2 months no with no issues until the other day it fails to execute with the following message. The step did not generate any output. The return value was unknown. The process exit code was 255. The step failed. I have event handlers on all my SSIS processes that email me if the package fails and I receive no emails so its almost like the job never starts. If I restart the sql agent the process will work fine again for awhile. I have other SSIS jobs that run on the same agent and are having no issues..... Anyone have any ideas?Thanks

No one has had this happen before?

To be honest, I believe I have had this issue in the past. However, I don't remember what it is that I did to resolve the issue. Have you output the logs from the SQL Agent job itself? Have you looked at the Server logs to see if there were any errors? The SQL Agent log? The windows app log? etc...Please mark answered posts. Thanks for your time.

I checked the application event viewer on the server itself and I did see a few errors like this: Faulting Application dtexec.exe,version 2007.100.2531.0

I ended up not using the job to run the SSIS package since it wasn't really a scheduled task anyway and now have it called on demand from a .net application using a stored procedure that calls dtexec command utility using xp_cmdshell. The package runs great this way.

Hello, How did you handle this Issue. Pl. provide me tips as Iam facing the same problem here. My Packages are running wonderfullly since 4 months and suddenly it failed showing this error. Pl. suggest some tips, pl. Thank You ChanduChandu - SQL Server 2005 - Please mark posts as answered where appropriate.

Hello, I think I had the same problem today with a job that ran for months. The server logged: Message Executed as user: domain\server$. The step did not generate any output. The return value was unknown. The process exit code was 255. The step failed. In this case a dataflow task within the ssis package caused the error. The task itself and all following tasks succeeded, but obviously the dataflow task hindered the job step from completion. The task loads data from two oracle db sources into a flat file destination. I set the delay validation property of the dataflow task to true. I know this is rather a workaround than a solution, but it worked.

Thanks Ramexx for providing workaround: Restarting SQL Agent. I hope this doesn't happen again. Cheers, Ferruccio GuicciardiApplication Support