RE: Incorrect DTS package version run by scheduled job

From: Craig (CraigNicholas_at_online.nospam)
Date: 09/07/04


Date: Tue, 7 Sep 2004 07:15:03 -0700

I've found the reason why ...
I had scheduled the job on another server and generated a SQL script from
the job.
Then I installed the package on another SQL server and installed the job
from the script. The job was running the DTS package on the original SQL
Server.
I now understand the encrpted DSTRUN command generated is NOT portable.

"Craig" wrote:

> Hi
> I have scheduled a DTS package which works fine.
> The last step in the package is a T-SQL task.
> I changed the T-SQL task and reran the scheduled job but it ran the original
> version.
> I removed the original version but the scheduled job still ran the original
> version.
> I restarted SQL Agent and SQL Server but the result is the same.
>
> Any suggestions?
> --
> Regards,
> Craig



Relevant Pages

  • Re: Problems launching DTS package from Stored Procedure
    ... I cannot run enterprise manager on our server because it is not installed. ... I can post the SQL later if necessary. ... >>package name as a parameter, executes the package and continues on. ...
    (microsoft.public.sqlserver.dts)
  • Re: SSIS package wont run in production server
    ... I also would like to mention that on my production server, ... When you run the setup of SQL 2005, it is indeed possible to install only ... I have a package that I developed on my local machine and runs well. ...
    (microsoft.public.sqlserver.dts)
  • Re: SSIS as part of scheduled job fails
    ... deploying to SQL 2005. ... This server has SQL 2000 as the default instance and a ... Encryptall... ... when you installed the package on the server? ...
    (microsoft.public.sqlserver.dts)
  • Re: Incorrect DTS package version run by scheduled job
    ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. ... > I would prefer it if the Generate SQL Script option did not generate an> encrypted command line. ... I never use the functionality of right>>>clicking on a package and use the Schedule Package. ...
    (microsoft.public.sqlserver.dts)
  • Re: more detail on issue
    ... then have SQL and SQL Agent running as an ... When you installed the package to your SQL ... Server, did it prompt you for the password you packaged with? ... strings not being visible to the SQL Agent user. ...
    (microsoft.public.sqlserver.dts)