The SSIS 2008 R2 job does not complete execution
SQL Server 2008, SQL Server 2008 R2, SQL Server Integration Services, SQL Server tables, SSIS, SSIS 2008, SSIS Job
I have an SSIS package created in 2005 SP2. I have compiled this and is sheculed to run under SQL Server 2008 R2, which connects to a SQL Server 2005 database.
What the package does.
1.The package FTP's some files to the local folder. I verified to confirm the files are downloaded correctly.
2. Truncate the tablse. Verified to see the record count is 0.
3.Copies the data from the FTP'ed file to the tables. Verified to see the table is loaded.
4.Calls a stored procedure. Verified the log table to see the message of the last step in stored procedure is executed.
5.Added one more last step in the package to log an entry in the table to see the lat step in package is executed. This also works fine.
6. The job still shows "In Progress..." I have to manually close this job.
Any help
Software/Hardware used:
What the package does.
1.The package FTP's some files to the local folder. I verified to confirm the files are downloaded correctly.
2. Truncate the tablse. Verified to see the record count is 0.
3.Copies the data from the FTP'ed file to the tables. Verified to see the table is loaded.
4.Calls a stored procedure. Verified the log table to see the message of the last step in stored procedure is executed.
5.Added one more last step in the package to log an entry in the table to see the lat step in package is executed. This also works fine.
6. The job still shows "In Progress..." I have to manually close this job.
Any help
Software/Hardware used:
ASKED:
June 11, 2011 5:10 PM
UPDATED:
June 13, 2011 5:47 PM
RELATED QUESTIONS
- a question about IMPORT/EXPORT from the SQL 2005 Migration
- How do you set a SQL Server job step status?
- update the tables in to two server using a single ssis package
- SSIS 2008 R2 performance and Windows Server 2008 R2 with a clustered SQL instance is slower than when connecting to a non-clustered instance?
- SQL Server 2008 SSIS Update Command Performance Issue
Approved Answer - Chosen by MelanieYarbrough
It was the same result, the job was still hanging.
Atlast i found the issue. I disabled all the steps in the package and enabled one step at a time and tried to run the job. I figured the step that was causing the issue, the issue was, afterdownloading the files, it used an executable named ND.EXE to archive the files. This step was hanging since the ND.EXE was not exeuting in a 64 bit environment.
Other Answers:
What happens if you log into the server and run the package manually from the command line?
To see other answers submitted to the Answer Wiki: View Answer History.
Thanks a lot MrDenny for replying to this issue.