If you receive the message Sage 50 Connection Manager is installed but it isn't running, you may be unable to open your company data or connect to Sage 50 from a workstation. This issue commonly occurs when the Connection Manager service is stopped, disabled, blocked by security software, or incompatible with the Sage 50 version installed on the computer.

The Connection Manager is especially important when Sage 50 company data is stored on a server and accessed by multiple computers. Sage recommends checking the Connection Manager service, its version, Windows updates, and security settings when this problem occurs.

What Is Sage 50 Connection Manager?

Sage 50 Connection Manager is a server component that helps Sage 50 communicate with company data stored on a local computer or network server. In a multi-user environment, the Connection Manager needs to be installed and running on the computer where the company data is stored.

When the service is stopped, Sage 50 may display messages indicating that it cannot find or communicate with the Connection Manager. Sage identifies a stopped Connection Manager service, missing network exceptions, and service startup timeouts as possible causes.

Why Is Sage 50 Connection Manager Not Running?

Several issues can prevent the Connection Manager from starting correctly. Common causes include:

• Connection Manager service is stopped.
• Service startup type is set to Disabled.
• Windows updates are pending.
• Sage 50 versions are incompatible.
• Connection Manager installation is damaged.
• Firewall or antivirus software blocks the service.
• Windows permissions prevent the service from starting.
• The server has not been restarted after an update.
• Required network ports are unavailable.
• Sage 50 was incompletely installed or updated.

Sage specifically recommends checking whether the Connection Manager versions match between the server and workstation.

How to Fix Sage 50 Connection Manager Not Running

Try the following solutions in order.

1. Start Connection Manager From Windows

The quickest solution is to manually start the Connection Manager.

1. Click the Windows Start button.
2. Search for Sage 50 Connection Manager.
3. Open the application.
4. Check the Running status.
5. If it says No, select Start Service.
6. Wait until the status changes to Yes.
7. Click OK.
8. Open Sage 50 and try accessing the company file again.

Sage recommends this procedure when the Connection Manager is installed but not running.

2. Restart the Connection Manager Service

If clicking Start Service does not resolve the problem, restart the Windows service.

1. Press Windows + R.
2. Type services.msc.
3. Press Enter.
4. Locate Sage 50 Database Connection Manager.
5. Right-click the service.
6. Select Stop if it is running.
7. Wait a few seconds.
8. Right-click it again and select Start.
9. Try opening Sage 50.

Sage also recommends restarting the service through Windows Services when the Connection Manager cannot be started normally.

3. Change Startup Type to Automatic

If the Connection Manager keeps stopping after a restart, check its startup configuration.

Open Services and locate Sage 50 Database Connection Manager. Right-click it and choose Properties.

Under Startup type, select:

Automatic

You can also use Automatic (Delayed Start) where appropriate.

Click Apply, then Start and OK.

Sage identifies a disabled startup type as one possible reason the Connection Manager service cannot start.

4. Restart the Computer or Server

A restart can clear temporary service, process, or Windows-update problems.

If your Sage 50 company data is stored on a server, restart the server rather than only restarting the workstation. Before doing this, make sure all Sage 50 users have saved their work and exited the program.

Sage recommends restarting the computer or server and checking for pending Windows updates when the Connection Manager is not running.

5. Check the Connection Manager Version

An incompatible version can prevent Sage 50 from communicating correctly with the server.

Open Sage 50 Connection Manager on the server and workstation and check the version listed under the application's About information.

Sage recommends ensuring that the Connection Manager version on the server matches the workstation. If the versions do not match, install the appropriate newer Connection Manager on the server.

This check is particularly important after upgrading Sage 50.

6. Check Windows Firewall and Antivirus

Security software can prevent the Connection Manager from starting or communicating across the network.

Sage identifies firewall and antivirus restrictions as possible causes of Connection Manager and network communication problems.

For troubleshooting, an administrator can temporarily test whether security software is responsible. If the Connection Manager works when security software is disabled, configure the appropriate Sage exceptions instead of leaving protection disabled.

Because firewall configuration affects system security, changes should preferably be made by your IT administrator.

7. Run Sage 50 Connection Manager as Administrator

Windows permissions can sometimes prevent the Connection Manager from starting correctly.

Right-click Sage 50 Connection Manager and choose Run as administrator. If Windows requests administrator credentials, enter an authorized account.

Sage lists insufficient permissions and administrator-rights issues among possible causes of Connection Manager startup problems.

8. Check the Server Connection

If the company data is stored on another computer, verify that the workstation can communicate with the server.

Check that:

• The server is powered on.
• The server is connected to the network.
• The shared company folder is accessible.
• The Connection Manager is running on the server.
• Workstations can communicate with the server.
• Sage 50 versions are compatible.

Sage recommends verifying the Connection Manager on the same server where the company data resides and checking the network connection when communication errors occur.

9. Reinstall the Connection Manager

If the service cannot start after the previous steps, the installation may be damaged.

Sage provides a server installation process in which you run the Sage 50 installer, select Advanced, and then choose Server-only under Sage 50 Server Components.

If the Connection Manager is severely damaged, Sage also documents a complete removal and reinstallation procedure. That procedure involves deleting the Connection Manager service and related files, so it should be performed carefully and preferably with appropriate technical knowledge.

Always back up your Sage 50 company data before performing major installation changes.

10. Check for the Connection Manager in the System Tray

If the Connection Manager application is installed but its icon does not appear in the Windows system tray, restart the computer first.

Sage also provides a method for manually launching the system-tray application from the Connection Manager installation folder. If the required executable is missing, Sage recommends reinstalling Sage 50.

Sage 50 Connection Manager Starts and Then Stops

Another related problem occurs when the Connection Manager starts but immediately stops.

Possible causes include:

• Firewall restrictions.
• Port conflicts.
• Interrupted Sage 50 installation.
• Mismatched Connection Manager files.
• Security software interference.
• Other Windows service problems.

Sage notes that port 13531 can be involved in this type of startup problem and recommends checking firewall settings and the Connection Manager installation.

If advanced Windows configuration is required, avoid changing the Windows Registry unless you understand the consequences or have assistance from a qualified administrator.

Frequently Asked Questions

Why is my Sage 50 Connection Manager not running?

The service may be stopped, disabled, blocked by security software, incompatible with your Sage 50 version, or affected by a damaged installation. Start by opening Sage 50 Connection Manager and selecting Start Service.

How do I restart Sage 50 Connection Manager?

Open Windows Services, find Sage 50 Database Connection Manager, select Stop, and then select Start. You can also restart it directly from the Connection Manager application.

Why does Sage 50 Connection Manager keep stopping?

Firewall restrictions, an interrupted installation, version mismatches, or other Windows configuration problems can cause the service to stop.

Should Connection Manager be running on the server?

Yes. When Sage 50 company data is stored on a server, the Connection Manager should be installed and running on the computer where the data is stored.

What should I do if Connection Manager will not start?

First restart the service, check its startup type, restart the computer, verify version compatibility, and check firewall or antivirus restrictions. If the problem continues, repairing or reinstalling the Connection Manager may be necessary.

Conclusion

When Sage 50 Connection Manager is not running, begin with the simplest solutions: open the Connection Manager, select Start Service, and check the Windows service configuration. If the problem continues, verify the Connection Manager versions, restart the server, check firewall and antivirus settings, and confirm that the company data is stored on the correct computer.

For persistent problems, repairing or reinstalling the Connection Manager may be necessary. Before making significant changes to Sage 50 or Windows, create a current backup of your company data and consider involving a qualified system administrator.