Track AG Listener port changes

Question

Post reply

Track AG Listener port changes

lanky_doodle

SSCrazy

Points: 2378
More actions
April 12, 2022 at 10:07 am

#4014470

Hi,
I've inherited an existing system. We've had an issue with our application connecting to the SQL back-end. The port number of the instances is 1433 and the AG Listener port is 8001. I don't know if it was originally designed like this, or if the port number has been recently changed which is why we have the problem.
Are AG Listener port number changes logged anywhere?
Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80325 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Michael L John One Orange Chip Points: 27059 More actions · Answer 2

lanky_doodle wrote:

Hi,
I've inherited an existing system. We've had an issue with our application connecting to the SQL back-end. The port number of the instances is 1433 and the AG Listener port is 8001. I don't know if it was originally designed like this, or if the port number has been recently changed which is why we have the problem.
Are AG Listener port number changes logged anywhere?
Thanks

1433 is the default port for SQL Server. When creating a listener, there is no default port. You need to specify it when you create it.

Why do you suspect that this is the issue? What are the specific errors you are getting? Can you show your connection string?

Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/

lanky_doodle SSCrazy Points: 2378 More actions · Answer 3

Hi, sorry for the late response.

SCCM was working one day then stopped literally the next. On inspecting the original SCCM config. (its connection string in Site Manager) it was set to use the AG Listener on port 1433. When checking the Listener in SQL, it was set to 8001.

SCCM was installed about 18 months ago and has been fine until this error happened. So someone or something changed the listener port, and I need to find out who what where when why for the root cause.

Do SQL logs capture these changes?

Thanks