I built a package on my development server. I backed-up the package using
DTSBackup 2000. I copied the backup to my production server & transfered it
to the local SQL server.
I opened the package an selected each Connection. I confirmed that the Local
server was selected, that the correct database was selected & that the proper
user/password were entered.
I can execute most of the steps in the package. The ones I cannot execute I
receive a Connection Failure error.
When I edit any of the Data Driven Queries I get a Connection Failure when I
select the table in the bindings tab or the Transform tab.
There are 3 seperate connections in the package, identical except for the
name. Each is a Microsoft SQL connection. Each connection uses the same SQL
user.
I have the same user/password and database name on development & production
servers.
I tried building a new (test) package on the production server, & I'm
getting Connection Failures there.
I'm stumped. It must be a security situation on the production server that
I'm unaware of. My development server is W2k & the production server is
Windows 2003.
Thansk in advance for any suggestions.

Sam

Do any packages run against the Product Win3K box?

Ask the Admin to see if you are being blocked on attempt to connect

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Sam" <Sam (AT) discussions (DOT) microsoft.com> wrote

if you use same connection (say conn1) for more than 3 consecutive
transformations in the DTS, you may get this problem. Create another
connection with the same properties and use them alternatively. it should
solve the problem.

"Allan Mitchell" wrote:

I setup a new connection, this did not resolve the problem. I appreciate the
tip, even though I haven't experienced this problem in the past.

When you ask if any packages run against a Win3k box, the answer is mixed.
I've run different packages (much smaller & simplier) on Windows 2003, but I
haven't run this package or one this complex on a Win3k box.

Sam

"athi" wrote: