January 6, 2017 at 2:05 pm
I have got SQL Server installed and working fine. In order to allow firewalls, I went in to see that the instance I created is listening on dynamic port for each IP.
I went to TCP/IP Protocol properties, removed 0 for Dynamic Port from all IPs and added 1433 as TCP Port value. I restarted SQL Server service.
But, SQL Server is listening on 54674 instead of 1433 even after restart. I tried restarting the machine to just rule out I'm not missing any other service restart but of no use.
I tried changing port to 2001 and followed the same steps but the issue is same.
I ran below command
USE MASTER
GO
xp_readerrorlog 0, 1, N'Server is listening on'
GO
This gives me a little bit strange output
2017-01-06 14:32:25.580 spid17s Server is listening on [ 'any' <ipv6> 1433].
2017-01-06 14:32:25.580 spid17s Server is listening on [ 'any' <ipv4> 1433].
2017-01-06 14:32:25.580 spid17s Server is listening on [ 'any' <ipv6> 2001].
2017-01-06 14:32:25.580 spid17s Server is listening on [ 'any' <ipv4> 2001].
2017-01-06 14:32:25.580 Server Server is listening on [ ::1 <ipv6> 54674].
2017-01-06 14:32:25.580 Server Server is listening on [ 127.0.0.1 <ipv4> 54674].
It looks like my changes to ports 1433 and then to 2001 has made spid17s to listen on but no effect on Server. I am puzzled on what this spid17s is and why it is being shown here!!
I'm pretty much sure I did this many times in earlier versions successfully but not able to figure out what is so special in 2014, that I might be missing.
Please throw some pointers on fixing the issue.
January 7, 2017 at 11:46 am
There are multiple IP addresses for your host. You need to set them all to 1433, if that's what you want.
Be sure that only one SQL instance is on this port. You cannot have multiple services on one port.
January 7, 2017 at 11:34 pm
Hope this is the only instance on your machine.
January 8, 2017 at 8:07 am
Yes, it is the only instance on the server and that is what puzzles me. Every time I changed port, it created sp17s server as shown in the output in my question.
VastSQL (1/7/2017)
Hope this is the only instance on your machine.
January 19, 2017 at 6:08 am
sarath.tata - Sunday, January 8, 2017 8:07 AMYes, it is the only instance on the server and that is what puzzles me. Every time I changed port, it created sp17s server as shown in the output in my question.VastSQL (1/7/2017)
Hope this is the only instance on your machine.
Is it a named instance? can you share the screenshot of your Port Configuration.
January 20, 2017 at 7:29 am
Have you done this?
Go into SQL Server Configuration Manager for that SQL Server and clear out all the TCP Dynamic Ports (set them to 0) and TCP Port entries (leave them blank) for all IPs (IP# through IPAll). Then set the static port entry you want for IPAll. Restart SQL Server.
K. Brian Kelley
@kbriankelley
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply