SQL Server 2022 CU24 includes a documented issue where an availability group listener can generate error 10013 messages in the SQL Server error log. Microsoft says this can happen when the SQL Server service starts, when an availability group failover occurs, or when you create a new listener after applying the update.
What Microsoft documented
According to the release notes for KB5080999 / CU24 for SQL Server 2022 (build 16.0.4245.2), SQL Server may try to open a TCP port that is already in use when it starts or when a listener is created. In those cases, SQL Server logs error messages related to the listener object.
Microsoft notes that this results in error messages only and does not affect functionality. Listener connections continue to work.
Microsoft is aware of the issue and is investigating a fix.
Example scenario
A documented scenario is:
- Configure a SQL Server availability group with a listener.
- Start the SQL Server service or trigger an availability group failover.
- Check the SQL Server error log and you may see listener-related error 10013 entries.
Microsoft also says that after applying this update, creating a new listener can produce a similar error message in the log.
Affected release
- SQL Server 2022 CU24
- KB5080999
- Build 16.0.4245.2