Hello all,

I mentioned this problem earlier, but I found something interesting...

I created a DTS to import an ASCII-file. When I manually start this DTS,
everything is working fine. But when I schedule this one, it fails.

I use real datatype fields in the table and I found out this was the
reason the scheduled DTS failed. So I changed the datatype fields into
numeric and also the scheduled DTS works fine.

But...

The kept the original DTS (with the real datatype fields). I scheduled
this DTS on another system and guess... It was working!

This last system is up-to-date with al the patches and fixes for
Windows. The first one not.

Can anyone tell me which patch / fix is the reason it's working on the
second machine? Does it have anything to do with MDAC, ODBC, or
something else?

Thanks in advance,
Marco.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

It's a permission thing.
When you run it manually it runs as you, when you run it
as a scheduled task it runs as the account SQLServerAgent
is starting as.
Try making the SQL Agent service start as your account.

Here is a good article abut running DTS as a scheduled job

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

--
--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Ryan Waight" <Ryan_Waight (AT) nospam (DOT) hotmail.com> wrote

Hello Ryan,

First of all thanks for your reply.

But it's no permission item. Because when I changed the datatype fields
into numeric, the scheduled job was working.

It seems it has something to do with a missing patch or something.

Regards,
Marco.



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!