"Invalid Class String" Message when loading/executing package ( related to Q274716?)

[Mark Craft]

I've got a package thats been written with 2000 tools, I can load this onto
a v7.0 Server using 2000 enterprise manager, but it will not execute, giving
the error "Invalid Class String". If I use v7.0 Enterprise manager I can't
even open the package ( from structured file or from the server ), same
error message is given. DTSRun wont run it either ( again same message ).

This is using v7.0 SP3, I applied SP3 as I was experiencing another error
message at exactly the same point ( "Cannot find the file specified" ) as
detailed in article Q274716 (
http://support.microsoft.com/support/kb/articles/Q274/7/16.ASP )

Thinking it was the server screwed up I have completely removed &
reinstalled Sql Server, this made no difference.

DTSRun report is as follows;

DTSRun: Loading...

Error: -2147221005 (800401F3); Provider Error: 0 (0)

Error string: Invalid class string

Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 713

Any help gratefully received!

Mark

[Stephen Allen]

Mark,

This is a documented problem. There are differences in the
formats of packages written in 2000/7.0.

Basicly 2000 adds additional propetries to a DTS package
that are not in a 7.0 package. You can not open a package
written in 2000 with 7.0 tools, but you can sometimes run
packages written in 2000 on a 7.0 box.

My rule of thumb is to write DTS packages with the same
version of SQL tools as the intended platform.

>.
>

[George Mason]

Mark,

What does your package do? It may be trying to use a function that is
valid for SQL Server 2000, but is not valid in SQL Server 7.0. Try
creating the package using the SQL Server 7.0 tools, and see if you see the
same behavior.

Thanks,

George Mason

Microsoft SQL Server Support

Please reply only to the newsgroups.
When posting, please state the version of SQL Server being used and the
error number/exact error message text received, if any.

[Darren Green]

In article <ef3c01c11f6f$b96528d0$9be62ecf@tkmsftngxa03>, Stephen Allen
<Stephe...@Systems-RSA.com> writes

>Mark,
>
>This is a documented problem. There are differences in the
>formats of packages written in 2000/7.0.
>
>Basicly 2000 adds additional propetries to a DTS package
>that are not in a 7.0 package. You can not open a package
>written in 2000 with 7.0 tools, but you can sometimes run
>packages written in 2000 on a 7.0 box.
>

>My rule of thumb is to write DTS packages with the same
>version of SQL tools as the intended platform.
>

Whilst this will obviously ensure you don't have such problems I much
prefer using the best tools but ensure I understand the limitations.
Things like Disco Edit are very powerfully features in the SQL 2000 EM
and work just as well against 7.0

My rule is don't use any SQL 2000 tasks or properties (usually on the
Object2 interface which is of course 2000 specific).

Ensure all machines have SP3 (including clients) or use package
passwords.

"Invalid Class String" just means it cannot find a DLL. This is normally
because you have used a SQL 2000 specific task or property and the 7.0
machine cannot find the appropriate DLL.

The error itself is not specific to 7.0 Vs 2000. You can cause it
yourself by using your own custom task which is not installed on the
second machine.

--
Darren Green
http://www.sqldts.com