Re: Migrating DTS Local Package from test to production environments v7.0

From: Allan Mitchell (allan_at_no-spam.sqldts.com)
Date: 02/26/04 

Date: Thu, 26 Feb 2004 15:29:26 -0000

OK

So you may have a couple of problems

1. The version of SQL Server on which the package was create is SQL Server
2000 and the version runing it is 7 <SP3.
2. Tasks inside that are not registered

DTS runs at the client so manually will be on the invoker's PC which in this
case may be 2000 which will of course be fine but scheduled it may be a 7
server as detailed above and fail.

To avoid #1 save the 2000 package with a password and specify that when
invoking it in the job.
To avoid #2 you need to know what it is that thet may have registered
internally. 

-- 
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Ted" <myitpro@att.net> wrote in message
news:OE6IJeH$DHA.4060@TK2MSFTNGP10.phx.gbl...
> Thank you Ross and Allan for your suggestions.
>
> When I got to the client, the DTS package was working!  Well, it was
working
> if launched from the DTS Designer window, but would not launch from the
> Scheduler.
>
> This is a SQL Server 7.0 installation.  I don't know what SP level they
are
> at.
>
> The original error they were getting was:
> Error Source: Microsoft Data Transformation Services (DTS) Package
> Error Description: Invalid class string.
>
> A search for this error message turned up the MSDN Q288910.  The only
> applicable parts of the error cause and solution was (no OLAP and not
Server
> 2000):
>
> Cause:
> A package includes a user-designed custom DTS task but the workstation on
> which the package is opened does not have this task registered.
>
> Solution:
> If your package contains custom DTS tasks, you must register these tasks
on
> the workstation in question.
>
> There are no instructions on how to do the suggested solution.
>
> The client had rebooted the server a couple times, but this did not change
> the error.  The next morning, when I came in, the error was not being
> repeated.
>
> So, the situation is that the client can manually run the DTS package each
> morning, but it will not run from the scheduler.  They get a "failed"
> message.
>
> Not much to go on and the client is willing to "work it out themselves for
> now," but I'm curious for my own sake.  Any ideas what is causing the DTS
to
> work manually but not from the SQL scheduler?
>
> Thanks a lot.
>
> Ted
>
>

Relevant Pages

  • Re: SQL 2000 - Connection Error with DTS Packages
    ... After I changed all SQL Server 'Database Connection' steps in each of my DTS ... Package" option when you right click a DTS package name in ME. ...
    (microsoft.public.sqlserver.dts)
  • Re: DTS Package throws error on Client Machines only
    ... If my first solution does not work, I will investigate ways to launch a DTS package from a stored procedure which is executed from within SQL Server therefore these client files should not be needed. ... >> Dim strPkgName As String ...
    (microsoft.public.sqlserver.dts)
  • Re: Downgrade to 32bit version of SQL2005?
    ... if you choose to _migrate_ your DTS package into SSIS then: ... ""Data Driven Query" tasks in SQL Server 2000 DTS package will not be ...
    (microsoft.public.sqlserver.setup)
  • DTS - cant run as scheduled task
    ... SQL Server 2000, Enterprise Manager ... Microsoft Data Transformation Services (DTS) Package ...
    (microsoft.public.sqlserver.dts)
  • DTS - cant run as scheduled task
    ... SQL Server 2000, Enterprise Manager ... Microsoft Data Transformation Services (DTS) Package ...
    (microsoft.public.sqlserver.dts)