DTS Connection and SP3a

Question

Post reply

DTS Connection and SP3a

Chris-232075

SSCrazy

Points: 2130
More actions
August 8, 2006 at 11:01 am

#191784

Hi,

SP3a was just downloaded and installed on my instance of SQL Server 2000 - Enterprise Edition (OS is Windows Server 2003). The SELECT ServerProperty('ProductVersion') command confirms that the service pack is installed (8.00.760).

Immediately after installing this service pack, I executed a DTS package, which previously worked flawlessly. Unfortunately, it's now generating the following error:

[DBNETLIB][ConnectionOpen(Connect().)Sql Server does not exist or access denied.

In addition, I can open the package, but when I attempt to look at the properties of any of the Data Transformation Tasks, I get this same error.

FYI, login info was not modified. The only change since last running this DTS package was the installation of this service pack.

I'd appreciate any insight into the possible causes of this problem or how I can approach resolving it. Please know that I'm a database developer, but not a DBA...so be gentle.

Thanks in advance!!!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

lucky-80472 SSCertifiable Points: 7793 More actions · Answer 1

Hello Chris,

Can you run svrnetcn.exe from the command prompt to check whether the default port for TCP/IP is 1433?

You can download a tool from Microsoft to scan your SQL instance

http://www.microsoft.com/downloads/d...displaylang=en

In the meantime, you can go through this discussion chain with the same problem:

http://www.dbforums.com/t976301.html

Thanks

Lucky

Chris-232075 SSCrazy Points: 2130 More actions · Answer 2

Thanks for your reply Lucky.

I ran the executable you suggested, and the default TCP/IP port is 1433.

Unfortunately, according to the Microsoft link you provided, the Microsoft download you recommended (Critical Update Package) doesn't run on Windows Server.

The dbforums thread you provided appears to address my issue, but the KB article that applies, I'm afraid is beyond my expertise. Here's a sample solution from over 20+ possibilities:

You are trying to connect through named pipes, but either the named pipe on which SQL Server is listening has changed from the default, or you are using the incorrect pipe name.
For a default instance, use the following pipe in the Server Network Utility:
\\.\pipe\sql\query
For a named instance, use:
\\.\pipe\MSSQL$instancename\sql\query

???????????

As I said, at this point this appears to be a DTS-only issue that arose immediately after installing SP3a. I'm still dead in the water, so please let me know if you have any suggestions to help me narrow this down.

Thanks again for your time (or anybody else who'd like to chime in)!!!

Chris-232075 SSCrazy Points: 2130 More actions · Answer 3

The cause of my problem turned out to be a network issue unrelated to SQL Server or DTS. Since posting this question, I learned that permissions on the applicable network drive had been changed, coincidentally, at approximately the same time SP3a was being installed. I was unaware of this and assumed that the service pack installation was the cause of my problem. Sorry...I'm in the habit of blaming Service Packs first.

Thanks and sorry for the confusion!