We have migrated a SQL Server based system to a new server. Along with that,
we copied over some very simple DTS packages. They each export data to .txt
files. When I click on the packages to view the design, I can click and see
properties for the Source and Destination nodes but when I try to click and
access properties for the Connection, I get this error window:
Package Error:
Error source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does
not exist or access denied.
Note: This problem does not occur when accessing these packages while on
the Server and it does not occur when I design a new package myself. Only
from my desktop on my PC. I cannot find anything else in Enterprise Mgr for
this group that I cannot access. I hope this is stated clearly.
Thanks for any help.
--
Stan Gosselin

Hello Stan,

So where are you accessing the properties?

It sounds as though there is a reference to a server that the package cannot
now find.

Allan

Alan,
I am trying to acces the Connection properties from my PC within Enterprise
Manager. I right-click on the DTS Package, select Design and that brings up
the GUI design form. I right-click on the Connection bar, select Properties
and get that error. I do not get, that error on the source or destination
node.
If I physically go to the server itself to do this, I do not get the error.
--
Stan Gosselin


"Allan Mitchell" wrote:

Hello Stan,
Then it is looking for a server connection that is not visible from your
PC or if you have used different logins to log on between the server and
your PC and the connections are using Trusted Authenitcation then you are
not wuthenticated.

What is the connections bar?

Allan

Sorry for the terminology confusion. When a DTS package is designed the GUI
shows Connection 1 as the source node, Connection 2 as the destination node
and an arrow or bar representing the transformation or flow of the data. I
can click on Connections 1 and 2 and see the properties of the source and
also the destination of the exported file. The problem occurs when I right
click on the transformation to view the properties or the SQL syntax and
transformation characteristics. That's when the error pops up. If I design
the same DTS package from scratch, I do not get the error. If I remote
desktop into the server, I don't get the error.
Thanks for all the time.
--
Stan Gosselin


"Allan Mitchell" wrote:

Hello Stan,

Ok so here's the thing.

Looking at individual connections like this will not tell you there is a
problem when there is.

I can change a server value to a meaningless value using Disconnected edit
on the connection, open up the connection and see the value. If I hit cancel
here then the connection is not checked. If I hit OK after looking at the
connection then it valiadtes the info and this is where it will error.

If however I try to look at the transform data task itself then the connection
is checked for the source (Because this is where the task opens) and if I
click the destinations tab the destination connection is checked.

what happens in your package when you click OK after looking at the connection?


Have you had a look at the properties in Disconnected Edit?

Allan

Allan,
Thanks for sticking with me. The use of the 'OK' while looking at the
properties of the source connection did the trick. It re-did the validation
and the error became obvious. The server had to be re-specified to the
current server that the system was moved to. My focusing on the properties
of the transformation was actually a 'red herring'.
Thanks again!
--
Stan Gosselin


"Allan Mitchell" wrote: