Intermittent ERROR: 10048 Unable to Listen on TCP Port 4550

[Alan Telford]

I have a nettalk server (mostly REST API methods) which has worked well for +1 year.
Without having changed anything (apart from windows updates on the VM) it now intermittently doesn't work.
After a server restart, it works correctly, but then several hours later it STOPS.

I have put the capesoft example WEB9 on the same server, and this is running fine, before and after the restart.
Web9 is using local TPS, whereas my WEBAPI is using MSSQL to a network SQL server.

When it stops working the SERVER LOG repeatedly shows these two lines:
Listening on IP Port: 4550
ERROR: 10048 Unable to Listen on TCP Port 4550


Any ideas?

[peterH]

Hi Alan,

Just a long shot: are you by any chance trying to UPDATE a field that's defined as a BLOB in the dict?

I'm having problems with that and the symptoms are similar to what you describe.

Peter

[Alan Telford]

No. Not updating any blobs in this case.
I had to restart the server again. It ran about 8 hours before requiring a restart.
I checked memory before, and 2GB free, so that wasn't an issue.
I ran TCPVIEW and that didn't show anything on port 4550. But it continued to give error 10048.

On another not e- I did notice another nettalk server program on the same machine (not the program I'm having error 10048 with) had lost the PORT setting in the program.serversettings.xml.
I restored the value in the XML, restarted that program, and that is now working again.
But I never had a problem with this program before EITHER.

As part of troubleshooting I have updated to the latest NETTALK from the website.
So I am running a later version than I was previously.

Still stuck. But going to sleep now. The server can just wait if it gets stuck again 

[agustinh2000]

Hello, if you are using windows server 2008 or 2012 is a new update that generates this problem, I solved it by uninstalling the update KB4338830 of 11/07.

Agust

[Alan Telford]

I'm running Windows Server 2012 R2 (not Server 2012).
In the last month it has the following updates KB4338419, kb4338424, kb4338605, kb4338613, kb4338824, kb4339093, kb4338815. So I don't have the particular update you're referring to.

Note - suppossedly KB4338830 issues were resolved with KB4338816.
Have you tried installing KB4338816? Did you find it fixed the issue for you?

Being on Server 2012R2 I found that KB4338824 (Win2012R2) is equivalent of KB4338816 (Win2012) that you mentioned. And supposedly the issues are fixed for R2 in KB4345424.
I am installing KB4345424 to see if that resolves the issue.

Thanks for the pointer in this direction

[agustinh2000]

I'm not completely sure, but now I have the latest versions installed and I do not have that problem anymore

Comment if the problem was resolved ..
regards

[Alan Telford]

I am installing KB4345424 to see if that resolves the issue.

I can confirm that the problem is now resolved.
Installing KB4345424 resolved the problem and it has now run for >36 hours without requiring a reboot.

Thanks again for the pointer in the right direction!!!