I'm trying to run a very simple DTS package using DTSRun command line
but keep getting a cryptic error that has stumped everybody in-house on
three continents.
The DTS pacakge (really just a test) simply inserts one record in a
table.
The paraphrased command line is this:

DTSrun -s MySQLServer -r MySQLDB -n MyDTSPackage -u SQLAgtSA -p
SQLAgtPW

The error message I get is:
Error: -2147467259 (80004005); Provider Error: 17 (11)
Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server
does not exist or access denied.

SQL Server and SQL Server agent run as SQLAgtSA. SQLAgtSA is a Windows
Domain user account with admin rights to the box on which SQL Server is
running and power user rights to several other boxes on the domain. The
DTS package runs fine from within DTS Designer when triggered
manually. It fails as a SQL job with an equally cryptic error message
implying something about access righs. I have read the TechNet article
about running DTS packages and it seems to me everything is OK. I have
tried many combinations of other users and passwords, spacing, using /
instead of -, ordering of parameters, anything I could possibly think
of. All to no avail.
Can anybody help?
Thanks.

I believe the problem is switch parameters are case-sensitive (i.e. -u is
different than -U)

Try upper-case:
DTSRun /S MySQLServer /R MySQLDB /N MyDTSPackage /U SQLAgtSA /P SQLAgtPW

- Tom


--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...r-dts/200508/1

Who owns the job? When you execute it manually, where are
you executing the package from?
The solution is still likely in the knowledge base article
on running DTS packages as scheduled jobs. When you run a
job manually, it runs from the location where the package is
executed and under the security context of whoever executes
the package. When you run it as a job, it runs from the
server and only under the security context of the SQL Agent
if the job is owned by a sysadmin - otherwise it's the proxy
account.
Also, try testing by logging onto the server and executing
the package manually.

-Sue

On 25 Aug 2005 12:39:18 -0700, "EoRaptor013"
<rchrismon (AT) patmedia (DOT) net> wrote:

I'd like to say you have to examin what is inside the DTS package. For
example, in a DTS package if you connect to other SQL Servers, who are
behind the firewalls, you may experience different stuff depending on where
you launch / run the DTS package.



"EoRaptor013" <rchrismon (AT) patmedia (DOT) net> wrote