On some configurations, the TCP port of the HTTP server is not closed properly when the Web Connector is closed or re-started. For some reason the .NET framework does not free the port until the Diafaan SMS Server service is completely stopped. When that happens, the Web Connector cannot start a new HTTP server because the port is still in use.
Unfortunately we have not been able to replicate this problem in one of our test systems and have not been able to find a solution. If you use an older version of the .NET framework on your server then updating to the latest version might help.
If I change a setting (in my case, allowing the API for server commands) and restart the connector, the http server fails to load.
It complains there is already one running on the port. I have to stop and start the server to get it running again. Disabling then renenabling the http server doesn't seem to make a different either, though I've not yet tried disabling the http server, making the change, restarting the connector then reenabling the http server (I can't afford any more down time at the moment; I'll wait until the dust settles).
"28/04/2020 12:03:24","Only one usage of each socket address (protocol/network address/port) is normally permitted","Web Connector General"
"System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at HttpServer.HttpListenerBase.Start(Int32 backlog)
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 602
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1275