Applies To:
| Operating System | Server 2012, Server 2012 R2 |
| SCCM | 2012, 2012R2 |
| SQL Server | 2008 R2, 2012 and 2014 |
As part of the morning checks, I generally check SCOM for any errors or look at SCOM for any new alerts.
Saw the below error and started working to resolve it:
The alert was spitting chips about our SCCM database server.
Logged on to the SCCM database server.
Ran netstat –aon | find “4022” on a command prompt on the server to show me all the connections using port ‘4022’.
Looked for any sign that the port ‘4022’ was in use by anything else.
Checking the SQL Server Management Studio Logs, I could reaffirm that there was a conflict on the port:
If we expand Server Objects then Service Broker.
Right click on the object and select Create. This will create the object into a new query window so we can see what settings have been set:
You can see in the Red box above that the Endpoint is set to use port 4022.
Decided to double check what TCP Port was setup, and low and behold, it is set to the same Port as the TCP Endpoint hence why we are having conflict issues.
Solution
Change the TCP Port within SQL Server Configuration Manager to something other than 4022, like 1433 or 14331.
1 Giant Nerd 