Opening Winlink Management results in "Cannot connect to server:localhost" error

The message "Cannot connect to server: localhost" is the result of WinLink trying and failing to communicate with the codebase database server that it installs to manage the data concerning your units and customers. This can be caused by a few easily resolved issues that may or may not be applicable to you depending on your configuration:

If you are running a single WinLink client/server setup:

1. Is the install process completed? If so, when it was installed was the client/server option selected, or just client? For a single PC setup, client/server is necessary. Reinstall the server with a client/server setup and reimport your database from a backup.

2. Has the codebase database server crashed? This can occur some times especially after unexpected hardware crashes or power outages due to a corrupted S4Server log file. The easiest solution is to run c:\winlinkv4\server\serverreset.bat, which is included in the regular installation of WinLink. If that is not an option then delete the c:\codebase\server\s4server.log file, then click on start>run and type in services.msc then click on OK, then find codebase database server, right click on it and select start. After it starts the service up, try running Management again.

If you are running multiple WinLink clients and a single WinLink server, follow the steps listed for the single client/server setup on the server machine. If that does not resolve the issue on all of your clients, try the following:

1. Make sure that the IP address of your server machine has not changed.

2. Click on Start>Programs>WinLinkV4>WinLink Configuration. When that opens, make sure that your clients are all pointed to the correct IP address/hostname, port and are using the right login information.