Anybody can pls solve this ? SQL Server - Connection Err

[mdrafik]

Hi,
We hv 3 databases in our sql server 7 machine and using for different projects such as c/s & web based applications. We hv connected the server with more than 10 clients and were working fine without any probs so far.

Suddenly, one day while trying to connect with server, we r getting error like.....

----------------------------------------------
Unable to connect server \\machinename

Server : Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General Network error.
Check your network documentation.
----------------------------------------------

The same error comes while we trying to connect database in server m/c itself. But, i can ping my server name from any client even from server m/c itself and it pinging successfully,returns ip address of server m/c.

I just gone thru books online.. But couldn't get proper idea. Since, no sql admin in our team, Kindly help us in this regard....

Any Suggestions would be appreciated.

Thanks & Regards,

Rafik.

[peet]

Have you searched the MSDN ?

If not, I got a couple of hits while searchin. I'm not to much into networking though...

If u havent got the MSDN, I will gladly post the results.
They didn't tell ME much, but it might mean something to you.

[JoshT]

Make sure the SQL server service is running or if it crashed or something. I've gotten that error, but it was because I changed the name of the computer, which causes SQL server not to be able to run until you reinstall it.

[mdrafik]

Thanx for u'r replies Mr. Peet & Mr. Jose.

Hi Mr.Peet,
I hv not tried it in MSDN, pls send me the results u got reg that.


Hi Mr.Jose,
As u told me, i hv not changed my server name, it was working 2 days b4. Don't know, anybody has done anything on it.

But, still it has same server name when it was working.
Also, I can ping my server name from any client even from server m/c itself and it pinging successfully,returns ip address of server m/c.

Pls provide further suggestions.

Thanx in advance.


Rafik.

[peet]

ok, what i searched for was : "[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General Network error"

I got 4 hits, and they showed as follows

Result 1:

MSDN :

Error 80004005 Occurs When You Manage Departments, Create Products Manually, or Re-categorize Assets

Q264031


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Digital Broadcast Manager for Windows Media, version 1.0

--------------------------------------------------------------------------------


SYMPTOMS
When you manage departments, create products manually, or re-categorize assets, you may receive the following error message:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.
/dbmadmin/include/Manager.asp, line 101



CAUSE
This error message is caused by a loss of network connectivity between Digital Broadcast Manager and Microsoft SQL Server.



RESOLUTION
Perform standard network troubleshooting procedures, such as verifying that the physical link has not been disturbed, or that TCP/IP connectivity has not been disrupted.



STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.



MORE INFORMATION
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q102908 How to Troubleshoot TCP/IP Connectivity with Windows NT
Q143351 How to Check Network Connectivity Using Net Diagnostics
Q146816 IIS Troubleshooting With ODBC SQL Integration

Additional query words: netshow wms wmt wmp tshoot

Keywords : prodsitesrv3 prodCS kbwms40 kbwms41
Issue type : kbprb
Technology : kbvcSearch


Last Reviewed: June 6, 2000
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.




--------------------------------------------------------------------------------
Send feedback to MSDN.Look here for MSDN Online resources.

[peet]

Result 2:

MSDN:
Error 80004005 Occurs When You Select Manage Assets

Q264051


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Digital Broadcast Manager for Windows Media, version 1.0

--------------------------------------------------------------------------------


SYMPTOMS
When you click Site Manager, and then select Manage Assets, you may receive the following error message in the Digital Broadcast Manager Administrator page:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network Documentation.
/dbmadmin/include/manager.asp, line 101



CAUSE
This error message is caused by a loss of network connectivity between Digital Broadcast Manager and Windows Media Server.



RESOLUTION
Perform standard network troubleshooting procedures, such as verifying that the physical link has not been disturbed, or that TCP/IP connectivity has not been disrupted.



STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.



MORE INFORMATION
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q102908 How to Troubleshoot TCP/IP Connectivity with Windows NT
Q143351 How to Check Network Connectivity Using Net Diagnostics
Q146816 IIS Troubleshooting With ODBC SQL Integration

Additional query words: netshow wms wmt wmp tshoot

Keywords : prodsitesrv3 prodCS kbwms40 kbwms41
Issue type : kbprb
Technology : kbvcSearch


Last Reviewed: June 6, 2000
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.




--------------------------------------------------------------------------------
Send feedback to MSDN.Look here for MSDN Online resources.

[peet]

Result 3:

MSDN:
FIX: Columns Listed Multiple Times in GROUP BY WITH CUBE Clause Cause Access Violation

Q246598


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft SQL Server version 7.0

--------------------------------------------------------------------------------
BUG #: 53838 (SQLBUG_70)

SYMPTOMS
When the same column is listed multiple times in a GROUP BY clause that uses the CUBE operator, you may receive the following Access Violation (AV) error message:

ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData ((null)()).
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.

Connection Broken



WORKAROUND
Use table aliases and qualify the multiple instances of the column in the GROUP BY clause with the aliases.



STATUS
Microsoft has confirmed this to be a problem in SQL Server version 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 7.0. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/view/de...hl&pg=sql.asp.

For more information, contact your primary support provider.



MORE INFORMATION

Steps To Reproduce The Problem
Query 1 demonstrates the problem while Query 2 uses table aliases to work around the problem.


Query 1

USE tempdb
GO
DROP TABLE t1
GO
CREATE TABLE t1(c1 INT)
GO
SELECT c1
FROM t1
GROUP BY c1, c1, c1, c1
WITH CUBE
GO
Query 2

USE tempdb
GO
DROP TABLE t1
go
CREATE TABLE t1(c1 INT)
GO
SELECT a.c1
FROM t1 a, t1 b, t1 c, t1 d
GROUP BY a.c1, b.c1, c.c1, d.c1
WITH CUBE
GO

Additional query words:

Keywords : kbbug7.00 kbDSupport
Issue type : kbbug
Technology :


Last Reviewed: March 17, 2000
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.




--------------------------------------------------------------------------------
Send feedback to MSDN.Look here for MSDN Online resources

[peet]

Result 4

MSDN:
PRB: ODBC Connection Failed: SQLState: '08001' DBMSSOCN

Q195566


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft SQL Server version 6.5
Microsoft SQL Server, Enterprise Edition, version 6.5

--------------------------------------------------------------------------------


SYMPTOMS
The following error message is returned from the ODBC Data Source Administrator and/or an ODBC application while attempting to make a connection to SQL Server:

Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][DBMSSOCN] General Network error. Check your documentation.
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][DBMSSOCN]ConnectionOpen(connect())
Connection failed:
SQLState: 08001
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.
Connection failed:
SQLState: 01000
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (connect())



CAUSE
The most common reason that this connection attempt failed is that this DSN or ODBC data source attempted to make a connection using the TCP/IP sockets Net-Library, which is Dbmssocn.dll. Because the SQL Server is not listening for incoming connections for TCP/IP sockets clients, the connection fails. From ISQL/w, the second error message stated above would be returned. The OS Error is 10061, and the function call that failed was ConnectionOpen(connect()).



WORKAROUND
By default, SQL Server will listen for incoming connections made by Named Pipes clients. Named Pipes is the default IPC mechanism for clients to connect to a SQL Server version 4.2, 6.0, and 6.5 server. The Named Pipes DLL is Dbnmpntw.dll, and it should be located in the Windows\System or Winnt\System32 directory. The TCP/IP sockets netlib DLL is Dbmssocn.dll, and also should be in the Windows\System or Winnt\System32 directory.The most common resolution to this problem is to configure the client computer to connect using Named Pipes.

Configuring Named Pipes
If the Microsoft Data Access Components (MDAC) ODBC drivers have been installed on the computer, you can make this change in the second step of the Create New Data Source wizard.

NOTE: You can download MDAC drivers from:
http://www.microsoft.com/data.
To configure the client, start the Create New Data Source wizard, click the Client Configuration button, and perform the following steps, based on the version of the SQL Server ODBC driver you are using:

For SQL Server ODBC Driver version 3.50

Click the Net Library tab and use the drop down list box to set the default network (Net Library) to Named Pipes.


On the Advanced tab, remove any advanced entries that reference the server you are connecting to.


Click Done.


For SQL Server ODBC Driver version 3.70

In the Network Libraries section of the Edit Network Library Configuration dialog box, select Named Pipes.


Click OK.


If you do not have the MDAC ODBC drivers installed, you can use the SQL Server Client Configuration Utility tool to set the default Net-Library to Named Pipes. You can install the client utilities from the SQL Server CD from the i386 directory.
Configuring TCP/IP Sockets
Server configuration:
In order for a client to connect to the SQL Server over TCP/IP sockets, the server needs to be listening on the server side sockets library. To add TCP/IP sockets support run SQL Setup.
Press Continue.


Press Continue again.


Select Change Network Support


Select TCP/IP Sockets


Press Continue to accept the default Pipe Name and TCP/IP socket port 1433.


Stop and restart the MSSQLServer service.


In order for you to confirm that your SQL Server is listening for incoming sockets connections, the following line should be in the current SQL Server error log found in \mssql\log.

ods Using 'SSMSSO60.DLL' version '6.5.0.0' to listen on '1433'.
Client configuration:
To configure the client, start the Create New Data Source wizard, click Client Configuration, and perform the following steps, based on the version of the SQL Server ODBC driver you are using:

For SQL Server ODBC Driver version 3.50:
Click the Net Library tab and use the drop down list box to set the default network (Net Library) to TCP/IP Sockets.


OR
Leave the default Net Library set to Named Pipes and on the Advanced tab, add a new entry where:

Server := SQL Server Name
Network:= TCP/IP Sockets
Connection String: = IP Address,1433
(There are no spaces between the IP Address, the comma, and the port 1433)



Click Add/Modify.


Click Done.


For SQL Server ODBC Driver version 3.70:
In the Network Libraries section of the Edit Network Library Configuration dialog box, select TCP/IP.


Enter the name of the SQL Server into the Server alias textbox


Change the Computer name to the actual IP address of the SQL Server.


Type 1433 in the port number textbox


Click OK.





MORE INFORMATION
This topic is also discussed in a troubleshooter available at the following location:

support.microsoft.com/support/tshoot/tshooterlist.asp?TPR=sql

Additional query words: Win95 datasource open database connectivity netlib lib net SBS Small Business Server

Keywords : SSrvGen SSrvNet_Lib SSrvVisB
Issue type : kbprb
Technology :


Last Reviewed: September 8, 1999
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.




--------------------------------------------------------------------------------
Send feedback to MSDN.Look here for MSDN Online resources.