SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-29-2008, 05:52 AM
| ||||
| ||||
 SQL Server 2000 cannot listen on TCP/IP! Hi all! I just tried to enable TCP/IP on SQL Server 2000 (trial, SP3a). The Server Network Utility shows it's already turned on, but after restarting the server doesn't listen to any TCP port, and in the eventlog it reports "SuperSocket info: gethostbyname(MSAFD Tcpip [TCP/IP]) : Error 11004." and "SuperSocket info: (SpnRegister) : Error 2102.". I googled but found nothing helpful. Does anyone know what's wrong?? The OS is Windows 2003 Server Enterprise Edition.      |
|
02-29-2008, 05:52 AM
| |||
| |||
| Re: SQL Server 2000 cannot listen on TCP/IP! "Aquila Deus" <aquila_deus@yahoo.co.uk> wrote in message news:1107174971.116391.61060@z14g2000cwz.googlegro ups.com... > Hi all! > > I just tried to enable TCP/IP on SQL Server 2000 (trial, SP3a). The > Server Network Utility shows it's already turned on, but after > restarting the server doesn't listen to any TCP port, and in the > eventlog it reports "SuperSocket info: gethostbyname(MSAFD Tcpip > [TCP/IP]) : Error 11004." and "SuperSocket info: (SpnRegister) : Error > 2102.". I googled but found nothing helpful. Does anyone know what's > wrong?? > > The OS is Windows 2003 Server Enterprise Edition. > This KB article lists a few possibilities: http://support.microsoft.com/kb/q307197/ If that doesn't help, could you post the relevant messages from the SQL Server log, which should show which protocols are in use? And how have you verified that the server isn't listening? Does netstat show the MSSQL port? Simon |
|
02-29-2008, 05:53 AM
| ||||
| ||||
| Re: SQL Server 2000 cannot listen on TCP/IP! Simon Hayes wrote: > "Aquila Deus" <aquila_deus@yahoo.co.uk> wrote in message > news:1107174971.116391.61060@z14g2000cwz.googlegro ups.com... > > Hi all! > > > > I just tried to enable TCP/IP on SQL Server 2000 (trial, SP3a). The > > Server Network Utility shows it's already turned on, but after > > restarting the server doesn't listen to any TCP port, and in the > > eventlog it reports "SuperSocket info: gethostbyname(MSAFD Tcpip > > [TCP/IP]) : Error 11004." and "SuperSocket info: (SpnRegister) : Error > > 2102.". I googled but found nothing helpful. Does anyone know what's > > wrong?? > > > > The OS is Windows 2003 Server Enterprise Edition. > > > > This KB article lists a few possibilities: > > http://support.microsoft.com/kb/q307197/ > > If that doesn't help, could you post the relevant messages from the SQL > Server log, which should show which protocols are in use? Shared Memory (and Named Pipe if I enable it). It doesn't show anything like "bind failed", the gethostbyname is the only relevant event logged. > And how have you > verified that the server isn't listening? Does netstat show the MSSQL port? Both tcpview and netstat show that MSSQL doesnt listen on any TCP port. I didn't use dynamic port and force encryption. However, I just successfully connected to it via named pipe (thanks to a jTDS dev  . |
 |
« How to copy Database Structure from one db to another w/o affecting data
|
Table export removes primary key »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 04:23 AM.
