I just created a SSIS package and added an Execute DTS 2000 Package
Task.
I set its properties to look for a DTS on a SQL 2000.
I run the package from dev studio: OK
I saved it on MSDB in SQL 2005, I created a job that runs that package
(as an Integration service type) and run it:
Code: 0x00000000 Source: Execute DTS 2000 Package Task
Description: This task does not support native Win64 environment.
Please run the package in 32-bit WOW environment instead.

I then changed the step type to cmdexec and added the following line
before command arguments: "C:\Program Files (x86)\Microsoft SQL Server
\90\DTS\Binn\dtexec.exe": OK.

So if you need to run DTS package in a 2005 agent job, you can with
some workaround...
If you need to run a DTS package on a 2005 job using DTSrun, you can
try copying dtsrun and related .dlls onto a folder (or installing
sql2000 client) on your server and then schedule a job with a cmdexec
with dtsrun, just like you did in sql2000.
Bye,
M.

I just created a SSIS package and added an Execute DTS 2000 Package
Task.
I set its properties to look for a DTS on a SQL 2000.
I run the package from dev studio: OK
I saved it on MSDB in SQL 2005, I created a job that runs that package
(as an Integration service type) and run it:
Code: 0x00000000 Source: Execute DTS 2000 Package Task
Description: This task does not support native Win64 environment.
Please run the package in 32-bit WOW environment instead.

I then changed the step type to cmdexec and added the following line
before command arguments: "C:\Program Files (x86)\Microsoft SQL Server
\90\DTS\Binn\dtexec.exe": OK.

So if you need to run DTS package in a 2005 agent job, you can with
some workaround...
If you need to run a DTS package on a 2005 job using DTSrun, you can
try copying dtsrun and related .dlls onto a folder (or installing
sql2000 client) on your server and then schedule a job with a cmdexec
with dtsrun, just like you did in sql2000.
Bye,
M.

I just created a SSIS package and added an Execute DTS 2000 Package
Task.
I set its properties to look for a DTS on a SQL 2000.
I run the package from dev studio: OK
I saved it on MSDB in SQL 2005, I created a job that runs that package
(as an Integration service type) and run it:
Code: 0x00000000 Source: Execute DTS 2000 Package Task
Description: This task does not support native Win64 environment.
Please run the package in 32-bit WOW environment instead.

I then changed the step type to cmdexec and added the following line
before command arguments: "C:\Program Files (x86)\Microsoft SQL Server
\90\DTS\Binn\dtexec.exe": OK.

So if you need to run DTS package in a 2005 agent job, you can with
some workaround...
If you need to run a DTS package on a 2005 job using DTSrun, you can
try copying dtsrun and related .dlls onto a folder (or installing
sql2000 client) on your server and then schedule a job with a cmdexec
with dtsrun, just like you did in sql2000.
Bye,
M.

I just created a SSIS package and added an Execute DTS 2000 Package
Task.
I set its properties to look for a DTS on a SQL 2000.
I run the package from dev studio: OK
I saved it on MSDB in SQL 2005, I created a job that runs that package
(as an Integration service type) and run it:
Code: 0x00000000 Source: Execute DTS 2000 Package Task
Description: This task does not support native Win64 environment.
Please run the package in 32-bit WOW environment instead.

I then changed the step type to cmdexec and added the following line
before command arguments: "C:\Program Files (x86)\Microsoft SQL Server
\90\DTS\Binn\dtexec.exe": OK.

So if you need to run DTS package in a 2005 agent job, you can with
some workaround...
If you need to run a DTS package on a 2005 job using DTSrun, you can
try copying dtsrun and related .dlls onto a folder (or installing
sql2000 client) on your server and then schedule a job with a cmdexec
with dtsrun, just like you did in sql2000.
Bye,
M.

I just created a SSIS package and added an Execute DTS 2000 Package
Task.
I set its properties to look for a DTS on a SQL 2000.
I run the package from dev studio: OK
I saved it on MSDB in SQL 2005, I created a job that runs that package
(as an Integration service type) and run it:
Code: 0x00000000 Source: Execute DTS 2000 Package Task
Description: This task does not support native Win64 environment.
Please run the package in 32-bit WOW environment instead.

I then changed the step type to cmdexec and added the following line
before command arguments: "C:\Program Files (x86)\Microsoft SQL Server
\90\DTS\Binn\dtexec.exe": OK.

So if you need to run DTS package in a 2005 agent job, you can with
some workaround...
If you need to run a DTS package on a 2005 job using DTSrun, you can
try copying dtsrun and related .dlls onto a folder (or installing
sql2000 client) on your server and then schedule a job with a cmdexec
with dtsrun, just like you did in sql2000.
Bye,
M.