Error establishing socket. Address already in use

[betagreg]

Running CFMX 6.1 on Win2k3, I just recently started getting these errors from
connections to one of our SQLServer database servers (2000, enterprise):
[Q]Error Executing Database Query.[Macromedia][SQLServer JDBC Driver]Error
establishing socket. Address already in use: connect[/Q]
Any ideas what might cause this?

[elDonrico]

[q]Originally posted by: betagreg
Running CFMX 6.1 on Win2k3, I just recently started getting these errors from
connections to one of our SQLServer database servers (2000, enterprise):
[Q]Error Executing Database Query.[Macromedia][SQLServer JDBC Driver]Error
establishing socket. Address already in use: connect[/Q]
Any ideas what might cause this?
[/q]


It caused by exactly what it says... The socket you are trying to connect to
is already in use or it didnt close properly. i'll bet the error clears after a
reboot of both the db server and the application server. what other connections
do you have on the sql server? what version of jdbc are you using? check pete's
site in help with this [url]http://www.petefreitag.com/item/118.cfm[/url]
here is a tech note on known issues with the jdbc driver 3.3 and mx6.1
[url]http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_18807[/url]

and here is an explanation of the error.
[url]http://people.cs.uchicago.edu/~mark/51081/labs/LAB6/sock.html[/url]

[betagreg]

Okay, not really helpful. I guess I should ask, "I can read the error as good
as you can, but what might cause CF to suddenly start throwing this error with
no changes to configuration or software?"

Maybe now I can get a real response?

[elDonrico]

ok. well, if you think that was useless, you might as well not read on... this
isnt a coldfusion error. it only appears that way because you are using cfml.
this is a most probably an SQL issue. i say most probably, because there are
many reasons this could be happening. try doing things in these steps as they
are in degrees of harshness.
1. check the server event log, see if you have an entry like this
.'You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server 2003
family. To reduce your computer's vulnerability to certain virus attacks, the
TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have
been disabled. To enable these ports, you must install a patch, or the most
recent service pack for Microsoft SQL Server 2000 or MSDE from
[url]http://www.microsoft.com/sql/downloads/default.asp[/url]'
install sp4 [url]http://www.microsoft.com/sql/downloads/2000/sp4.mspx[/url]
2. change your database server name to its IP (if that doesnt work, you might
as well change it back)
3. make sure you are authenticating with an SQL account. windows integrated
authentication does not work well ... in your SQL enterprise manager, set it to
mixed authentication in the security tab, select SQL server and windows
authentication. the microsoft driver seems to not handle the windows
authentication properly. i wouldnt use the the SA account, create another one
just for this purpose.
4. under the general tab in your enterprise manager click network
configuration. enable TCP/IP which is not enabled by default
5. Install SQL Server 2000 sp3 or sp4

and here are some other useless articles you might want to read...
Know bug in SQL Server preventing it from listening on port 1433
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;306865[/url]
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;329329[/url]
info on clustered SQL servers
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;815431[/url]

[betagreg]

hey, don't mind me, I'm just cranky because of the inexplicable errors (and
reasons behind those errors). I appreciate the responses. Items 1, 3, and 5
don't apply (we are running SQLServer 2000 enterprise SP4, using a SQL
account). I will try the IP suggestion. Sorry for getting snippy.