“Could Not Find the Eaglesoft Messenger Server”: Causes and How to Fix It

Short answer: This error means a workstation cannot reach the Eaglesoft Messenger Server, a program that runs on your Eaglesoft server alongside the database. Either the Messenger Server is not running, or something is stopping the workstation from reaching it: a network drop, a firewall blocking port 5964, folder permissions, or the wrong server name. If every computer shows the error, check the server first. If only one does, start with that workstation.

What the Eaglesoft Messenger Server does

Eaglesoft Messenger passes messages and notifications between workstations through the server. It normally starts automatically when the Eaglesoft database server starts. When a workstation cannot find it, Eaglesoft shows “Could not find the Eaglesoft Messenger server” or a similar error mentioning port 5964.

Common causes

• The Messenger Server is not running on the server, for example after a restart.
• The workstation’s network connection dropped, often because the network card went to sleep.
• A firewall on the server or workstation is blocking port 5964.
• Windows permissions on the Eaglesoft folder or registry are wrong.
• The workstation is searching for the server automatically and finding the wrong one, or none.

How to fix it

Patterson’s KB 2155 says to start at step 1 if every computer is affected, and at step 3 if only one is.

1. Check the Messenger Server is running on the server. Look for the Messenger icon in the system tray, or for “Eaglesoft Messenger Server Program” in Task Manager’s background processes.
2. Start it if it is not running. Use the desktop shortcut, or Start | Eaglesoft | Start Patterson Eaglesoft Messenger Server.
3. Check permissions on the Eaglesoft folder and registry on the affected computer (Patterson KB 39994). This is an IT task.
4. Point the workstation at the server directly. In Technical Reference, untick “Auto Search for Server” and enter the server name or IP address. In version 21.20 and later this is under Settings; in 21.00 and earlier it is under Database Setup.
5. Check the network. Open File Explorer, select Network and confirm the workstation can see the server.
6. Check firewalls for anything blocking port 5964.
7. Reboot the server, at a time when everyone is out of Eaglesoft.
8. Confirm the office has internet access.

On the workstation, also stop the network card from sleeping: Device Manager, network adapter properties, Power Management, untick “Allow the computer to turn off this device to save power.”

A note on backups

Patterson’s KB 2031 points out that the Eaglesoft database engine and the Messenger Server must both be closed before a backup of the Eaglesoft data is made. If your backup routine stops these services overnight, make sure it starts them again afterwards. A backup job that stops the Messenger and never restarts it is a common cause of this error every morning.

Frequently asked questions

Can we keep working while Messenger is down?

Often, yes. The database is separate from Messenger. But some features that depend on messaging between workstations will not work, and the error usually points to a wider network problem worth fixing quickly.

Why does it only affect one computer?

When only one workstation is affected, the cause is usually on that computer: its network card, firewall, permissions or server setting.

What is port 5964?

It is the network port Eaglesoft Messenger uses. If a firewall blocks it, workstations cannot reach the Messenger Server.

Still down? Call (716) 463-5111

If the Messenger error keeps coming back, call Buffalo IT Services at (716) 463-5111. We look after the server, network and workstations Eaglesoft runs on, and work alongside Patterson. Learn more on our Eaglesoft IT support page.