|
Home > Archive > MS SQL Server ODBC > April 2006 > SQL Server does not exist or access denied
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server does not exist or access denied
|
|
|
| How do I resolve the Micosoft SQL Server Login Error Message Prompts:
Connection fail:
SQLState: 08001
SQL Server ERROR: 17
{Microsoft}{ODBC SQL Server Driver} {TCP/IP Sockets} SQL Server does not
exist or access denied
Regards,
Hal
| |
| Sue Hoegemeier 2006-04-04, 3:23 am |
| Refer to the following troubleshooting article:
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Fri, 31 Mar 2006 21:31:01 -0800, hal
<hal@discussions.microsoft.com> wrote:
>How do I resolve the Micosoft SQL Server Login Error Message Prompts:
>
>Connection fail:
>SQLState: 08001
>SQL Server ERROR: 17
>{Microsoft}{ODBC SQL Server Driver} {TCP/IP Sockets} SQL Server does not
>exist or access denied
>
>Regards,
>Hal
| |
|
|
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
| |
| Sue Hoegemeier 2006-04-05, 8:23 pm |
| 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
<hal@discussions.microsoft.com> 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
| |
|
| Sue,
Do you know of a diagnosis tool to narrow the specific cause
Hal
| |
| Sue Hoegemeier 2006-04-07, 3:25 am |
| It depends on the error. So going back....the thing to do is
work through ALL the steps in the troubleshooting article,
follow all the links in the article, etc. The article is
long because the issue can be one of hundreds of things with
the error SQL Server does not exist or access denied
You need to narrow down the causes by going through the
article.
-Sue
On Thu, 6 Apr 2006 03:41:01 -0700, hal
<hal@discussions.microsoft.com> wrote:
>Sue,
>
>Do you know of a diagnosis tool to narrow the specific cause
>
>Hal
>
| |
|
|
Sue,
I received the following error message on installing MDAC 2.0
MDAC 2.6 Setup
Snap-in failed to initialize
Name Sql Server Configuration Manager
CLSID {CA9F82727-31DF-41D2-975C-887D84903967}
Does this help narrow down the error
Hal
|
|
|
|
|