Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Tom.Hiscox
Starting Member
12 Posts |
 Posted - 2001-02-15 : 13:14:48
|
| Hi All,I have had a few problems with instances of SQL Server.I have a DTS package (in MSDB) which is scheduled, and hence using the CmdExec with the DTSRUN utility.I have one server which only has SQL 7 on:If I run DTSRUN /S TESTDB /U sa /P password /N package namewhere the package name doesn't exist, I get an error "package name doesn't exist in msdb etc." I get this if I run it both from the command prompt directly and from the SQL Server Job. This is fine.However, I have another server that has SQL 7 on it, and also a named instance of SQL 2000. If I run the same code as before it works from the command prompt, but not from within the SQL Server Job, where I get an OLEDB "Login failed for user 'sa'" error. If I create an alias for my SQL 2000 instance called TESTDB2000, and run DTSRUN /S TESTDB2000 /U sa /P password /N package nameit works fine both from the Job, and the command prompt.Can anyone tell me why I should get a login failure from the SQL Server Job, but not from the command prompt apparantly only because I also have a named instance of SQL 2000 running.P.S. Both servers are running Windows 2000 AS, Sql Server 7 sp2, and the 2nd has SQL Sever 2000 Enterprise. Both servers are identical.If anyone can help you're a lifesaver!!Regards,Tom |
|
|
|
|
|
|
|
Scheduling a DTS Package on SQL 7