Ошибка odbc sqlstate 08001 номер ошибки 17

  • Remove From My Forums

locked

Sql server ODBC connection error «Connection failed: SQLState: ‘08001’ SQL Server Error:17»

  • Question

  • Hi Everyone, 

                   I am having conundrum guys. I recently moved all my access linked database to new NAS device except one client all works fine with database where it comes out with error «

    Connection failed:
    SQLState: ‘01000’
    SQL Server Error: 1703
    [Microsoft][ODBC SQL Server Driver][Multi-Protocol]
    ConnectionOpen(RPCopen())
    Connection failed:
    SQLState:’08001′
    SQL Server Error:11
    [Microsoft][ODBC SQL Server Driver][Multi-Protocol]General 
    network error. Check your network documentation.

            When I test ODBC connection it completes successfully and I also checked permission and seems to be okey and also checked security in
    SQL database it has permission to  connect to corresponding database. To let you know guys I recently changed the password of that machine to blank and urged my colleague to change in next login so is it because of password
    its not connecting. I am using TCP/IP dynamic port in ODBC connection. One thing I dont understand is that why its functioning well in all clients except one which I checked previous day before changing password it was working fine.I am
    using sql server 2000 and access 2003 database.

    GUYS HELP HELP!!!!!

    Cheers

    bis

    • Edited by

      Thursday, June 9, 2011 2:42 PM

Answers

  • What is your client operating system? If it is Windows XP or earlier version, please first check the client settings:

    1. Check your SQL Server Client Network Utility settings.

    Open SQL Server Client Network Utility by running Cliconfg.exe from command prompt on your client machine, selected the General tab and make sure that the TCP/IP protocol and named pipes protocols that your
    SQL Server support are enabled. You can check what the protocols your SQL Server support by running SQL Server Server Network Utility at your server side. Make sure that they are equal and then you can create an alias with the sql server name with a
    specific protocol like TCP and TCP port in the Client Network Utility. The alias must be the name that you used to connect to your SQL Server instance.

    2. If the above does not work, please check if there is any problem of your MDAC with MDAC checker,

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=1953 

    3. Make sure that your client operating system has the latest service pack installed.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help

    • Marked as answer by
      Alex Feng (SQL)
      Monday, June 20, 2011 10:18 AM

Источник
  • Remove From My Forums

  • Question

  • SQL server 2000 with remote clients at 3 locations. Sites had been connected via leased line. We switched everything to internet/VPN. Everything works, but a several times a day, the clients receive this error:

    Microsoft SQL Server Login
    Connection failed:
    SQL State: ‘01000’
    SQL Server Error: 53
    [Microsoft][ODBC SQL Server Driver][DBNETLIB]
    Connection open
    (connect ( ) )
    Connection failed:
    SQL State: ‘08001’
    SQL Server Error: 17

    If they exit and log back in, then it’s OK. Here’s what has changed:

    New ISP at HQ and remote sites with new static IPs. New firewalls/VPN setup. VPNs setup to alloow all traffic between sites. Internal IP addresses/computer names did not change. Only exception is the HQ gateway is different, but all network settings were updated to reflect that. I have all of the remote firewalls pinging the HQ firewall every 30 seconds and have not seen any hint of a problem in the firewall logs. Seems to be isolated to SQL. None of the SQL server or client configs were touched. I know little about SQL. What do the errors above mean and does anyone have any ideas? THANKS!

Answers

  • Hi All,

    This is the Solution on Following Error.

    Connection failed
    SQL State ‘01000’
    SQL Server error 53
    [microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
    Connection failed
    SQL State ‘08001
    SQL Error 17
    [microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

    I have also faced this problem with MSSQL Server 2005 Express Edition then i check connectivity from ODBC i give the solution pls go step by step

    Start => Control Pane => Open Administrative Tools => Data Sources (ODBC)

    u get window with tabs

    Go Tab — User DSN => Click on ADD => opemed window => Create New Data Source => SQL Native Client or SQL Server => Finish

    You find New Window Create New Data Source To SQL Server

    Name = SQLEXPRESS

    Description = SQLEXPRESS

    select Server or type the name of Server with correct path

    Server = COMP1SQLEXPRESS (your computer name SQLEXPRESS)

    Click on Next => On next window you have choose Window or Server Authentication and click on Next

    Now you have find new window with Change Default Database and Attach Database FileName, if you want to chand default db then click and change. go to Next

    On next window you just click on Finish and see the Magic you have find your connectivity.

    Test the Data Source

    Microsoft SQL Native Client Version 09.00.1399

    Running connectivity tests…

    Attempting connection
    Connection established
    Verifying option settings
    Disconnecting from server

    TESTS COMPLETED SUCCESSFULLY!

    if you shown this msg then you have done. and click on ok Button

    you have find your SQL Server added in your ODBC.

    Best of Luck Friends

    • Proposed as answer by

      Thursday, May 7, 2009 8:37 AM

    • Marked as answer by
      Naomi N
      Friday, February 11, 2011 3:47 PM

  • plz help!!fast =)

    If you are using SQL Express 2005 and getting this error, try this. By default after you install the Named Pipe and TCP/IP connections are disabled. Go to SQL Server Configuration Manager, Go to Network Configuration, Click on Protocols and on the right side Right click on the Named Pipes and enable it and do the same for the TCP/IP as well and that should fix the problem.

    • Marked as answer by
      LekssEditor
      Tuesday, October 20, 2009 8:42 AM

Источник
  • Remove From My Forums

locked

Sql server ODBC connection error «Connection failed: SQLState: ‘08001’ SQL Server Error:17»

  • Question

  • Hi Everyone, 

                   I am having conundrum guys. I recently moved all my access linked database to new NAS device except one client all works fine with database where it comes out with error «

    Connection failed:
    SQLState: ‘01000’
    SQL Server Error: 1703
    [Microsoft][ODBC SQL Server Driver][Multi-Protocol]
    ConnectionOpen(RPCopen())
    Connection failed:
    SQLState:’08001′
    SQL Server Error:11
    [Microsoft][ODBC SQL Server Driver][Multi-Protocol]General 
    network error. Check your network documentation.

            When I test ODBC connection it completes successfully and I also checked permission and seems to be okey and also checked security in
    SQL database it has permission to  connect to corresponding database. To let you know guys I recently changed the password of that machine to blank and urged my colleague to change in next login so is it because of password
    its not connecting. I am using TCP/IP dynamic port in ODBC connection. One thing I dont understand is that why its functioning well in all clients except one which I checked previous day before changing password it was working fine.I am
    using sql server 2000 and access 2003 database.

    GUYS HELP HELP!!!!!

    Cheers

    bis

    • Edited by

      Thursday, June 9, 2011 2:42 PM

Answers

  • What is your client operating system? If it is Windows XP or earlier version, please first check the client settings:

    1. Check your SQL Server Client Network Utility settings.

    Open SQL Server Client Network Utility by running Cliconfg.exe from command prompt on your client machine, selected the General tab and make sure that the TCP/IP protocol and named pipes protocols that your
    SQL Server support are enabled. You can check what the protocols your SQL Server support by running SQL Server Server Network Utility at your server side. Make sure that they are equal and then you can create an alias with the sql server name with a
    specific protocol like TCP and TCP port in the Client Network Utility. The alias must be the name that you used to connect to your SQL Server instance.

    2. If the above does not work, please check if there is any problem of your MDAC with MDAC checker,

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=1953 

    3. Make sure that your client operating system has the latest service pack installed.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help

    • Marked as answer by
      Alex Feng (SQL)
      Monday, June 20, 2011 10:18 AM

Источник
  • Remove From My Forums

locked

Sql server ODBC connection error «Connection failed: SQLState: ‘08001’ SQL Server Error:17»

  • Question

  • Hi Everyone, 

                   I am having conundrum guys. I recently moved all my access linked database to new NAS device except one client all works fine with database where it comes out with error «

    Connection failed:
    SQLState: ‘01000’
    SQL Server Error: 1703
    [Microsoft][ODBC SQL Server Driver][Multi-Protocol]
    ConnectionOpen(RPCopen())
    Connection failed:
    SQLState:’08001′
    SQL Server Error:11
    [Microsoft][ODBC SQL Server Driver][Multi-Protocol]General 
    network error. Check your network documentation.

            When I test ODBC connection it completes successfully and I also checked permission and seems to be okey and also checked security in
    SQL database it has permission to  connect to corresponding database. To let you know guys I recently changed the password of that machine to blank and urged my colleague to change in next login so is it because of password
    its not connecting. I am using TCP/IP dynamic port in ODBC connection. One thing I dont understand is that why its functioning well in all clients except one which I checked previous day before changing password it was working fine.I am
    using sql server 2000 and access 2003 database.

    GUYS HELP HELP!!!!!

    Cheers

    bis

    • Edited by

      Thursday, June 9, 2011 2:42 PM

Answers

  • What is your client operating system? If it is Windows XP or earlier version, please first check the client settings:

    1. Check your SQL Server Client Network Utility settings.

    Open SQL Server Client Network Utility by running Cliconfg.exe from command prompt on your client machine, selected the General tab and make sure that the TCP/IP protocol and named pipes protocols that your
    SQL Server support are enabled. You can check what the protocols your SQL Server support by running SQL Server Server Network Utility at your server side. Make sure that they are equal and then you can create an alias with the sql server name with a
    specific protocol like TCP and TCP port in the Client Network Utility. The alias must be the name that you used to connect to your SQL Server instance.

    2. If the above does not work, please check if there is any problem of your MDAC with MDAC checker,

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=1953 

    3. Make sure that your client operating system has the latest service pack installed.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help

    • Marked as answer by
      Alex Feng (SQL)
      Monday, June 20, 2011 10:18 AM

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Ошибка no database selected как исправить
  • Ошибка odbc sqlstate 01000 номер ошибки 0
  • Ошибка no bootable device на ноутбуке acer что делать
  • Ошибка od off хендай акцент
  • Ошибка no bootable device is detected system will enter the bios setup utility как исправить

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии