Error "Integrated webservice could not be started"

[mopperle]

I'm getting this error suddenly. Didn t work with Imatch for about 4 weeks. Get it with latest 2020 and last 2019 version.
Configured is port 50519; Tried to find out with netstat which app uses this port, but no luck: netstat -b doesnt work as the list is continously being updated, so you cant scroll through it. netstat -ano gave me a PID, but couldnt find any app/service with this PID in Taskmanager.

Any idea?

[Mario]

The IMatch log file log file should contain corresponding E> error messages or W> warnings.

The most likely cause is that you have installed something (or something was installed) which blocks the port usually used by IMatch.
Have you just tried to reboot your system once?
Just pick another port in IMatch under Edit > Preferences > Application if you cannot find out which application / service / background task has allocated the port.

[mopperle]

Hi Mario,
this is the last entry in the log file:
Error starting web server: null context when constructing CivetServer. Possible problem binding to port.  'v:\develop\imatch5\src\imws\imatchwebservicescw.cpp(324)'

Yesterday after the second reboot the error disappeared. but today after starting imatch for the first time it came back. Strange thing is that this time netstat didnt give me anything, port 50519 was not listed at all. Also no blocking throuh security software.

Will try it with a different port and see if the error goes away finally.

BTW: the file mentioned in the error message exits nowhere on my PC.

[Mario]

This is clearly caused by something blocking the port.
It may even be fleeting (temporary) when something on your machine is opening a port to send or listen for a short time.

netstat -ab

usually returns the correct info and the process/application locking having the port open.

[mopperle]

Setting another port in IMatch solved the problem. At least for the moment.

[Mario]

This can always happen and hence the port  can be changed in IMatch.
Dynamically searching a port is surprisingly hard and error-prone so IMatch does not do it.
The fixed port also makes documenting and posting links easier.

But, Windows or any of the other software you use may decide to allocate a previously free port, blocking IMatch when IMatch starts later. That's just the nature of things in this modern world.