Case one - upgrade from SQL 2000 to SQL 2005 in the same box
(actually it is a copy of the test box being upgraded)
Case two - install fresh SQL 2005 in a different box
Results for running (dts packages migrated to dtsx) in SSIS from a job
Note all other jobs in (Case one) using the old DTSRUN works fine, but new jobs trying to run migrated packages fail. Migrating this new package to (Case two) runs. How do I troubleshoot this? The process exit code was -532459699.
Is this exit code something that can be looked up?
Case one
Date 4/17/2007 2:51:49 PM
Log Job History (TEST SSIS5)
Step ID 1
Server USXXXX4O
Job Name TEST SSIS5
Step Name SSIS5
Duration 00:00:02
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: xxxx. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:51:49 PM. The return value was unknown. The process exit code was -532459699. The step failed.
Case two
Date 4/17/2007 2:34:07 PM
Log Job History (TEST SSIS5)
Step ID 1
Server USXXXX4
Job Name TEST SSIS5
Step Name SSIS5
Duration 00:00:07
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: xxxx. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:34:07 PM DTExec: The package execution returned DTSER_SUCCESS (0). Started: 2:34:07 PM Finished: 2:34:14 PM Elapsed: 6.328 seconds. The package executed successfully. The step succeeded.
Have you run the package manually to see if it gives different results or where it fails?
|||
Manually runs fine for both cases from within SQL Server BI Dev Studio and also the SQL Server Mmgt Studio.
Got a link to the logging setting you mentioned earlier.
Thanks.
No comments:
Post a Comment