Hi Jason,
The plan is to reboot today end of day and see what port services.exe self allocates, will report back.
1 Like
Rebooted the server and services.exe took another random port and everything is groovy.
It really was a âdid you try turning it off and on againâ moment 
, the odds of this happening though⌠cursed
1 Like
I havenât come across this before, and will definitely add it to my bag of tricks. Thanks for your patience going through all these details.
1 Like
Same, crazy stroke of bad luck, I donât have good math because Iâm not sure how services.exe or anything else that uses dynamic ports âchoosesâ which port to use but on paper at the most basic level it was a a 0.00006103515625% or 1/16384âŚ
Yes, those are very slim odds and I havenât encountered that particular one before. But Iâm concerned that it could happen, and given that âfixed it with a rebootâ is a solution I donât know that weâd know if this is actually a more common occurrence.
Iâve uploaded a Fixlet to at https://bigfix.me/fixlet/details/27007 that will add an exclusion for port 52315 from the ephemeral port range, so it should not be automatically allocated to a dynamic service. If youâre concerned that you might encounter such a port conflict again, this is worth trying out at least in a development environment.
1 Like
Awesome Jason!
We will be looking to add that on our instance, thank you.
1 Like