We have a vendor who has an SSIS package that executes a DTS package. We've asked that they migrate the DTS code completely to SSIS, but that is something that will not be done in the near future. The package is scheduled to run every 5 minutes through a SQL Server scheduled job.95% of the time the package executes without an error, but occassionally the following error is reported. Date10/2/2007 7:35:00 AMLogJob History (Pyxis - Data Load) Step ID1ServerDEVSQL1V5Job NamePyxis - Data LoadStep NameRun SSIS PackageDuration00:00:03Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0 MessageExecuted as user: Domain_Name\SQLService. The return value was unknown. The process exit code was -1073741819. The step failed. When I look at the DTS and SSIS package logs no errors are reported and each log indicates the package completed successfully. Any ideas what this exit code is indicating or how to further troubleshoot the problem? Thanks, Dave

Take a look here and see if this helps: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1162060&SiteID=1 Also, ensure that in the job step under SQL Agent that you are capturing the job output to history.

We were getting this error: The process exit code was "-1073741819" while the expected was "0". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:03:21 AM Finished: 10:03:26 AM Elapsed: 5.055 seconds. The package execution failed. The step failed. For some reason it would run if the proxied user was logged in, but not if the package was running just by itself from SQL Server. Just to be clear, I was running SSMS and remotely connecting to the SQL Server and the only difference between running and not, was opening a remote desktop session and logging into the box itself. The resolution was odd. Apparently GNUPG was located in both program files directories and if we chose to execute the x86 version, it failed. If we chose to run the main Program Files directory it worked. Doubt this is a common problem, but one more thing to check.

hey, did you got any solution for this I am also having the same error every time a run the package.Ratan

hey, did you got any solution for this I am also having the same error every time a run the package. Ratan Who is running the package? Check the selected proxy at the jobstep and then the used credential. The user used in that credential should have sufficient rights.Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com | Twitter