Job Task for SSIS packet

  • Good Morning,

    i have migrated a DTS 2000 packet with Business Intelligence Studio 2008. Then i exported it to the sql 2008 Server. There i created a task to run automatically the new SSIS packet.

    But after a few seconds an error occured.

    Executed as user: HELLMANN\sqlclstsrv. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 09:26:46 Error: 2010-06-30 09:26:46.96 Code: 0x00000000 Source: Erstellen Dimension Konto Description: System.ApplicationException: The Execute DTS 2000 Package task requires the SQL Server 2000 Data Transformation Services (DTS) runtime. To install the DTS runtime, on your SQL Server 2008 installation media, locate and run the Windows Installer package for SQL Server 2005 Backward Compatibility (SQLServer2005_BC*.msi). You can also download the DTS runtime from the SQL Server Feature Pack page on the Microsoft Download Center. at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.PackageUtils.LoadDTS8Package(String pkgSrc, String sourceUser, String sourcePwd, Int32 srcType, Boolean bUseTrustedConnection, String packageName, String packagePassword, String packageID, String packageVersionGUID) at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.LoadPackage() at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread() End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 09:26:46 Finished: 09:26:46 Elapsed: 0.578 seconds. The package execution failed. The step failed.

    But i have no DTS 2000 packet. It is now a orignalle ssis packet. In the Business Intelligence Studio the packet runs perfekt.

    In the Step to start the SSIS packet, the commandline is:

    /SQL "\ProcessCube" /SERVER SLHLMSQLCLST /USER sa /PASSWORD /CHECKPOINTING OFF /REPORTING E

    Is that right ?

    I use 2 data sources, but in the Task i don't check the two data sources on, because, when i do that, i become a error, that the command line is wrong.

    What goes wrong here ?

    Kind regards

  • Ok first Package not packet..

    Now I think there are some misunderstandings here.

    1. When a package is upgraded the wizard tries its best to make a full 2005/2008 package with no 2000 components.

    2. When there are such things as dynamic properties components or script tasks they usually get put into an EXEC DTS 2000 task, so you might have a 2008 package but it still has 2000 stuff in it.

    You need to look the pacakge over, I am 99.9999% sure you have a EXEC DTS 2000 task.

    Also I'm willing to be where you did the conversion was NOT on the same amchine as the server so the fact it works on your desktop and not the server doesn't tell us much.

    CEWII

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply