Hello all,
I've been wrestling with this for a while and hope someone can help.

I have 2 servers - one production, one test.
Both are Win 2003 R2 Std x64 SP2, SQL Server 2005 std 64bit SP3
The production server has multiple instances (5)
The test server has one instance.
They both have SQL 2005 Backward compatability and SQL 2000 DTS
components installed.
On both servers I have 'migrated' a number of DTS packages by opening
the package in SQL 2000 (old server) and saving to the new 2005 64bit
servers.

On the test server I can run the DTS packages from the command line
using dtsrun.
On the production server, if I try to run packages on the named
instance I get :

cmd> DTSRUN /S <server>\<instance> /N "<package_name>" /E
DTSRun: Loading...
Error: -2147467259 (80004005); Provider Error: 17 (11)
Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server
does not exist or access denied.
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0

On the test server I can run packages.

On the production server, if I specify the test server in the DTSrun
command, then the package runs.

When I installed the 5 instances, the first being default, I did not
specify specific ports. So the default instance is running 1433, the
rest are dynamic. There are no firewalls involved and all clients are
on the same domain so I didn't consider it an issue.
The test instance of course is default 1433.

So, maybe I've answered this myself, but it's late and I'm looking for
affirmation or something.

Are dynamic ports my problem ?
and if they are,
Will changing to specific ports upset the current client base - ie,
cause connection issues ?

Any advice gratefully recieved.
N.

Neil Cudd (neil.cudd (AT) blueyonder (DOT) co.uk) writes:
Do you run DTSRUN on the same machine as the instance, or do you
run DTSRUN from a different machine? Is the production server a
cluster?

If you run DTSRUN on the same machine, and it is not a cluster, check
the spelling of the server and instance names.

If you run DTSRUN from a different machine, make sure that the Browser
server is running on the production machine. Can you cannot to the
instance through SSMS and other tools remotely?

If you are on a cluster, you should specify the cluster name, not the
local machine name, I believe.




--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx