Bind failed on TCP port 1433

I installed SP3a and now I am getting this error message in the application
event log. Also, I can only connect to my server using namepipes. But
TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
event logs says that SQL is listening on 127.0.0.1:1433.
Can someone please help. I have not seen the answer and I have been
searching for 2 days now.
Log:
SQL server listening on 127.0.0.1: 1433.
SuperSocket Info: Bind failed on TCP port 1433.
SuperSocket info: (SpnRegister) : Error 1355.
Thanks in advance!Dolph,
There are two scenarios that I can think of that will cause this situation.
1) You have bounced the SQL Server service programmatically (probably in
C++) and the service has been stopped and restarted too quickly. SQL
Server does not release the port quickly enough before it is restarted
and thinks that another service is using port 1433. The bind, then fails.
2) Another application is using port 1433.
You can check your ports using this on the commandline:
netstat -a
Look at the local address column for <machinename>:ms-sql-s or
<machinename>:1433
On my Inspiron laptop I get these results:
Active Connections
Proto Local Address Foreign Address State
TCP inspiron4100:ftp inspiron4100:0 LISTENING
TCP inspiron4100:http inspiron4100:0 LISTENING
TCP inspiron4100:epmap inspiron4100:0 LISTENING
TCP inspiron4100:https inspiron4100:0 LISTENING
TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
TCP inspiron4100:1025 inspiron4100:0 LISTENING
TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
TCP inspiron4100:2869 inspiron4100:0 LISTENING
TCP inspiron4100:3389 inspiron4100:0 LISTENING
TCP inspiron4100:1028 inspiron4100:0 LISTENING
TCP inspiron4100:1061 inspiron4100:0 LISTENING
TCP inspiron4100:1134 localhost:1135 ESTABLISHED
TCP inspiron4100:1135 localhost:1134 ESTABLISHED
TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863
ESTABLISHED
TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
UDP inspiron4100:microsoft-ds *:*
UDP inspiron4100:isakmp *:*
UDP inspiron4100:1026 *:*
UDP inspiron4100:1069 *:*
UDP inspiron4100:1070 *:*
UDP inspiron4100:1131 *:*
UDP inspiron4100:ms-sql-m *:*
UDP inspiron4100:3456 *:*
UDP inspiron4100:4500 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:1050 *:*
UDP inspiron4100:1057 *:*
UDP inspiron4100:1156 *:*
UDP inspiron4100:1900 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:netbios-ns *:*
UDP inspiron4100:netbios-dgm *:*
UDP inspiron4100:1900 *:*
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Dolph Larson wrote:
> I installed SP3a and now I am getting this error message in the application
> event log. Also, I can only connect to my server using namepipes. But
> TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
> event logs says that SQL is listening on 127.0.0.1:1433.
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
> Log:
> SQL server listening on 127.0.0.1: 1433.
> SuperSocket Info: Bind failed on TCP port 1433.
> SuperSocket info: (SpnRegister) : Error 1355.
> Thanks in advance!|||I didn't finish. :-/
If you still cannot find the cause of the problem, I suggest that you
reboot the server.
In the case of 1) the solution is to put a small pause in your code
before starting the MSSQLServer service again.
In the case of 2) you will need to ensure that your application uses
another port - perhaps there is a setting somewhere (maybe the registry)
where you can tweak this.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Allison wrote:
> Dolph,
> There are two scenarios that I can think of that will cause this situation.
> 1) You have bounced the SQL Server service programmatically (probably in
> C++) and the service has been stopped and restarted too quickly. SQL
> Server does not release the port quickly enough before it is restarted
> and thinks that another service is using port 1433. The bind, then fails.
> 2) Another application is using port 1433.
> You can check your ports using this on the commandline:
> netstat -a
> Look at the local address column for <machinename>:ms-sql-s or
> <machinename>:1433
> On my Inspiron laptop I get these results:
>
> Active Connections
> Proto Local Address Foreign Address State
> TCP inspiron4100:ftp inspiron4100:0 LISTENING
> TCP inspiron4100:http inspiron4100:0 LISTENING
> TCP inspiron4100:epmap inspiron4100:0 LISTENING
> TCP inspiron4100:https inspiron4100:0 LISTENING
> TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> TCP inspiron4100:1025 inspiron4100:0 LISTENING
> TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> TCP inspiron4100:2869 inspiron4100:0 LISTENING
> TCP inspiron4100:3389 inspiron4100:0 LISTENING
> TCP inspiron4100:1028 inspiron4100:0 LISTENING
> TCP inspiron4100:1061 inspiron4100:0 LISTENING
> TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHED
> TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> UDP inspiron4100:microsoft-ds *:*
> UDP inspiron4100:isakmp *:*
> UDP inspiron4100:1026 *:*
> UDP inspiron4100:1069 *:*
> UDP inspiron4100:1070 *:*
> UDP inspiron4100:1131 *:*
> UDP inspiron4100:ms-sql-m *:*
> UDP inspiron4100:3456 *:*
> UDP inspiron4100:4500 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:1050 *:*
> UDP inspiron4100:1057 *:*
> UDP inspiron4100:1156 *:*
> UDP inspiron4100:1900 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:netbios-ns *:*
> UDP inspiron4100:netbios-dgm *:*
> UDP inspiron4100:1900 *:*
>
>
>|||Thanks for trying to help. Sadly, it can not be either case. I am not
doing anything with C++ and I have not downloaded any application lately that
is build on it. Esp. working with SQL server. I looked at the ports with
netstat -an and I see the port being listened by SQL Server. The server just
wont bind to that port. If I can't find a solution soon, I will be left to
do a re-install. :(
Dolph
"Mark Allison" wrote:
> I didn't finish. :-/
> If you still cannot find the cause of the problem, I suggest that you
> reboot the server.
> In the case of 1) the solution is to put a small pause in your code
> before starting the MSSQLServer service again.
> In the case of 2) you will need to ensure that your application uses
> another port - perhaps there is a setting somewhere (maybe the registry)
> where you can tweak this.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Mark Allison wrote:
> > Dolph,
> >
> > There are two scenarios that I can think of that will cause this situation.
> >
> > 1) You have bounced the SQL Server service programmatically (probably in
> > C++) and the service has been stopped and restarted too quickly. SQL
> > Server does not release the port quickly enough before it is restarted
> > and thinks that another service is using port 1433. The bind, then fails.
> >
> > 2) Another application is using port 1433.
> >
> > You can check your ports using this on the commandline:
> >
> > netstat -a
> >
> > Look at the local address column for <machinename>:ms-sql-s or
> > <machinename>:1433
> >
> > On my Inspiron laptop I get these results:
> >
> >
> > Active Connections
> >
> > Proto Local Address Foreign Address State
> > TCP inspiron4100:ftp inspiron4100:0 LISTENING
> > TCP inspiron4100:http inspiron4100:0 LISTENING
> > TCP inspiron4100:epmap inspiron4100:0 LISTENING
> > TCP inspiron4100:https inspiron4100:0 LISTENING
> > TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> > TCP inspiron4100:1025 inspiron4100:0 LISTENING
> > TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> > TCP inspiron4100:2869 inspiron4100:0 LISTENING
> > TCP inspiron4100:3389 inspiron4100:0 LISTENING
> > TCP inspiron4100:1028 inspiron4100:0 LISTENING
> > TCP inspiron4100:1061 inspiron4100:0 LISTENING
> > TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> > TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> > TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> > TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHED
> > TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> > TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> > TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> > UDP inspiron4100:microsoft-ds *:*
> > UDP inspiron4100:isakmp *:*
> > UDP inspiron4100:1026 *:*
> > UDP inspiron4100:1069 *:*
> > UDP inspiron4100:1070 *:*
> > UDP inspiron4100:1131 *:*
> > UDP inspiron4100:ms-sql-m *:*
> > UDP inspiron4100:3456 *:*
> > UDP inspiron4100:4500 *:*
> > UDP inspiron4100:ntp *:*
> > UDP inspiron4100:1050 *:*
> > UDP inspiron4100:1057 *:*
> > UDP inspiron4100:1156 *:*
> > UDP inspiron4100:1900 *:*
> > UDP inspiron4100:ntp *:*
> > UDP inspiron4100:netbios-ns *:*
> > UDP inspiron4100:netbios-dgm *:*
> > UDP inspiron4100:1900 *:*
> >
> >
> >
> >
> >
>|||Dolph Larson wrote:
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
For the benefit of any other poor ***s trying to work this one out,
here's what I just found...
We got the "SuperSocket Info: Bind failed on TCP port 1433" error, yet
netstat says the socket _is_ listening. TCPView (from the excellent
sysinternals site) confirms that it's listening, and that it's SQL
server that doing it.
Stumped despite much googling, I suddenly realised we'd recently
installed a new remote access _client_ on this server, Windows Secure
Application Manager from netscreen. This seems to work by hooking the
TCP stack with an LSP. Needless to say, it was this that was messing
up SQL server - using the diagnostics tool to remove the LSP sorted it
out straight away.
Thinking back, I've seen problems with an LSP before: some weird
problem with Norton Antivirus left a machine in a state where ipconfig
said it was dialled up OK, it could ping, but it couldn't do email or
http... Zapping the LSP sorted it (not that I can remember how I
removed it!)
Cheers,
Martin.

Bind failed on TCP port 1044.

I am getting this error in the Event Viewer and the clients are unable to
connect to the SQL server. What is wrong?
PLEASE HELP!!
ScottHi
You SQL Server is configured not to use the standard 1433 port, but this is
not a problem in itself.
By the time SQL Server starts, there is another application that is using
the port 1044. This results in SQL Server not being able to use it. You need
to either stop that application or configure SQL Server to use a different
port. Configure the port though Server Network Utility in the SQL Server men
u.
Regards
Mike
"scottdog129" wrote:

> I am getting this error in the Event Viewer and the clients are unable to
> connect to the SQL server. What is wrong?
> PLEASE HELP!!
> Scottsql

Bind failed on TCP port 1044.

I am getting this error in the Event Viewer and the clients are unable to
connect to the SQL server. What is wrong?
PLEASE HELP!!
Scott
Hi
You SQL Server is configured not to use the standard 1433 port, but this is
not a problem in itself.
By the time SQL Server starts, there is another application that is using
the port 1044. This results in SQL Server not being able to use it. You need
to either stop that application or configure SQL Server to use a different
port. Configure the port though Server Network Utility in the SQL Server menu.
Regards
Mike
"scottdog129" wrote:

> I am getting this error in the Event Viewer and the clients are unable to
> connect to the SQL server. What is wrong?
> PLEASE HELP!!
> Scott

Better explanation of the "Scan:Started" Event's "Mode" data column in SQL Profiler?

A scan is a scan is not a full scan?
I am trying to monitor full table or clustered index scans. In SQL
Profiler, we have the "Scan:Started" event class. It has a
corresponding Mode data column that represents "Scan Mode" (duh). The
only information I have been able to find about what each of the modes
means is the very terse description for each mode supplied in SQL BOL.
Can anyone point me to better descriptions of these scan modes?
Maybe more importantly, what are the ones I should look out for that
represent full scans.
TIA,
-Peterit depends what you mean by full scan,
the entire contents of the table?
this would be table or clustered index scans, having
indexID 0 or 1
a scan could apply to just a nonclustered index, which is
all rows but not the full contents of the table
also, suppose your query was select top x,
the plan could show a scan, but stops after x rows are
retrieved
or are you wanting to exclude range scans? thats a term
used in other products, SQL Server considers retrieving an
indexed block of rows an index seek, not a scan
>--Original Message--
>A scan is a scan is not a full scan?
>I am trying to monitor full table or clustered index
scans. In SQL
>Profiler, we have the "Scan:Started" event class. It has
a
>corresponding Mode data column that represents "Scan
Mode" (duh). The
>only information I have been able to find about what each
of the modes
>means is the very terse description for each mode
supplied in SQL BOL.
> Can anyone point me to better descriptions of these scan
modes?
>Maybe more importantly, what are the ones I should look
out for that
>represent full scans.
>TIA,
>-Peter
>.
>|||I'm performace tuning and monitoring, so I am interested in
determining the "bad" kinds of scans. Even if the execution plan
shows only an index seek, there is still a "Scan:Started" event event
in profiler and a "Scan count 1" coming out of "SET STATISTICS IO" ON.
How dow I monitor for only the bad types of scans? I was guessing
that the Scan Mode in profiler was the right direction.
Where can I find a better description for the scan mode in profiler?
"joe chang" <anonymous@.discussions.microsoft.com> wrote in message news:<062f01c3dbd7$b4af6130$a301280a@.phx.gbl>...
> it depends what you mean by full scan,
> the entire contents of the table?
> this would be table or clustered index scans, having
> indexID 0 or 1
> a scan could apply to just a nonclustered index, which is
> all rows but not the full contents of the table
> also, suppose your query was select top x,
> the plan could show a scan, but stops after x rows are
> retrieved
> or are you wanting to exclude range scans? thats a term
> used in other products, SQL Server considers retrieving an
> indexed block of rows an index seek, not a scan
> >--Original Message--
> >A scan is a scan is not a full scan?
> >
> >I am trying to monitor full table or clustered index
> scans. In SQL
> >Profiler, we have the "Scan:Started" event class. It has
> a
> >corresponding Mode data column that represents "Scan
> Mode" (duh). The
> >only information I have been able to find about what each
> of the modes
> >means is the very terse description for each mode
> supplied in SQL BOL.
> > Can anyone point me to better descriptions of these scan
> modes?
> >Maybe more importantly, what are the ones I should look
> out for that
> >represent full scans.
> >
> >TIA,
> >
> >-Peter
> >.
> >|||I'd still love a response to this one.
Thx.
nospampedro@.yahoo.com (Peter Daniels) wrote in message news:<2fd8f155.0401160937.396fecf4@.posting.google.com>...
> I'm performace tuning and monitoring, so I am interested in
> determining the "bad" kinds of scans. Even if the execution plan
> shows only an index seek, there is still a "Scan:Started" event event
> in profiler and a "Scan count 1" coming out of "SET STATISTICS IO" ON.
> How dow I monitor for only the bad types of scans? I was guessing
> that the Scan Mode in profiler was the right direction.
> Where can I find a better description for the scan mode in profiler?
> "joe chang" <anonymous@.discussions.microsoft.com> wrote in message news:<062f01c3dbd7$b4af6130$a301280a@.phx.gbl>...
> > it depends what you mean by full scan,
> > the entire contents of the table?
> > this would be table or clustered index scans, having
> > indexID 0 or 1
> > a scan could apply to just a nonclustered index, which is
> > all rows but not the full contents of the table
> > also, suppose your query was select top x,
> > the plan could show a scan, but stops after x rows are
> > retrieved
> > or are you wanting to exclude range scans? thats a term
> > used in other products, SQL Server considers retrieving an
> > indexed block of rows an index seek, not a scan
> >
> > >--Original Message--
> > >A scan is a scan is not a full scan?
> > >
> > >I am trying to monitor full table or clustered index
> scans. In SQL
> > >Profiler, we have the "Scan:Started" event class. It has
> a
> > >corresponding Mode data column that represents "Scan
> Mode" (duh). The
> > >only information I have been able to find about what each
> of the modes
> > >means is the very terse description for each mode
> supplied in SQL BOL.
> > > Can anyone point me to better descriptions of these scan
> modes?
> > >Maybe more importantly, what are the ones I should look
> out for that
> > >represent full scans.
> > >
> > >TIA,
> > >
> > >-Peter
> > >.
> > >|||Instead of searching for "bad scans" you may want to instead look for
long-running queries with the profiler. After all, a sequential scan of a
small table is not really a "bad scan."
Once you have found the long-running queries, see what you can do to speed
them up.
If you want some automated assistance, use the index tuning wizard on a
tracefile you collect with the profiler.
Eric
"Peter Daniels" <nospampedro@.yahoo.com> wrote in message
news:2fd8f155.0402111609.180fabbb@.posting.google.com...
> I'd still love a response to this one.
> Thx.
> nospampedro@.yahoo.com (Peter Daniels) wrote in message
news:<2fd8f155.0401160937.396fecf4@.posting.google.com>...
> > I'm performace tuning and monitoring, so I am interested in
> > determining the "bad" kinds of scans. Even if the execution plan
> > shows only an index seek, there is still a "Scan:Started" event event
> > in profiler and a "Scan count 1" coming out of "SET STATISTICS IO" ON.
> > How dow I monitor for only the bad types of scans? I was guessing
> > that the Scan Mode in profiler was the right direction.
> >
> > Where can I find a better description for the scan mode in profiler?
> >
> > "joe chang" <anonymous@.discussions.microsoft.com> wrote in message
news:<062f01c3dbd7$b4af6130$a301280a@.phx.gbl>...
> > > it depends what you mean by full scan,
> > > the entire contents of the table?
> > > this would be table or clustered index scans, having
> > > indexID 0 or 1
> > > a scan could apply to just a nonclustered index, which is
> > > all rows but not the full contents of the table
> > > also, suppose your query was select top x,
> > > the plan could show a scan, but stops after x rows are
> > > retrieved
> > > or are you wanting to exclude range scans? thats a term
> > > used in other products, SQL Server considers retrieving an
> > > indexed block of rows an index seek, not a scan
> > >
> > > >--Original Message--
> > > >A scan is a scan is not a full scan?
> > > >
> > > >I am trying to monitor full table or clustered index
> > scans. In SQL
> > > >Profiler, we have the "Scan:Started" event class. It has
> > a
> > > >corresponding Mode data column that represents "Scan
> > Mode" (duh). The
> > > >only information I have been able to find about what each
> > of the modes
> > > >means is the very terse description for each mode
> > supplied in SQL BOL.
> > > > Can anyone point me to better descriptions of these scan
> > modes?
> > > >Maybe more importantly, what are the ones I should look
> > out for that
> > > >represent full scans.
> > > >
> > > >TIA,
> > > >
> > > >-Peter
> > > >.
> > > >|||Thanks for your response, but I want to use BOTH angles for my query
analysis. Duration is only one aspect of the performance of a query.
I understand that full scans on small tables may not be a bad thing,
but SQL Server Profiler provides the scan mode data column, so I just
want a better description of what those scan modes are that what is
provided in SQL BOL:
Scan mode. Can have these values:
1 = Normal
2 = First
4 = Back
8 = Unordered
16 = No data
32 = Reserved
64 = Exlatch
128 = Index supplied
256 = Marker
Thanks,
-Peter
nospampedro@.yahoo.com (Peter Daniels) wrote in message news:<2fd8f155.0402111609.180fabbb@.posting.google.com>...
> I'd still love a response to this one.
> Thx.
> nospampedro@.yahoo.com (Peter Daniels) wrote in message news:<2fd8f155.0401160937.396fecf4@.posting.google.com>...
> > I'm performace tuning and monitoring, so I am interested in
> > determining the "bad" kinds of scans. Even if the execution plan
> > shows only an index seek, there is still a "Scan:Started" event event
> > in profiler and a "Scan count 1" coming out of "SET STATISTICS IO" ON.
> > How dow I monitor for only the bad types of scans? I was guessing
> > that the Scan Mode in profiler was the right direction.
> >
> > Where can I find a better description for the scan mode in profiler?
> >
> > "joe chang" <anonymous@.discussions.microsoft.com> wrote in message news:<062f01c3dbd7$b4af6130$a301280a@.phx.gbl>...
> > > it depends what you mean by full scan,
> > > the entire contents of the table?
> > > this would be table or clustered index scans, having
> > > indexID 0 or 1
> > > a scan could apply to just a nonclustered index, which is
> > > all rows but not the full contents of the table
> > > also, suppose your query was select top x,
> > > the plan could show a scan, but stops after x rows are
> > > retrieved
> > > or are you wanting to exclude range scans? thats a term
> > > used in other products, SQL Server considers retrieving an
> > > indexed block of rows an index seek, not a scan
> > >
> > > >--Original Message--
> > > >A scan is a scan is not a full scan?
> > > >
> > > >I am trying to monitor full table or clustered index
> scans. In SQL
> > > >Profiler, we have the "Scan:Started" event class. It has
> a
> > > >corresponding Mode data column that represents "Scan
> Mode" (duh). The
> > > >only information I have been able to find about what each
> of the modes
> > > >means is the very terse description for each mode
> supplied in SQL BOL.
> > > > Can anyone point me to better descriptions of these scan
> modes?
> > > >Maybe more importantly, what are the ones I should look
> out for that
> > > >represent full scans.
> > > >
> > > >TIA,
> > > >
> > > >-Peter
> > > >.
> > > >

Best way to prevent multiple notifications for an event

I am setting up a notification system using the SQL Event Provider, and I have a question about preventing multiple notifications for a single event. The events are provided from a SQL select, and the notification emails are sent once a day. How does NS decide if it's already handled an event? If I change the email frequency, do I need to add a check in my SQL select, or does NS handle this?

Thanks
Erick

Chronicles tables can be used to prevent duplicate notifications. Check out ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlntsv9/html/17e2debd-485f-4962-b974-6be6597983f9.htm for more information.

HTH...