Symptom: The server's machine name or IP address has changed, and now the WaspTime client program will not open.
Resolution: On the server machine, go to Start > Run and enter regedit.exe. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wasp Technologies\WaspTime5\Options. In the right hand pane, the Server entry will be the SQL Server connection information, which will typically be in the form <machinename>\WASPDBEXPRESS. Depending on your network, yours could have the IP address in place of the machine name. For Enterprise version installs, WASPDBEXPRESS would be replaced by your SQL Server instance name, or left off if the database was installed to the default instance. Right click Server and select Modify, then update the machine name or IP address, leaving the \WASPDBEXPRESS as is.

You will also need to update Time Server Name. This is the pointer for the WaspTimeServer service, and will just have the machine name or IP address. Right click and Modify it as above, then close the registry editor.

Next, the service will need to be restarted. Go to Control Panel > Administrative Tools > Services. Scroll down to WaspTimeServer, and if it currently shows Started, right click on it and select Stop. Wait 30 seconds to ensure it has fully released its port, then right click it and select Start. Wait another 30 seconds to ensure it is fully started before attempting to launch the client program.

On the client machines, when the program attempts to launch but cannot contact the service by the machine name or IP address it was using prior to the change, it will poll your network to attempt to find the service, and then update itself automatically.

If it finds multiple instances of the service, it will show a list of all machines where the service was detected. If you see this list, you will need to check the machines where the service is running in error and Disable it from the services list. The service should only be on a single machine.