Service terminated because it was unable to initialize tcp/ip communications: Address already in use!
The error message "WebWatchBot Service terminated because it was unable to initialize tcp/ip communications: Address already in use!" usually means that another program/service is using port 444.
The cause for this error is if there are two instances of WebWatchBot running, e.g. two or more processes named "WWBGui.exe" or "WWBServer.exe" or if another program is using port 444.
To check for a conflict, open a dos command prompt window and type "netstat -a". This will produce a list of all the ports in use on your system. For example:
TCP MACHINENAME:444 MACHINENAME:0 LISTENING
This shows that something has a lock on port 444.
And a line like this:
TCP MACHINENAME:444 localhost:2692 ESTABLISHED
This shows that something is connected.
If you have the "Established" line, then something is already using that port - perhaps another instance of WebWatchBot. In this case, you can open the Windows task manager and search for a running process named "WWBGui.exe"
In the event of a conflict with another program, you can change the port numbers used by WebWatchBot. Since you cannot open WebWatchBot Manager, you will need to modify the registry.
- Stop the WebWatchBot service (named WWBServer)
- Open the registry editor: Start -> Run, type "regedit", then press Enter.
- Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Exclamationsoft\WebWatchBot\5.0\General
- Double click "TCP_SERVER_PORT", select "Decimal" (ensure HEX is not selected) and enter a new port number then click OK.
- Navigate to: HKEY_CURRENT_USER\Software\ExclamationSoft\WebWatchBot\5.0\Client
- Double click "TCP_SERVER_PORT", select "Decimal" (ensure HEX is not selected) and enter the same port number you entered on step 4 then click OK.
- Start WebWatchBot Manager - if you don't get the error then start the service when prompted.