Connection Failure question

  • We have a custom VB6 application. Using MDAC 2.6 we connect to a Clustered SQL2k SP2 Backend. After pushing MDAC 2.6 to all our users we started getting random errors with the following message:

    [Microsoft][ODBC SQL Server][TCP/IP Sockets]SQL Server does not exist or access denied.

    I have searched MS KB and other resources and have found little or no mention of this.

    Any thoughts on this?

  • Look into your Client Network Utility and see if you are using Name Pipes -vs- TCP/IP.

    And Check your odbc configuration to ensure you have a valid ID hitting against SQL Server.

    -JG


    -JG

  • We are using sockets. A registry key was ran on all systems mapping the name/instance to the <old name>. So that all the connection strings would not have to be changed on all systems.

  • You say you mapped the old name to the new instance in the registry. Exactly how was this done. The old name to the TCP/IP address or based DNS address entry?

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

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

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