Posted by Erland Sommarskog on 03/24/06 00:56

mike (mike.a.rea@gmail.com) writes:
> Yea to me using the /E /P switches did not make sense either, but using
> the /E switch by itself gave the error and using both worked for me as
> dud using the /U /P which is more standard.
> Here is what I am using
>
> dtsrun /S server /U username /P password /N dtspackage
>
>
> Here is what it is returning
>
> Step 'Copy Data from xxxxxxxx to [xxxx].[dbo].[xxxxxxxxxxxx] Step'
> failed
>
> Step Error Source: Microsoft OLE DB Provider for SQL Server
> Step Error Description:Login failed for user 'domain\username'.
> Step Error code: 80040E4D
> Step Error Help File:
> Step Error Help Context ID:0
>
>
> But like I said if I use the OSQL lines they run fine like this
>
> osql /S server /U username /P password /i c:\live_scripts\script.sql
>
> So why would login work for the script and not for the dts package?

One cannot accuse me for knowing too much about DTS, but what does
the DTS package do? Does it access the server you connect to only?
/S /U and /P serves to find the package as such, but does not the
package itself log in somewhere? Looks llike this login fails.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]