Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

  • Comments 98

Please visit http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx for troubleshooting connection problems when SNAC(SQL Native Client) connect to SQL Server 2005.

Part II – Connection Fail when MDAC connects to SQL Server 2005

 

Use osql.exe to simulate the connection string in your application and quick troubleshoot if your application uses ODBC provider and use Query Analyzer (isqlw.exe) in SQL Server 2000 for OLEDB provider. Usually, they are located under %SYSTEMDRIVE%\Program Files\Microsoft SQL Server\80\tools\binn.

 

How to distinguish your application is using MDAC client or SNAC client:

1) From connection string, especially follow blue part:

 

- MDAC ODBC -

DRIVER= {SQL Server}; SERVER=xx; Trusted_connection=yes; Connect Timeout=30

 

- MDAC OLEDB –

Provider= SQLOLEDB; Data Source=xx; Integrated Security=SSPI;Connect Timeout=30

 

- SNAC ODBC –

DRIVER= {SQL Native Client}; SERVER=xx; Trusted_connection=yes; Connect Timeout=30

 

- SNAC OLEDB –

Provider=SQLNCLI; Data Source=xx; Integrated Security=SSPI; Connect Timeout=30

 

2) From error message:

Osql /Sxxx /E ß “xxx” is an unknown server

 

Result of using MDAC client:

 

[DBNETLIB]SQL Server does not exist or access denied.

[DBNETLIB]ConnectionOpen (Connect()).

Or

[DBNETLIB]Specified SQL server not found.

 

Result of using SNAC client:

 

Named Pipes Provider: Could not open a connection to SQL Server [53]

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

 

Basic connection string:          osql(sqlcmd) /S[prefix]<servername> /E

                                                osql(sqlcmd) /S[prefix]<servername>\<Instance> /E

 

Before start troubleshooting, another important thing is to identify MDAC version on your client box.

 

Step 1: Browse to the following Microsoft Web Site to know about MDAC release version.

http://support.microsoft.com/default.aspx?scid=kb;en-us;231943

Step 2: Browse to the following Microsoft Web Site to download the tool that help you check the MDAC version on your client box.

http://support.microsoft.com/default.aspx?scid=kb;en-us;301202

 

However, MDAC does not provide so many visible error messages like SNAC, which makes it more difficult to troubleshoot connection problems when using MDAC connect against Yukon. Most likely, any of the follow three errors you would see in any case. Therefore, I will give tips for troubleshooting not based on the messages, but, on various Protocols Setting in SQL Server 2005.

 

Message 1:

[DBNETLIB]SQL Server does not exist or access denied. 

 

Message 2:

[DBNETLIB]Specified SQL server not found.

 

Message 3:

[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.

 

Before further troubleshooting, you need to know what is the current protocol setting on the server box, and make sure server is running and sqlbrowser service is running, two ways to check.

 

1) Go to SSCM( SQL Server Configuration Manager ), click “protocols for  <Instance>”, you can see the status of each protocol that server support.

2) Look at server ERRORLOG file.

 

- Key words indicates server shared memory is enabled -

“Server local connection provider is ready to accept connection on [\\.\pipe\SQLLocal\MSSQLSERVER]” or [ \\.\pipe\SQLLocal\<InstanceName>]

 

- Key words indicates server named pipe is enabled -

Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$<InstanceName>\sql\query ] or [ \\.\pipe\sql\query ]

Note: you may also see these key words even when only shared memory is enabled. To make sure server remote named pipe is enabled, you need to do one more thing, test connection through named pipe. “osql /S\\<machinename>\pipe\sql\query /E” or

“osql /S\\<machinename>\pipe\MSSQL$<InstanceName>\sql\query /E” only when the connection succeeds that means server is listening on name pipe.

 

- Key words indicates server TCP/IP is enabled –

Server is listening on ['any' <ipv4> <Port Number>] or

[ <ipaddress> <ipv4> <Port Number>].

First one is when enabling server “ListenonAllIPs”, and second one is when server listening on individual IP. To further verify, you can test whether sql server is listening on the exact port using "netstat -ano| findstr <PortNumber>". 

 

Thereby, the following troubleshooting tips would be based on which protocol was enabled. When you came across connection failure, please first identify what is the current protocol configuration on your server box.

 

Note: only when I explicitly point out named instance, otherwise, all cases apply to both default instance and named instance. And, normally, there are three parts in “Server” or “DataSource” field in the connection string. [<Prefix>]<Server>\[<InstanceName>], in the server part, it could be any of those:

  1. “.”
  2. “(local)”
  3. “localhost”
  4. <machinename>
  5. “127.0.0.1”
  6. FQDN(Server Fully Qualified Domain Name)
  7. <IpAddress>

 

Assumption: Follow situation are mainly cover MDAC 2.8/2.81/2.82 client connects against Yukon RTM on Windows 2000/Windows 2003/Windwos XP.

 

Case 1 – Only shared memory was enabled:

 

Go through follow reason list:

 

1) You might specify “tcp:” in your connection string, however, TCP was disabled, to resolve this, remove the prefix.

 

2) You might specify ”np:” in your connection string, plus, specify localhost or FQDN or “127.0.0.1” or <ServerIP> in the server part in Server or DataSource field in your connection string, to resolve this, either enable name pipe or specify <machinename> as Server part.

 

3) You might specify localhost or FQDN or “127.0.0.1” or <ServerIP>, to resolve this specify <machinename> as Server part.

 

4) You might specify “lpc:” in your connection string, plus, specify localhost or FQDN or “127.0.0.1” or <ServerIP> in the server part in Server or DataSource field in your connection string, to resolve this, specify <machinename>  instead as Server part.

 

5) You might first, use OLEDB provider; secondly, connect to local default instance through "." or "(local)", to resolve this, replace the server part as <machinename>.

 

Case 2 – Shared Memory and TCP/IP was enabled, but Named Pipe was disabled.

 

Go through follow reason list:

 

1) You might specify ”np:” in your connection string, plus, specify  localhost or FQDN or “127.0.0.1” or <ServerIP> in the server part in Server or DataSource field in your connection string, to resolve this, either enable name pipe or specify <machinename> as Server part.

2) You might specify “lpc:” in your connection string, plus, specify in the server part in Server or DataSource field in your connection string. To resolve this, replace to <machinename>.

 

Case 3 - Shared Memory and Named Pipe was enabled, but TCP/IP was disabled.

 

Go through follow reason list:

 

1) You might specify “tcp:” in your connection string, however, TCP was disabled, to resolve this, remove the prefix.

2) You might first, use OLEDB provider; secondly, connect to local default instance through "." or "(local)", to resolve this, replace the server part as <machinename>.

 

Case 4 – Only Named Pipe was enabled.

 

Go through follow reason list:

 

1) You might specify “tcp:” in your connection string, however, TCP was disabled, to resolve this, remove the prefix.

2) You might first, use OLEDB provider; secondly, connect to local default instance through "." or "(local)", to resolve this, replace the server part as <machinename>.

 

Case 5 – Only TCP was enabled.

 

Go through follow reason list:

1) You might specify “np:” prefix in your connection string, Named Pipe was disabled. To resolve this, remove the prefix.

 

Case 6 – Only Shared Memory was disabled.

Case 7 – All protocols are enabled.

 

All connection in Case 6 and Case 7 should succeeds unless some special cases.

 

Special Cases:

 

Case 1: localhost

 

Windows 2000 and Windows XP do not recognize “localhost” as a representative of local machine in pipe name. In another word, you can not connect  to default instance through explicit pipe \\localhost\pipe\sql\query( eg, you connection string like "Data Source = \\localhost\pipe\sql\query; Integrated Security = SSPI" or "osql /S\\localhost\pipe\sql\query /E") on Win2k and WinXP when remote name pipe was enabled.

 

Case 2: Connect to local named instance

 

If you can not identify cause for connection fail when use MDAC connecting to local  named instance, there are two other possible reasons:

1) Your application was running under an account that has no permission to the registry entry where MDAC client reads (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceName>\MSSQLServer).

2) SQL Browser service was not enabled or running.

 

Case 3: Remote Connection

 

Whenever remote connection fail and you saw any of above error messages, you should first check whether remote named pipe or tcp was enabled or sqlbrowser service was enabled and running. Please see “SQL Server 2005 Connectivity Issue TroubleShoot –Part I” for more detail info.

 

Case 4: Blank

 

If you use ODBC driver and leave the server part as blank when connecting to local default instance, connection would fail. Please explicitly specify server name whenever make connection. The error message when connection fail usually is “[Microsoft][ODBC SQL Server Driver]Neither DSN nor SERVER keyword supplied ”.

 

Case 5: "." or "(local)"

 

To emphasize this, if you use MDAC OLEDB, you can not connect to local default instance through "." or "(local)" whenever TCP was disabled on the Server. To resolve this, please use <machinename> instead.

 

Summary:

 

When you discover any connection fail through MDAC client to SQL Server 2005, please first make sure server is accessible and SQL instance is running; secondly, identify which protocol is enabled; finally, go through above scenarios to track the root cause.

 

Ming Lu SQL Server Protocols

Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights

 

Leave a Comment
  • Please add 6 and 7 and type the answer here:
  • Post
  • i need to differentiate MS SQL SERVER 2005 named instance and default instance through c# code..

    This is needed to attach the data base with server.  that is i have to know  whether i have to give (local) or (local)\SQLEXPRESS at the time attaching the data base.

  • Hello,

    I have some problem here...

    When I use Server Explorer on Microsoft Visual Studio .NET 2005, I can't connect the SQL Server 2005 with Data Source : Microsoft SQL Server (SqlClient) but when I use Microsoft SQL Server (OLE DB) its work, its also happening when I make a connection test using udl file.

    why this problem happening?

    Thank for your help. Thank You

  • Hi, Chandra

       Please check out the blog according to the error message that you saw from sql client.

       http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx

    Good Luck!

    Ming.

  • We had a major issue on one of the SQL Server instance with the memory and getting following error message

  • Database access error. Reason [Microsoft][SQL Native Client]Communication link failure.

    Webi report server log

    (.\infostore.cpp:265): trace message: CInfoStore::Query: SELECT SI_SERVER_NAME,SI_CLUSTER_NAME,SI_SERVER_IS_ALIVE,SI_SERVER_IOR,SI_SYSTEM_INFO FROM CI_SYSTEMOBJS WHERE (SI_PARENTID = 16 AND SI_SERVER_KIND = 'aps') OR SI_ID = 4

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: UNV_Manager:originalReportFilePath:frs://Input/a_068/001/000/324/test_universe.unw

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: UNV_Manager:tempFileName:

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: FSFactoryListener_impl::GetNewServiceHelper: Asking for filestore from server Input:Input.alg1101rh2boa01..

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  UNV_Manager:attachHelper: 0.015

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1644). (false : TraceLog: **ASSERT:UNV_CacheManager:copy Universe file failed... [UNV_CacheManager.cpp;210]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  UNV_CacheManager:UNWCacheManager::DownloadFile: 0.031

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:The universe cache manager failed to download file.. [UNV_Manager.cpp;1758]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [ENTER] UNV_CacheManager:UNWCacheManager::DownloadFile

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [ENTER] UNV_Manager:attachHelper

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: UNV_Manager:originalReportFilePath:frs://Input/a_068/001/000/324/test_universe.unw

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: UNV_Manager:tempFileName:

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  UNV_Manager:attachHelper: 0

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1644). (false : TraceLog: **ASSERT:UNV_CacheManager:copy Universe file failed... [UNV_CacheManager.cpp;210]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  UNV_CacheManager:UNWCacheManager::DownloadFile: 0.016

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:The universe cache manager failed to download file.. [UNV_Manager.cpp;1758]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:Failed at : -2147206823 [UNV_Manager.cpp;1986]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:HRESULT : -2147206823 [UNV_Manager.cpp;1986]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  UNV_Manager:ImportUniverseFromCE: 0.062

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  UNV_Manager:GetUniverseFromCache: 0.062

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  UNV_Manager:LoadUniverseHeader: 0.062

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [ENTER] QT_LocalServer:SetErrorMessage

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: QT_LocalServer:An error occurred, the corresponding message will be set in the TLS

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: QT_LocalServer:Error Code:506

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ctResourceBundle:Message bundle loaded::qtserver_error_en_

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:[Cdztools Error Trace:BEGIN]

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:PREFIX:ERR

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:COMPONENT:WIS

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:ERRORCODE:506

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:ERRORTYPE:USER

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:MESSAGE:Could not download the universe test_universe from the CMS for the following reason: . See your Business Objects administrator for further information. (Error: WIS 00506)

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:BORESULT:89

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:MODULENAME:QTServer

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:FILENAME:QTLocalServer.cpp

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:LINEPOSITION:1770

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:DPNAME:

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:DPLONGNAME:

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:DPID:

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:COMMANDNAME:

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:COMMANDID:

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ct_cdz_error_context:[Cdztools Error Trace:END]

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ctResourceBundle:Message bundle released::qtserver_error_en_

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: ctResourceBundle:Message bundle released::qtserver_error_en_

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  QT_LocalServer:SetErrorMessage: 0

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  QT_LocalServer:GetUniverseParameters: 0.062

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:C3_cdbQTServer:m_pQT->GetUniverseParameters : -2147206823 [kc3qtds.cpp;3911]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  C3_cdbQTServer:LoadUniverseConnection: 0.062

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:C3_cdbQTServer:LoadUniverseConnection failed [kc3qtds.cpp;5389]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  C3_cdbQTServer:_LoadDictionary: 0.062

    [Wed Jun 20 08:04:08 2007]      4920    6528    assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:C3_cdbQTServer:m_pServer->_LoadDictionary(*m_pDict); failed : -2147467259 [kc3qtds.cpp;2801]).

    [Wed Jun 20 08:04:08 2007]      4920    6528    trace message: TraceLog: [EXIT]  C3_cdbQTServer:tbQTDS_CreateObjects: 0.062

    Input FRS log

    Timestamp       ProcessID       ThreadID        Message

    [Wed Jun 20 07:58:06 2007]      7072    7896    (.\nsclient.cpp:2037): trace message: Name server communication failed.  Reconnect...

    [Wed Jun 20 07:58:06 2007]      7072    7896    (.\nsclient.cpp:224): trace message: NSCLIENT: Do connection to alg1101rh2boa01.connectprod.connect.bt.com.  Last successful connection to ALG1101RH2BOA01.CONNECTPROD.CONNECT.BT.COM

    [Wed Jun 20 07:58:06 2007]      7072    7896    (.\oscafactorymgr.cpp:1318): trace message: DONT CALL DONT CALL DONT CALL DONT CALL

    [Wed Jun 20 07:58:07 2007]      7072    7896    trace message: SIWarning: ResolveSocket failed!

    [Wed Jun 20 07:58:07 2007]      7072    7896    trace message: CNSClientManager::DoConnectToAps(): failed to retrieve aps factory handle from aps alg1101rh2boa01.connectprod.connect.bt.com.

    [Wed Jun 20 07:58:07 2007]      7072    7896    (.\oscafactorymgr.cpp:1318): trace message: DONT CALL DONT CALL DONT CALL DONT CALL

    [Wed Jun 20 07:58:08 2007]      7072    7896    trace message: SIWarning: ResolveSocket failed!

    [Wed Jun 20 07:58:08 2007]      7072    7896    trace message: CNSClientManager::DoConnectToAps(): failed to retrieve aps factory handle from aps alg1101rh2boa01.connectprod.connect.bt.com:6401.

    [Wed Jun 20 07:58:08 2007]      7072    7896    trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com from m_ActiveMembers and adding to m_InactiveMembers

    [Wed Jun 20 07:58:08 2007]      7072    7896    trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com:6401 from m_ActiveMembers and adding to m_InactiveMembers

    [Wed Jun 20 07:58:08 2007]      7072    7896    trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com from m_ActiveMembers and adding to m_InactiveMembers

    [Wed Jun 20 07:58:08 2007]      7072    7896    trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com:6401 from m_ActiveMembers and adding to m_InactiveMembers

    [Wed Jun 20 07:58:08 2007]      7072    7896    (.\nsclient.cpp:237): trace message: NSCLIENT: no valid APS available to connect to

    [Wed Jun 20 07:58:08 2007]      7072    7896    (.\nsclient.cpp:2069): trace message: Failed to connect to name server: Transport error: unable to retrieve the CMS factory. (44)

    [Wed Jun 20 07:58:52 2007]      7072    5016    trace message: FileResourceMgr::cleanup: Going thru maps of readers and writers

  • PingBack from http://www.glorf.it/blog/2007/06/25/sql-server/sql-server-2005-immer-mit-named-pipes

  • My application is losing connectivity while being installed / running on same machine as SQL Server.

    SQL Error! SQL State: 01000, ErrorCode 10054, ErrorMessage: [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).

    Any ideas.

    Addi

  • Respected Sir,

    I face a problem .please read it and email me its solution as soon as possible.

    This is problem.

    An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes Provider,error:40-Could not open connection to SQL Server))

    I try to serach from google its solution ,but i can not find its solution.

    Try this link.i do every thing which tell in this link but my problem still remain.

    http://www.datamasker.com/SSE2005_SAC.htm

    2) Problem

    SQL Server(SQLEXPRESS) is in stop state .when i try to change its state from stop to start it generate error & do not change its state stop state to start state.kindly please sole my these problems.

    I will be thankful to you.

    Best Regards

  • Congratulations!! Excellent article!  Very helpfull!!  

  • I'm using classic ASP to connect using the following connection string:

    Conn.open "Provider=sqloledb;Server=server;Initial Catalog=db;UID=;PWD=;

    But I'm getting the following error:

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

    Note: This *was* working at one point, but something changed on the database machine and I can't figure out what changed.

  • Unique Issue :

    I can connect to SQL Server 2005 using 32 bit processor but when i tries the same application from 64 bit processor machine i recived remote connections not allowed by sql server error.

    Please help

  • An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)

    what this means

  • I installed SQL Server 2005 Standard on Windows Vista Business. I am using Sql Server Management Studio and have no problem connecting to my local database. However, I keep getting the following error when trying to connect to a remote SQL Server. I can connect fine under XP with SQL 2000 Enterprise Manager. Here's the error message I get:

    "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 1214)"

    I have tried the following, based on reading your blog and suggestions by others:

    1) Using Surface Area Configuration, enabled remote connections through both TCP/IP and named pipes

    2) Using Surface Area Configuration, granted sysadmin priveleges to my admin user account

    3) Using SQL Server Configuration Manager, created an alias specifying the tcp protocol, server name, and port number required by the SQL server

    4) Created exceptions for sqlservr.exe and sqlbrowser.exe in the Windows Firewall

    5) Using SQL Server Configuration Manager, enabled shared memory, TCP/IP, and named pipes in both SQL Server 2005 Network Configuration and SQL Native Client Configuration

    6) Temporarily disabled the Windows Firewall completely

    Despite all of this I am still getting the same error message. Did I leave out something important?

    Any help would be appreciated...I've been at this for several days.  Thanks, Tom

  • I have XP/SP2 laptop. I downloaded the trial edition. When I click on the Management Studio, the dialog box asks for server name. The computer name is shinaspc. I installed XP as a standalone workgroup. I get the error message:

    "An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)"

    I cannot create any new database or start learning from samples. Please help.

  • Setup is web farm accessing SQL 2055 through a firewall with port 1433 open to the sql 2005 machine and all ports from SQL network open. Windows firewalls are turned off. SQL accepts remote connections and is set for port 1433.

    I am seeing the below error randomly on connections to our SQL 2005 Std server.

    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

Page 5 of 7 (98 items) «34567