March 23, 2004 at 1:24 pm
I am experiencing a problem with the SQL Enterprise Manager (EM) not allowing me to access the Transform Data Task Properties Step of a DTS Package. The DTS Package was created via a Terminal Services connection and it appear I can not access this particular step via an Enterprise Manager Connection. SQL EM returns the following error messags:
Error Description [DBNETLIB][ConnectionOpen(Connect()).] Sql server does not exist or access denied.
Please help!
Thanks in advance, Kevin
March 23, 2004 at 1:55 pm
Possibly you created the dts using Windows Authentication for the db connection, and from your machine you cannot authenticate against the SQL server using Windows Auth.
March 23, 2004 at 3:22 pm
In this case you state is was create via Terminal Services to the box. What most likely is occurring is the SQL Connection is defined with something that doesn't work on your local box. For instance the developer could have defined the Server as (local) whihc means unless you are on the server it cannot find it. Or it could be he used a Friendly name in Client Network Utilities on the server that doesn't exist on yuor box, all you have to do then is create a connection for the same firendly name on your machine in Client Network Uitilites. Then also as suggested if you don't have an account on the box with the same userid and password for the OS as you local machine or it is using Domain Accounts and your machine is not connected to the domain it will not authenticate.
June 28, 2004 at 9:46 am
I had the same error message and my problem had to do with conflicting protocols. When I added "Network=DBMSSOCN;" to my connection string my page started working again.
I got my information through the microsoft website: http://support.microsoft.com/defaul...kb;EN-US;328383
Here is what helped me:
Specify the protocol in your connection string. For example: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBaseName;Network=DBMSSOCN;Address=IP_Address,1433;UID=YourUID;PWD=YourPassword;"
In this example, you specify the network protocol as "DBMSSOCN", which means that you want to use the TCP/IP protocol. If you specify the protocol inside your connection string, Dbnetlib only uses the specified protocol and does not try any other protocol.
Similarly, to enable Named Pipe protocol only, use a connection string similar to this: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBaseName;Network=DBNMPNTW;Address=\\.\pipe\sql\query;UID=YourUID;PWD=YourPassword;"
Hope this helps!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply