Riaan de Wet 
South Africa
Member since
4/4/2005
Platinum Membership
Posts: 56
 |
| 7/17/2007 11:30 PM |
|
Hi,
I'm running SQL 2000 (and have WSUS3.0 installed)
I'm getting the followng error in my error log. Any ideas on how to fix it?
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 2007/07/17
Time: 22:23:14
User: N/A
Computer: TTSBS03
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 44 4a 00 00 10 00 00 00 DJ...... 0008: 08 00 00 00 54 00 54 00 ....T.T. 0010: 53 00 42 00 53 00 30 00 S.B.S.0. 0018: 33 00 00 00 00 00 00 00 3.......
Kind Regards,
Riaan
|
|
|
|
|
|
Marina Roos
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12280
|
|
Edwin Sarmiento
Singapore
Member since
2/13/2007
Microsoft MVP
Posts: 133
|
| 7/23/2007 09:00 AM |
|
| This seems to only affect the default SQL Server instance. Check the Server Network Utility and see if TCP/IP is set and check the port number as well |
|
MCP MCDBA MCAD MCSD MCT MCTS MCITP : DBA MCSA
http://bassplayerdoc.blogspot.com
Need a remote SQL Server DBA? |
|
|
|
Riaan de Wet
South Africa
Member since
4/4/2005
Platinum Membership
Posts: 56
|
| 7/23/2007 09:42 PM |
|
Hi Edwin,
For the default SQL server Instance (the one I'm having problems with), TCP/IP is set to Port 1433, and Named Pipes is also enabled.
TCP/IP with Port 1433 is also enabled for the other named instances: (local)\SBSMONITORING, (local)\MSFW and (local)\SHAREPOINT.
The one instance which I cannot see any details for is (local)\MICROSOFT##SSEE.
|
|
|
|
|
|
Riaan de Wet
South Africa
Member since
4/4/2005
Platinum Membership
Posts: 56
|
| 7/23/2007 09:58 PM |
|
Hi Marina,
I had a look at the support link you've supplied.
I;ve run the PortQuery as indicated, but got the following results:
PortQry is querying TCP ports 25,110,143,53, and 389
It will only report which ports are listening
Port 1433 is listening
Port 25 is listening
Port 110 is listening
Port 143 is listening
Port 53 is listening
Port 389 is listening
When I run netstat -ano to display the ports being used and the PID (Processor ID's of the aplications using the port), I get the following:
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:1294 0.0.0.0:0 LISTENING 5484
TCP 0.0.0.0:1330 0.0.0.0:0 LISTENING 5244
TCP 0.0.0.0:1344 0.0.0.0:0 LISTENING 5880
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING 2212
TCP 0.0.0.0:1444 0.0.0.0:0 LISTENING 6216
TCP 0.0.0.0:1453 0.0.0.0:0 LISTENING 5048
In this instance Port 1433's PID = 2212, which in my Taks Manager is SQLSRVR.exe.
Thus according to this, SQL is bound to Port 1433.
This does not make sense, unless it is some of the other instances that hogs the port. Maybe the Microsoft##SSEE? (See above post)
Cheers,
Riaan
|
|
|
|
|
|
Edwin Sarmiento
Singapore
Member since
2/13/2007
Microsoft MVP
Posts: 133
|
| 7/30/2007 05:59 AM |
|
You can check which instance it is by running this command
tasklist /svc /fi "IMAGENAME eq sqlservr.exe" |
|
MCP MCDBA MCAD MCSD MCT MCTS MCITP : DBA MCSA
http://bassplayerdoc.blogspot.com
Need a remote SQL Server DBA? |
|
|
|
Riaan de Wet
South Africa
Member since
4/4/2005
Platinum Membership
Posts: 56
|
| 7/30/2007 10:06 PM |
|
Hi Edwin,
I've run the command supplied. The my SQL$SBSMONITORING instance is the one that is currenlty listening to port 1433.
How would I change is so that my default SQL Instance listen on port 1433?
Thanx for the continued assistance.
Riaan
|
|
|
|
|
|
Marina Roos
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12280
|
| 7/31/2007 01:01 AM |
|
Hi Riaan,
That instance shouldn't be listening to 1433 at all. If you pull up the SQL Server Network Utility, the local SQL server instance should have the Named Pipes and TCP/IP in the enabled protocols. The Monitoring, MSFW (ISA) and Sharepoint instance should have nothing listed in the enabled protocols by default. Can you check this and remove it if they are enabled?
|
|
| Marina Roos Smallbizserver.Net Administrator | Mission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain' |
|
|
|
|
Riaan de Wet
South Africa
Member since
4/4/2005
Platinum Membership
Posts: 56
|
| 8/07/2007 12:55 AM |
|
Hi Marina,
Thank you very much. This solved my issue.
Kind Regards,
Riaan |
|
|
|
|
|