manual execute vs. dtsrun

Can anyone tell me the difference between "execute" on a package versus "dtsrun" command line?

I have a package that runs fine by right clicking and "execute", when I run from the command line with "dtsrun" it errors out with the following.  This is definitely not a permsissions problem, as I am logged in as the same account that runs the SQL Agent service.

Error = -2147467259 (80004005)      Error string:  Specified driver could not be loaded due to system error  1114 (Alchemy Driver (*.ald)).      Error source:  Microsoft OLE DB Provider for ODBC Drivers      Help file:        Help context:  0    

Package uses a 3rd party driver (Alchemy) to transfer data to a SQL db.

thanks for the help,
Mark
CRI906Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Jay ToopsConnect With a Mentor Commented:
hmm im almost thinking an "Environment" problem
that is ... does anything special have to be placed into the path or environment
for the alchemy drivers to work?

Jay
0
 
SoftEng007Commented:
when you click on the package and execute you get the odbc drivers from your workstation.
when you use dtsrun you get the odbc drivers from the server you run the package on.

Are you sure the drivers are installed and working on your server?
0
 
Jay ToopsCommented:
good point.. i'll bet they arn't
jay
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
CRI906Author Commented:
I'm logged in to the console of the server machine and running both Enterprise Manager and the command line DTSRUN.
0
 
SoftEng007Commented:
check to see what user sql agent is using.

I believe dtsrun will use those permissions.

enterprise manager will use the permissions of the user.
0
 
CRI906Author Commented:
I'm logged in to the console with the same account that starts the SQLAgent service.
0
 
SoftEng007Connect With a Mentor Commented:
I'm starting to lean towards jltoops answer.
if you open a command prompt can you navigate to the directory where the alchemy drivers are located.

are the environment variables the same between what you see in you environment path in windows
versus the PATH variable from a command prompt?
it may be an install issue with the alchemy drivers.

other than that I'm out of ideas :(
0
 
CRI906Author Commented:
Yes, path variables have the same values. I am able to reproduce this error on another SQL box as well.
I'm perplexed. Thanks for the effort.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.