We had to rebuild our SQL server and before doing so, saved our DTS packages
off to a development server running the same SQL 2000 + SP3a setup.

Once the server was rebuilt, I resaved the packages from the devel box over
to the newly built SQL2K, SP3a server.

The packages run from within DTS Designer, and when right-clicking on the
package itself to run.

However, when I schedule the package to run, it fails every time. It gives
me the "invalid class string" error. I've read elsewhere it means a COM
CLSID cannot be located. However, why does it run on-demand from the
designer - from a remote Enterprise Manager connection, as well as the local
Enterprise Manager!

It is using the Visual FoxPro OLE DB driver which has been installed - so
those classes are registered. That's the only odd "com" DLL that might be
in use other than the standard SQL tasks, etc.

Any help on this? These packages worked fine on the server before it had to
be rebuilt. I don't remember any particular configuration changes I made to
the server that possibly would have allowed this to work otherwise. Any
help would be GREATLY appreciated.

Thanks.
A

In message <epFlP3tPEHA.3012 (AT) tk2msftngp13 (DOT) phx.gbl>, AVance
<avance@[atnospamforyou].invalid> writes
Does it work if you use Enterprise Manager whilst actually sat at the
server? The usual issue is because the location changes. when scheduled,
from your desktop to the server when scheduled.
Do you have any tasks available on the workstation that are not in the
server, for example a third-party custom task, or the OLAP task, which
does not come as part of a normal SQL Server tools install.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Darren,
Thanks for your reply.

The job runs fine from within Enterprise Manager both on my machine, and
the server itself. That's when you right-click the DTS package and execute
it.

There are no custom tasks on my machine that are not on the server --
that I am aware of. We only use the built-in tasks, and as I mentioned, the
FoxPro OLEDB Provider which is installed on both the server and my machine.

It's really wierd. It executes - thus, it's finding something. But
it's as if the dtsrun that the SQL Scheduled job sets up does not like the
package.

Any further tips?

Thanks, Aaron

"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

Aaron,

Just to be clear, if you are sat at the server machine, and log onto that
box directly (ideally using the SQL Server Agent service account) and run
the package there, so that it is really executing on the server, not a
client running EM that may be connected to the server, then it fails with
the error below?

In that case doesn't make a whole lot of sense!

Try and break the package, starting with one task, and add then back until
it breaks to try and isolate the task that causes the problem.

If the package cannot be run as described above on the server, then check
you have consistent service pack levels across the machines (client tools
need the SP not just servers, same install though).

Service Pack and Version Compatibility Problems
(http://www.sqldts.com/default.aspx?223)


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


"AVance" <avance[atnospamforyou]iowaheart.com> wrote

Hi,

I'm having this exact same problem. My package runs fine when executed
manually but fails with this error when scheduled.

Have you been able to find out what's going on??

thanks

Ricardo

Darren Green wrote:

Are you using any custom tasks?
Does the package actually start or does it fail at "Starting"

When a package runs fine manually and not when scheduled then it can usually
be attributed to this

http://support.microsoft.com/?kbid=269074

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
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


"Ricardo Sada" <rsada (AT) solcominter (DOT) com> wrote

No I'm not using any custom tasks.

The package, which actually runs some other packages using "Execute
Package Tasks" actually starts, but crashes at a particular one that
dows some data pumps from a FoxPro (DBF Style) database to SQL Server.

As I wrote.. the packege runs fine when executed in Enterprise Manager
manually.

I'll take a good look at the article though, and see what I can figure.

thanks Allan,

Allan Mitchell wrote:

In message <O#j8rsOSEHA.3608 (AT) TK2MSFTNGP10 (DOT) phx.gbl>, Ricardo Sada
<rsada (AT) solcominter (DOT) com> writes
thread. Right-click the task (black line), Workflow Properties, Options.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org