There are over 20 possible causes listed in the article in
addition to which there are over 20 other links to follow to
try to address the issue. Running just connectivity tests
does nothing. There is just not enough info in your post for
anyone to provide specific steps or fixes. You need to work
through the entire article. Please note all of the different
variables that come into play that you can extrapolate from
reading the article: Protocols, the client, the version of
SQL Server, the edition of SQL Server, DSNs, registry
settings, firewall settings, TCP/IP issues, etc.
-Sue
On Wed, 5 Apr 2006 03:07:02 -0700, hal
wrote:
>
>
>Sue,
>
>Sorry, did not work. Here are the results below
>
>
>Microsoft SQL Server ODBC Driver Version 03.86.1830
>
>Running connectivity tests...
>
>Attempting connection
>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist
>or access denied.
>
>TESTS FAILED!
>
>
>
>
>
>Microsoft SQL Server ODBC Driver Version 03.86.1830
>
>Data Source Name: test
>Data Source Description: test
>Server: DSL-COMPUTER2
>Database: (Default)
>Language: (Default)
>Translate Character Data: Yes
>Log Long Running Queries: No
>Log Driver Statistics: No
>Use Integrated Security: Yes
>Use Regional Settings: No
>Prepared Statements Option: Drop temporary procedures on disconnect
>Use Failover Server: No
>Use ANSI Quoted Identifiers: Yes
>Use ANSI Null, Paddings and Warnings: Yes
>Data Encryption: No >> Stay informed about: SQL Server does not exist or access denied