Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Eric — Mon, 28 Nov 2005 19:01:56 GMT

I am using MDAC OLEDB connection where shared memory is the only enabled protocol.

I am just wondering why "(local)" and "localhost" do not work but <machinename> does? Is there any more information on this? This seems very counter intuitive to me. Is this a problem in Windows 2000 and XP?

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Tue, 29 Nov 2005 07:32:55 GMT

Hi, Eric

MDAC OLEDB uses TCP protocol when you connect through (local) and localhost and in your case, your TCP/IP was disabled, you can verify this by enabling TCP/IP. However, if you specify <machinename>, it connects through shared memory.

Appreciate your comments.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Allen Modine — Thu, 01 Dec 2005 17:57:03 GMT

I am trying to connect to a remote SQL Server 2005 Standard edition server with TCP from a Virtual Machine running XP/VS2005. When I try to add a connection in VS, I get the server name in the database server dropdown list but I get the following error when testing the connection:
"An error has occurred while establishing a connection to the server. When connectiong 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, errror: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.)

On the Sql Server server:
I have the SQLBrowser service running and it is active.
I have the remote connection enabled using TCP/IP only
Connection string I am using from VS2005:
Data Source=W-MODINEDEV;Integrated Security=True;Network Library=dbmssocn

I am at a loss, any help would be appreciated. When I am on the server, making connections works fine, it is just remotely that I have issue. --Allen

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Fri, 02 Dec 2005 04:42:24 GMT

Hi, Allen:
In my another post: http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

I point out the exact case you faced.
Please search Message 11 in the post and follow the resolution.

This is because connection blocked by firewall. To resolve this, take follow steps:

1)Enable SqlBrowser, see the info in Message 4. Plus, add sqlbrowser.exe into Firewall exception list: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List
2)Add Tcp port to Firewall exception list. (eg, Name-1433:TCP, Value-1433:TCP:*:Enabled:Tcp 1433).

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\GloballyOpenPorts\List

For more detailed operation, see http://support.microsoft.com/default.aspx?scid=kb;en-us;287932

If you have further question, please let me know.

Thanks for your comments.
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Allen Modine — Mon, 05 Dec 2005 16:47:55 GMT

Ming:

Thanks for the reply. I would not think this is the problem because I should not be going through the firewall to make a connection to the SQL Server machine, we are both on the same domain and both behind the firewall. Why would I need to do anything with the firewall? Thanks, Allen

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Wed, 07 Dec 2005 21:11:08 GMT

Hi, Allen

Please follow the below step to identify your problem:
1) Make sure SQL Server is listening on the right TCP port. You can check errorlog, and search key words:Server is listening on ['any' <ipv4> <Port Number>] or
[ <ipaddress> <ipv4> <Port Number>]. Then "netstat -ano |findstr <Port>" to see which process is listening on this port.

2)From your client machine, "telnet <ServerIP> <PortNum>" see whether succeeds.

3)Please check whether the windows firewall is on your server. Eg, if your server is XP, then Go to Control Panel -> select "Network and Internet Connection" -> "Windows Firewall", please turn off it if it is on and then try your connection again, if works that means your original connection failure is because the windows firewall on your server blocks any out packet if the application was not added into the exceptionlist since you were making remote connection. I believe the *firewall* that you mentioned is not the same as the windows firewall.

Thanks!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Allen Modine — Wed, 07 Dec 2005 23:09:03 GMT

The Ming Dynasty Rules, you the man, thanks much, and yes, I was thinking "real firewall" versus "windows fiewall" and thought you were crazy, but off course it was me that was foolish.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Vinay — Tue, 20 Dec 2005 08:39:18 GMT

Hi,

Where I can find part III of this series?

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Thu, 22 Dec 2005 07:22:54 GMT

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

Thanks for your comments!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Shawn — Fri, 27 Jan 2006 23:50:03 GMT

Out of all my forum/net searching on this topic, yours by far is the most indepth and well-presented. Good job!

After going through your steps, my problem hasn't gone away. On my development machine, I'm using SQL Server 2005 and the sqloledb provider via C++. This is my connection string:
string ConnectionString2 = "Provider='sqloledb';Data Source='localhost';Initial Catalog='master';Integrated Security='SSPI';";
and it works just fine on that machine.

I've installed SQL Server 2005 Express on two separate machines and it fails in the connnection->Open() call with the standard error: "[DBNETLIB][ConnectionOpen(Connect()).]SQL Swerver does not exist or access denied."

I can connect to the sqlcmd just fine. TCP, Shared, NP are all enabled. The browser is started. The OLEDB provider is correctly pointing to MS's file. The port (1314) is reporting in the App event log and Netstat as listening.

I tried changing <localhost> to machine name, but it didn't help. I did notice in the TCP/IP properties of the Server config mgr that even though TCPIP was enabled, looking at the specific IP address showed that they were active, but disabled. After enabling port there it still didn't help.

Any clues?

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Shawn — Sat, 28 Jan 2006 00:37:17 GMT

On a hunch, I changed my provider from MDAC to Native Client with the string:
"Provider='SQLNCLI';Data Source='localhost';Initial Catalog='master';Integrated Security='SSPI';"

This gave me a more helpful error:
"[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]."

I didn't even know I was using Named Pipes, I thought it would've been defaulting to TCP/IP. Going back to your other article as reference and stepping through the debugging process for named pipes, I couldn't connect with \\.\pipe\sql\query, but I could connect with \\.\pipe\MSSQL$SQLEXPRESS\sql\query.

That seems to have done it, my app works both on the development and test machines.

Thanks for the tips!

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Sat, 28 Jan 2006 01:41:45 GMT

Hi, Shawn

Glad to hear you solve the problem. Basically, SQLEXPRESS is installed as a named instance and with TCP and Named Pipe are disabled by default.

For local connection: You need to change your connection string to:

Provider='SQLNCLI';Data Source=localhost\SQLEXPRESS;Initial Catalog='master';Integrated Security='SSPI'

For remote connection, remember enable tcp or named pipe.

Here is useful info for SqlExpress

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Thanks for your comments!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

rudy — Mon, 20 Feb 2006 13:40:23 GMT

I try to connect to SQL Server 2005 using ADO:

(1)connect to a named instance(mynamedinstance),using SQL Native Client as the driver.

CString strConn =_T("Provider=SQLNCLI;Data Source=mypcname\\mynamedinstance;Initial Catalog=mydb;User Id=myuser;Password=mypw;");
_ConnectionPtr conn("ADODB.Connection");
_bstr_t bstrConn(strConn);
if( FAILED(conn->Open(bstrConn, _T(""), _T(""), 0)) )
{...}

Connect successfully!

(2)connect to the default instance, using SQL Native Client as the driver, but use DSN in the connection string.

CString strConn =_T("Provider=SQLNCLI;DSN=myDSN;Uid=myuser;Pwd=mypw;");
...
...

Connect successfuly!

(3)Conncet to a named instance(mynamedinstance), using SQL Native Client as the driver, using DSN in the connection string.

CString strConn =_T("Provider=SQLNCLI;DSN=myDSN;Uid=myuser;Pwd=mypw;");
...
...

Connect error!!!

Why (3) failed? Please help me.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Thu, 23 Feb 2006 04:42:17 GMT

Provider SQLNCLI does not recognize DSN. So, in the second case, the DSN=myDSN is ignored and, possibly, connection successfully connect to local default instance. In the third case, the DSN=myDSN is ignored as well and connection cannot be established for named instance.

So the short answer is “Do not use DSN when using SQLNCLI provider”.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

GeorgeC — Mon, 06 Mar 2006 05:42:06 GMT

Ming,

I'm getting the error message: "SQL Server does not exist or access denied." I've followed the instructions here as closely as possible. I'm trying to access from a client with MDAC 2.8 SP1 on Windows XP SP2. I checked with netstat -ano on the server, and it's listening on the right IP address and right port. I can connect to an SQL 2000 server just fine.
One possibility is that I installed Windows Server 2003 and SQL 2005 on a new machine and then changed the name of the server.

Any advice would be greatly appreciated.

Thanks,
George C

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Tue, 07 Mar 2006 22:56:36 GMT

Hi, George

Were you trying to connect remotely to SQL Server 2005? Is it default or named instance? Is it SQL Express 2005? How do you make connection?

The MDAC error is very general, if you can provide the above info, we can help you identify the problem quickly.

Thanks for your comments!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Dan — Tue, 28 Mar 2006 16:23:23 GMT

Hi,

I'm having a problem with a .NET 2 command-line app which accesses a SQL 2000 cluster.
If I run it on a Windows 2003 Server SP1 box, it runs fine.
If I run it on a Windows 2000 Server SP4 box, it reports that it can't access the SQL database despite the fact that I can create a DSN on that same box pointing to the db which runs fine and run the .NET 1.1 version of the same app from that box without a glitch. I've run cliconfg.exe and enabled TCP and named pipes but with no avail.

The connection string looks like this. Server=xx;Integrated Security=SSPI;Initial Catalog=name

Any ideas? Does Win2k work differently for .NEt 2.0 than .NET 1.1 somehow?

Cheers, Dan

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Nan Tu — Tue, 28 Mar 2006 21:09:22 GMT

Is the SQL Server named instance or default instance? If it is named instance, you need to enable sql browser service eventthough the client is on the same box of the server. Otherwise, please post the entire exception stack trace of your .Net2.0 app of connection failure.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Dan — Wed, 29 Mar 2006 12:32:39 GMT

It's the name referring to the virtual IP address for a SQL cluster. But its just the default instance on that cluster: CLUSTERDB rather than CLUSTERDB\INSTANCE. That said, do you mean turn on the sqlbrowser on the client or the cluster? Apologies for being dumb, but how do i do either? The Win2k machine has no client tools installed - is part of cliconfg.exe? - and how do ou switch sqlbrowser on for a cluster? - do ou need to switch it on on both machines?

The full error messages I get are as follows - the first is if I try and use named pipes, the second if i use tcp.

-----

Named pipes error message

System.Data.SqlClient.SqlException: 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)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
Boolean& failoverDemandDone, String host, String failoverPartner, String
protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean
encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection
owningObject, Boolean aliasLookup)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)

-----

TCP error message

System.Data.SqlClient.SqlException: Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean
encrypt, Boolean trustServerCert, Boolean& marsCapable)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
Boolean& failoverDemandDone, String host, String failoverPartner, String
protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean
encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection
owningObject, Boolean aliasLookup)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Dave W. — Mon, 10 Apr 2006 18:41:22 GMT

I have a client with 64 bit 2003 server running SQL 2005.
Also has 32 bit XP sp2 client machines that connect fine to the server with OLEDB. When attempting to connect with DMO from the machines with the same credentials and IP, I get
error number: 55555
error source: Microsoft SQL-DMO (ODBC SQLState: 42000)
error description: [Microsoft][ODBC SQL Server Driver][SQL Server]To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).

If I try the same code locally on the server it connects fine.

The client has installed the DMO backwards compatibility patch on both client and server.

I am at wit's end. All protocals on the server are enabled. SQL Browser is enabled on the server. Windows firewall is not enabled on the server.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Tue, 11 Apr 2006 09:02:57 GMT

Hi, Dave

This is not connectivity issue, please post your question to SQL DMO/SMO Forum:

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=88&SiteID=1

Thanks!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Bobikus — Tue, 25 Apr 2006 19:57:02 GMT

Ouyaaaaah!
I solved it! I spent two day by reading many many forums and blogs. Finally I found this stupid error...it must be two backslashes between MachineName and InstanceName in connection string in my application - "<MachineName>\\<InstanceName>".
Everything was enabled, every service ran well but symptoms were identical
So if someone has the same little problem.....

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

bow — Wed, 31 May 2006 10:41:23 GMT

i just test for adding an exception in firewall. Only add sqlbrowser.exe in exception. it's fine. No need to add port 1433 anymore. thank you.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

PRANAV GARG — Mon, 19 Jun 2006 12:37:43 GMT

try to register your sql server on the active directory.
go to the sql server instance name and then right click go to properties and an active directory tab is there click on add and then ok.
try to connect now.
I hope it connects

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Fri, 07 Jul 2006 19:49:54 GMT

Hi,

Can you provide your connection string? The error you saw could caused by various reason:

1) Is your Yukon default instance?
2) What protocol enabled in your Yukon instance?
3) How you make connection? "localhost/127.0.0.1/<FQDN>/<IP>" which one you specified as server?
4) Could you run cliconfg.exe and see what protocol order you specify?
5) Which OS were you running your client APP? WIN2K3?

Thanks!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

su — Sat, 08 Jul 2006 01:15:45 GMT

Hi,

I can't create a DSN using SQL Server to connect to SQL Server 2005, but I can connect successfully using SQL Native Client. My Shared Memory, Named Pipes, & TCP/IP are enabled. My firewall is disabled.

I upgraded SQL Server 2K to 2005 so I have some users who have an DSN using FileMaker SQL Server Driver. I am trying to re-establish that connection but I get:
[ODBC SQL Server Driver] Client unable to establish connection.
[ODBC SQL Server Driver] Unable to load communication module. Driver has not been correct.

I was thinking if I can establish a connection using SQL Server drivers then I can figure out my FileMaker SQL Server Driver issue. The error I'm getting using SQL Server is:
[TCP/IP Sockets]ConnectionOpen(Invalid Instance())
[TCP/IP Sockets]Invalid connection.

Please help.

Thanks
SU

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Sat, 08 Jul 2006 01:51:45 GMT

Hi, Su

From the error message, it looks like that your connection string is not correct, could you provide it to us? Double check following things:

1) Is your SQL 2k5 a default instance or named instance? if named instance, you need add <instancename> in your connection string, like <servername>\<instancename>
2) What is the SKU of your SQL 2k5? Express? Were you making local or remote connection? What OS are you using?

Thanks!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Su — Mon, 10 Jul 2006 03:15:55 GMT

Hi Ming,

I figured out the SQL Server DSN issue. My "Dynamically determined port" was checked with port number 1433 on "Client Configuration", but my TCP Dynamic Ports on SQL 2K5 was 1157.

Now I still have that Filemaker SQL Server Driver issue. I tried connecting using a named instance "DPMMSSQL\MSSQL" and I'm getting [Named Pipes]Specifed SQL server not found. When I use the static IP, I get [ODBC SQL Server Driver] Unable to load communication module. Driver has not been correct.

Could it be that Filemaker SQL server Driver does not support SQL 2K5?

My OS is 64 bit Win2K3 server. All clients are using XP Pro. SQL server 2k5 is 64 bit version 9.00.2047.00.

Thank you so much Ming!
Su

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Tue, 11 Jul 2006 05:26:41 GMT

Hi, su

Glad to hear you address the issue.

I am not sure whether your SQL2k5 is a named instance? And you connect through" DPMMSSQL\MSSQL", is the "DPMMSSQL" the remote machine name? Is the "MSSQL" the instance name of SQL2K5? Can you provide more specifically about your connection string? Means how you make connection?

Can you telnet to your remote server? eg: if your sql server was listening on tcp port 1157, can you run "telnet <remoteservernae> 1157" on your client machine?

Can you try "osql /S<remoteserver>\<instancename> /E" from client machine? what was the error?

What sql protocols enabled on your server?

To identify your problem quickly, could you help to answer following question and provide it to us?

http://blogs.msdn.com/sql_protocols/archive/2006/04/21/581035.aspx

Good Luck!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Su — Wed, 12 Jul 2006 18:44:13 GMT

Hi Ming,

I've called the vendor of that ODBC drive and they don't support 2K5.

My new question is can I backup a DB from 2K5 and restore it on SQL server 2000?

Thanks
Su

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Fri, 14 Jul 2006 06:58:15 GMT

Hi, Su

You can post your question to sql database engine forum, there are a lot of experts who can quickly help you:

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1

Good Luck!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Gabby — Mon, 24 Jul 2006 00:21:33 GMT

hi,
i am having connectivity issues with sql 2000. i have a cgi script that has been accessing this database for production operations and suddenly, it started to return this error

Cannot connect: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation. (SQL-08001)
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (PreLoginHandshake()). (SQL-01000)(DBD: db_login/SQLConnect err=-1)

i have tried everything but restarting the sql server as this server is constanly in use. is there a way to solve this problem? i hav tried using sql ping and i can greac the server, but sqlping also gives the followinh error

Connection error: [DBNETLIB][ConnectionOpen (PreLoginHandshake())

timely response will be grately appreciated

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Mon, 24 Jul 2006 06:52:08 GMT

Hi,Gabby

The error you saw is quit common and it can be mapped to many cases. In most cases, the error happens because the server closes the connection for some reason when client is expecting data from the server.

1) Can you described more about you app? Does the error happen during a long running query? Is the error consistent or intermittent?

2) Which OS your sql server installed? WIN2K3 SP1? Here is a blog that bound to OS specific issue:
http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx

Also, could you check your Server ERRORLOG, what protocls enabled on your server? and whether there is any error info that may give clue? If you were running long query, please open server trace file and watch which operation caused server close connection.

Good Luck!
Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Gabby — Mon, 24 Jul 2006 11:28:19 GMT

thanks a lot Ming,
i actually found out that it was one of the network admins that turned on firewall filtering on the Gateway router. this was actually filtering out MSSQL connections

Thanks a lot for your response

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Greg — Thu, 27 Jul 2006 20:17:54 GMT

Hi Ming,

I have SQL Server 2005 Express installed on a windows server 2003 standard endition. I have configured the firewall according to specs above where I added program exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility.
Here is the strange part: I am able to connect to the Sql Server remotely via Sql Server Management Studio Express, but I am unable to connect to the Sql Server by registering it in Sql Server Enterprise Edition...Is it possible to register the Instance through Enterprise Manager?
Thanks,
Greg

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

pkj — Wed, 02 Aug 2006 10:24:06 GMT

hi,

I am trying to deploy an analysis server cube on a remote server on my LAN. The remote server has firewall off. From the Business development studio I can connect to the remote machine and create data source and data source view. However, when I try to deploy the cube I get the folowing error:

A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running.

I have ensures that the SQL Browser is running. What could be the problem and its solution?

thanks in advance,
PKJ

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Wed, 02 Aug 2006 20:09:42 GMT

PKJ,

Please take a look at the Windows event log on the machine where you have Analysis Server and SQL Browser running to see if there is any error and warning events generated by SQL Browser. If there are, please post a sample of them to help us troubleshoot what the problem may be.

BTW, I would recommend that you continue to have the Windows Firewall on, but put the SQL Server process (sqlservr.exe) and SQL Browser process (sqlbrowser.exe) in the exception list.

Jimmy

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Jeorge Lukasing — Sun, 27 Aug 2006 13:00:53 GMT

Very many thanks for a good work. Nice and useful. Like it!

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Sandy — Wed, 06 Sep 2006 15:33:37 GMT

Hi,

I am trying to deploy a DTSX package to 32-bit SQL Server 2005 in a 64-bit machine from my installer.
I am getting the following error in the SaveToSQLServer method:

The SaveToSQLServer method has encountered OLE DB Error code 0x80004005 (Communication Link Failure). The SQL statement that was issued has failed.

However I am not facing this problem when I try to deploy the DTSX package to a 32-bit SQL Server 2005 in a 32-bit machine.

Can anyone tell me why this happens and how this could be solved?

Thanks,
Sandhya

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

deena — Sat, 11 Nov 2006 14:52:36 GMT

Hi,

I have been running backup on a database(with size more than 20 GB), here I was not able to connect mssql server 2005 thro' management studio.

Event log says the following error

Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: 4%. System Idle: 16%.

However I icreased the worker thread value from 128 to 300, but still problem exists.

After the backup was completed every thing was fine.

Any suggestions would be appreciated.

Thanks

deena

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Deepak sethi — Thu, 16 Nov 2006 15:22:13 GMT

I have just installed SQL SErver 2005,

when i start server management studio, it asks for server registration.

i have downloaded adventureworks x86 from the website. but now i don;t know how to register.

please provide some feedback as i am new toit.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Sun, 19 Nov 2006 10:00:57 GMT

Hi, Deepak

Find the answer from Books Online installed w/ SQL Server 2k5.

Good Luck!

Ming

SQL Server 2005 Remote Connectivity Issue TroubleShoot

SQL Protocols — Fri, 24 Nov 2006 02:23:24 GMT

With shipping SQL Server 2005, we heard from customer feedback about suffering make successful remote

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

ALZDBA — Thu, 07 Dec 2006 17:53:52 GMT

Is there a space for Service Broker connectivity issues ? (... connection forcibly closed ...)

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Sanjay — Fri, 19 Jan 2007 08:13:27 GMT

I am have setup SQL Server 2005 Express on Windows XP Pro SP2 machine. I enabled SQL Server and SQL Server Browser services, configured the firewall. I migrated Access 2002 databases (in linked tables mode) to this SQL server from workstations running XP Pro SP2. All went perfectly well, as planned. The problem is that, we have two W2k Pro machines, and I can not connect these machines to the SQL at all. I can ping the machine running SQL, but can't connect to the SQLEXPRESS.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Mon, 22 Jan 2007 09:02:38 GMT

Hi, Sanjay

Try this blog and follow the best practice:

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

Good Luck!

MIng.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Vijay Anand — Mon, 22 Jan 2007 13:10:33 GMT

I unable to connect to sql from windows 2003 server were as I can able to connect from windows xp

Connection failed:

SQLState: '01000'

SQL Server Error: 53

[Microsoft][odbc sql server driver][dbnetlib]connectionopen(connect())

connection failed:

SQLState: '08001'

SQL Server Error: 17

SQL 2000 client (Eng) to SQL 2005 Server(Korean)

praveen — Tue, 23 Jan 2007 07:47:14 GMT

Hi Guys,

I have a unique problem, i am having SQL Server 2000 client (English Version)running in my machine and i have a SQL Server 2005 (Korean Version). When i try to establish a connection in my enterprise manager i am not able to connect, but the same is getting connected when i try in SQL Query Analyzer.

Can someone help me in resolving the issue.

Thanks

Praveen

help me

Preved — Wed, 24 Jan 2007 16:39:50 GMT

Thank you!

http://symy.jp/?Ct_220745,Thank">http://symy.jp/?Ct_220745,Thank you!

http://symy.jp/?Ct_220745

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Mon, 29 Jan 2007 09:31:42 GMT

Hi, Praveen

Please provide your connection string and the error message you came accross.

If you face further problem, please provide more detail info by following:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

Thanks!

Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Mon, 29 Jan 2007 09:34:16 GMT

Hi, Vijay

Can you provide more detail info by follow up below questions?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

Thanks!

Ming.

SQL Server 2005 Connectivity Issue Troubleshoot - Part I

SQL Protocols — Mon, 29 Jan 2007 09:43:57 GMT

This post provides some tips to troubleshoot Sql Server connection problems based on various displayed

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Aliyah — Sat, 03 Feb 2007 01:13:53 GMT

Help am doing C# and whenever i call store procedure a message come up that i can't open or login.

string connstring = "Data Source =.\\SQLEXPRESS; Initial Catalog=testDatabase; User Instance=True; Integrated Security = True";

SqlConnection connection = new SqlConnection(connstring);

// SqlConnection Connection = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=|DataDirectory|\testDatabase.mdf;Integrated Security=True;User Instance=True");

SqlCommand cmd = new SqlCommand();

SqlDataReader reader;

cmd.CommandText = "StoredProcedure1";

cmd.CommandType = CommandType.StoredProcedure;

cmd.Connection = connection;

// cmd.ExecuteNonQuery();

// connection.Open();

connection.Open();

reader = cmd.ExecuteReader();

// Data is accessible through the DataReader object here.

connection.Close();

where am i going wrong? HELP!!!!!!!!!

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Priya — Tue, 06 Feb 2007 10:43:29 GMT

I am not able to figure out how to use sql express 2005 in client server environment.

I have installed the completed SQLEXpress and Advnaced Sql Express on both machines, enabled all protocols but still not able to connect from client to server.

I also tried SQLEXpress and Advnaced Sql Express on one machine and only Sql NAtive Client on client machine but no success.

What settings needed on server machine and what on client machine?

Can you please help?

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Shane — Tue, 13 Feb 2007 21:41:31 GMT

Ming,

First of all, thank you for this great resource.

We have a strange case with some customers. We are connecting to a local SQL 2005 Express named instance. We are supplying the local server and instance name using "127.0.0.1\TOCTTARGPPC05". Also note we are using Windows Authentication. When we try to connect to the instance using the IP for the local machine we get the error:

[DBNETLIB][ConnectionOpen (Connect()).]Specified SQL Server not found. (6)

We have shared memory, named pipes and tcp protocols enabled. In our troubleshooting we tried using sqlcmd to connect to the database. When we used "127.0.0.1\TOCTTARGPPC05" the connection failed, but when using ".\TOCTTARGPPC05" the connection was established immediately. From our research we noticed that this can occur if the SQL Browser service is not running and in fact we could reproduce this issue on our own machines. However, on the customers machine the SQL Browser service is running and they are still not able to connect using "127.0.0.1\TOCTTARGPPC05". We are currently stumped. Do you have any suggestions?

Thanks,

Shane

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Wed, 14 Feb 2007 08:21:36 GMT

Hi, Shane

Assume your local sqlexpress has np and tcp enabled, and it is listening on a tcp port and named pipe from ERRORLOG.

Can you try:

1) "sqlcmd /Snp:127.0.0.1\TOCTTARGPPC05", what is the error message you got?

2) "sqlcmd /Stcp:127.0.0.1\TOCTTARGPPC05", what is the error message you got?

3) Repeat step 1) and 2) by replace server to

a. "<localmachinename>\TOCTTARGPPCO5"

b. "localhost\TOCTTARGPPCO5"

c. "<ipaddress>\TOCTTARGPPCO5"

Would all of these work?

Is this problem only occur when you were trying "127.0.0.1"?

What OS when repro? WIN2K3? Do you have ipv6 enabled on the box?

Thanks!

Ming.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Peter — Sat, 03 Mar 2007 23:46:14 GMT

I want to know why in Case 2 that SQL Browser service is required when it is dealing with local instance:

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.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

khalid — Mon, 02 Apr 2007 13:45:43 GMT

i am using the following connection string in my desktop application.it works fine with SQL Enterprise edition but when i use it with SQLExpress edition it does not work.

kindly help me how to fix this problem

Provider=sqloledb;Data Source=;Initial

Catalog=HTMS;User Id=HC;Password=123;

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Mon, 02 Apr 2007 22:04:39 GMT

Hi, khalid

Please take a look the blog for best practice of connecting to sqlexpress.

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

Good Luck!

Ming

how to differentiate MS SQL SERVER 2005 named instance and default instance

sethu — Thu, 12 Apr 2007 15:48:54 GMT

i need to differentiate MS SQL SERVER 2005 named instance and default instance

how to differentiate MS SQL SERVER 2005 named instance and default instance

sethu — Thu, 12 Apr 2007 15:52:19 GMT

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.

Why SQL Client cannot connect SQL Server 2005 but OLEDB have no problem to connect SQL 2005

Chandra — Mon, 16 Apr 2007 13:18:49 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

SQL Protocols — Tue, 17 Apr 2007 19:59:35 GMT

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.

Handling and troubleshooting memory issues in a SQL Server 2005 instance

SQL Server Performance and Tuning - (SSQA) — Wed, 20 Jun 2007 12:02:27 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

can anyone help me in this — Wed, 20 Jun 2007 16:53:33 GMT

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: [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 (.\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

Glorf IT - Bedenkliches aus dem IT-Alltag » SQL-Server-2005: immer mit Named-Pipes

Mon, 25 Jun 2007 21:54:30 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Addi — Thu, 16 Aug 2007 21:50:28 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

neklace — Sat, 18 Aug 2007 04:36:43 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Lucas Rodrigues Gonçalves — Thu, 20 Sep 2007 15:25:46 GMT

Congratulations!! Excellent article! Very helpfull!!

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Dale — Mon, 24 Sep 2007 19:01:05 GMT

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.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Ashish Gupta — Sat, 20 Oct 2007 21:43:11 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Bharath — Thu, 15 Nov 2007 13:36:34 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Tom — Sun, 06 Jan 2008 01:24:45 GMT

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Trial

Sadat — Mon, 04 Feb 2008 17:15:41 GMT

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:

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

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

fliben — Tue, 04 Mar 2008 22:39:16 GMT

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.)

SQL2k5 - Named Pipes Provider, error: 40 // Andrea Soto Blog

SQL2k5 - Named Pipes Provider, error: 40 // Andrea Soto Blog — Mon, 10 Mar 2008 22:59:22 GMT

PingBack from http://www.yuibox.com/2008/03/10/sql2k5-named-pipes-provider-error-40/

Programming Links Of The Day, 3/18 « 36 Chambers - The Legendary Journeys

Programming Links Of The Day, 3/18 « 36 Chambers - The Legendary Journeys — Wed, 19 Mar 2008 03:33:23 GMT

PingBack from http://36chambers.wordpress.com/2008/03/18/programming-links-of-the-day-318/

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Eric — Mon, 24 Mar 2008 14:07:07 GMT

Very helpful, I was able to resolve the connectivity issue.

Thank you!

tracker connection error 506

tracker connection error 506 — Wed, 07 May 2008 16:09:44 GMT

PingBack from http://arturo.radiofreemedia.com/trackerconnectionerror506.html

my computer » Re: provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Tue, 20 May 2008 15:56:53 GMT

PingBack from http://www.ie16.com/re-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server/

my computer » Re: Reg: Error while browsing Report server in IIS manager

my computer » Re: Reg: Error while browsing Report server in IIS manager — Tue, 20 May 2008 15:59:14 GMT

PingBack from http://www.ie16.com/re-reg-error-while-browsing-report-server-in-iis-manager/

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

hi — Sat, 04 Oct 2008 04:08:17 GMT

i have installed visual studio 2008 and i can't find sql enterprise manager in it and i have installed query analyzer seperately but when i try to connect it with the database it is throwing error that odbc driver missing or sql server not found.................. kindly suggest me how come i get rid of this problem

DBNETLIB ConnectionOpen error de Red | hilpers

DBNETLIB ConnectionOpen error de Red | hilpers — Sat, 17 Jan 2009 23:11:42 GMT

PingBack from http://www.hilpers-esp.com/709253-dbnetlib-connectionopen-error-de-red

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Leo — Tue, 17 Mar 2009 01:00:37 GMT

I have searched many places and finally got it solved by trying a suggestion here about registration.

I was able to add a SQL Express to a gourp in SQL 2005 Server Management Studio using Windows Authentication. I tried to register the same database using a SQL server user. Testing of registration was successful. But whenever I tried to create an ODBC connection to SQLEXPRESS, I got an error saying that the SQL server does not exist or authentication failed.

What I finally did was to right click the SQL database group or the database, then cilck the option "Update Local Server Registration".

The reason that I tested ODBC connection was the failure of connection when I used connection string in the code.

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Leo — Tue, 17 Mar 2009 01:27:09 GMT

The exact error of mine was "SQL Server does not exist or access denied" after connection is open.

I had connection errors before this error. I cannot remember the exact error messages. I tried suggestions at this site:

http://74.125.95.132/search?q=cache:VWFIV3SxCH4J:blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx+sqlexpress+odbc&cd=3&hl=en&ct=clnk&gl=us

Here is how to enable connections:

Start->All Programs->Microsoft Sql Server 2005

->Configuration Tools-> SQL Server Surface Area Configuration

In the left area:

SQLEXPRESS

Database Engine

->Remote Connections

Enable "Using both TCP/IP and named pipes"

After the change, you can stop/start the service

SQLEXPRESS

Database Engine

->Service

or using command

net stop mssql$sqlexpress

net start mssql$sqlexpress

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Michael Gibson — Wed, 18 Mar 2009 03:00:01 GMT

Just installed SQL Express 2008 - amazing all the tools they include for free now! Your page helped me tremendously. Was troubleshooting connection strings on old .asp code trying to connect to the new DB. Thanks a ton!

Just FYI, I switched from

MyConn.Open("driver={SQL Server};server=ABC

MyConn.Open("driver={SQL Native Client};Data Source=XYZ

(With an appropriately configured DSN)

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

laertejunior — Thu, 21 May 2009 00:29:01 GMT

Hi...We have a VM with Sharepoint connect to another server (SQLSERVER) and sometimes we have this error in

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

But it is not normal and in some hours of day this happend. We have to restart the VM to connect again in sql server. Could be a sql server problem ?

Thanks

re: The troubleshooter has determined that you may not have Internet connectivity. Please make sure that your Internet connection is working by using the Windows network troubleshooter.

Carol — Tue, 26 May 2009 04:57:26 GMT

I already test HTTP Proxy is success connect to MSN messenger services. Test TCP connection unable to connect 8007274c.

SQL Protocols Troubleshoot Connectivity Issue in SQL Server 2005 | Wood TV Stand

SQL Protocols Troubleshoot Connectivity Issue in SQL Server 2005 | Wood TV Stand — Wed, 03 Jun 2009 03:25:35 GMT

PingBack from http://woodtvstand.info/story.php?id=84106

SQL Protocols Troubleshoot Connectivity Issue in SQL Server 2005 | debt settlement program

Fri, 19 Jun 2009 16:47:28 GMT

PingBack from http://edebtsettlementprogram.info/story.php?id=24652

SQL Protocols Troubleshoot Connectivity Issue in SQL Server 2005 | debt consolidator

Fri, 19 Jun 2009 18:41:11 GMT

PingBack from http://mydebtconsolidator.info/story.php?id=3326

re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II

Sumen — Sat, 19 Dec 2009 09:43:13 GMT

http://sqlerrormessages.blogspot.com/2009/12/specified-sql-server-not-found-or-error.html