Sep 17, 2026 |
Matthew Thompson |
Read time :05 MIN
When Sage 50 works correctly on one computer but fails when several users try to access the same company file, the problem is often related to the network setup or Sage 50 Connection Manager. If the service is stopped, blocked by a firewall, incorrectly configured or installed with an incompatible version, workstations may be unable to open company data in multi-user mode.
This guide explains how to install and configure Sage 50 Connection Manager on a server, connect workstations, configure firewall access, map shared folders, and troubleshoot common connection problems. If you need immediate technical assistance, call +1-844-269-7070.
Sage 50 Connection Manager is a background service that helps Sage 50 workstations communicate with company data stored on a network server. It is particularly important when multiple users need to access a shared Sage 50 company file.
You may also see it referred to as Sage 50 Database Connection Manager or simply Database Connection Manager. In many Sage 50 environments, these terms refer to the service responsible for managing connections between Sage 50 and the company database.
The service normally runs on the computer where the Sage 50 company data is stored. Workstations connect to that computer over the local network.
Without a properly functioning Connection Manager service, users can experience problems such as:
For a multi-user installation, both the server and workstations must be configured correctly.
A typical Sage 50 multi-user environment follows this basic process:
Workstation → Network → Sage 50 Connection Manager on Server → Shared Company Data
The workstation sends a request to access the company data. Connection Manager running on the server handles the database connection while Sage 50 accesses the company files stored in the shared folder.
This means that troubleshooting should not focus only on the Sage 50 application. The server service, Windows permissions, network path, firewall, and software versions can all affect the connection.
Connection Manager and Sage Drive serve different purposes. Connection Manager is primarily associated with accessing company data through a networked server, while Sage Drive is designed to synchronize company data for access across various locations and devices.
| Feature | Sage 50 Connection Manager | Sage Drive |
| Primary setup | Installed on a local server or host workstation | Cloud-based synchronization |
| Company data | Stored physically on a local server/network drive | Synchronized through Sage’s cloud service |
| Multi-user network | True concurrent multi-user access over LAN | Allows access without relying solely on the same LAN |
| Internet dependency | Usually not required for local LAN access | Internet connection is generally required |
| Best suited for | Single-office teams sharing a local network | Remote workers, accountants, or multi-site teams |
| Firewall/network configuration | Inbound/outbound local firewall rules for Connection Manager service/ports | Outbound HTTPS internet access (port 443; no inbound server rules) |
The appropriate option depends on your Sage 50 edition, workflow, features, and how your company accesses its accounting data. Always verify compatibility with your specific Sage 50 version before changing the deployment method.
Before installing Sage 50 Connection Manager, prepare the server and network environment.
Requirements can vary by Sage 50 edition and release, so check the documentation for your specific version. In general, verify the following:
Before installing, repairing, updating, or reinstalling Sage 50 components, create a current backup of your company data.
If the company data is stored on a server, verify that the backup can actually be opened or restored before making significant changes to the installation.
In many Sage 50 installations, Connection Manager is included with the Sage 50 installation package rather than being a completely separate application that you download independently.
Select the installer for the appropriate version of Sage 50 that you are using. Never use the installation files for other Sage 50 versions since it may lead to compatibility issues.
If your installation package provides separate server or database-service options, use the option intended for the computer hosting the company data.
Follow these general steps to install the server component.
Installing the server component alone is not enough for a complete multi-user setup. Each workstation that will run Sage 50 should have the appropriate Sage 50 workstation installation.
Read More: Sage 50 Script Error
A firewall can prevent a workstation from communicating with the Sage 50 service even when the software is correctly installed.
Some Sage 50 configurations use ports in the 13531–13545 range. The exact ports required can depend on your Sage 50 release and configuration, so confirm the requirements for your version before creating permanent rules.
On the server:
Where appropriate, you can also create an application-based firewall rule for the Sage 50 program or Connection Manager executable.
Application rules can be preferable when you want to restrict access specifically to a known Sage executable instead of broadly opening a port.
Security software can have its own firewall or application-control features.
If Windows Firewall is correctly configured but Sage 50 still cannot communicate, check whether your antivirus or endpoint-security product is blocking Sage 50 or its database service.
Do not permanently disable security software simply to test the connection. Instead, use the vendor’s approved exception or allow-list mechanism.
A correctly shared company-data folder is essential for many network installations.
Locate the folder containing the Sage 50 company data.
Right-click the folder and open its sharing and security settings. Grant authorized users the permissions required by your Sage 50 installation and your organization’s security policy.
Open File Explorer and select This PC.
Choose Map Network Drive, select a drive letter, and enter the shared folder path.
For example:
\\AccountingServer\CompanyData
You can alternatively use the UNC path directly without mapping a drive.
Open the mapped drive or UNC path from the workstation and ensure that the authorized Windows user has access to the necessary files.
If the folder is unable to be opened in File Explorer, resolve any Windows networking or permission issues prior to addressing Sage 50.
Once the service and shared folder are ready:
Avoid moving Sage 50 company files to a different location without first confirming the new location is supported and properly configured.
A restart can resolve temporary service or connection problems.
If Restart is unavailable, use Stop followed by Start.
A repair is generally worth considering when the installation appears damaged, but the underlying Sage 50 version and server configuration are correct.
Consider a repair when:
A clean reinstall may be appropriate when repair does not resolve the problem.
Before reinstalling:
If the service is still not running after these steps, call +1-844-269-7070 for assistance with the installation and network configuration.
Connection problems can originate from the Sage service, Windows networking, permissions, firewall rules, or incompatible software versions.
| Error / Problem | Cause | Recommended Fix |
| Connection Manager is installed but not running | Service stopped or failed to start | Check services.msc, start the service, and review Windows Event Viewer if it stops again |
| Sage 50 cannot connect to the database | Firewall, service, or network problem | Verify Connection Manager, network access, and required firewall rules |
| Company file cannot be found | Incorrect path or unavailable shared folder | Check the mapped drive/UNC path and verify the folder exists |
| Multi-user mode does not work | Workstation/server configuration problem | Verify server components, permissions, and workstation connectivity |
| Connection times out | Firewall or network interruption | Test server reachability and review firewall/security software |
| Service remains on Starting | Service dependency or damaged installation | Restart Windows, check dependencies/events, then consider repair |
| Service is disabled | Windows service configuration changed | Open Services and set the appropriate startup configuration |
| Different Sage 50 versions detected | Version mismatch | Standardize the Sage 50 release across the environment |
| Firewall blocks Sage 50 | Missing inbound or application rule | Add the required Sage 50 exceptions for the installed version |
| Shared folder opens but Sage 50 cannot use it | Permissions or unsupported location | Verify read/write access and confirm the data location is supported |
Sage 50 error numbers can vary by product edition and release. Therefore, do not assume that a particular numeric code has the same cause in every Sage 50 environment.
If you see a specific error code, record:
This information makes troubleshooting significantly faster.
Remote Desktop Services, Terminal Server, and hosted Sage 50 environments require additional planning.
Typical LAN consists of a situation whereby the computer interacts with the server using the network available locally. In RDP system, the user can log onto the server running Windows instead.
Important considerations include:
For hosted environments, coordinate Sage 50 configuration with the hosting provider or system administrator before changing services or firewall rules.
Use these practices to reduce connection problems:
Your setup is generally functioning as expected when:
A successful Sage 50 Connection Manager setup involves more than installing one service on a server. The complete environment includes the server, workstations, shared company folder, Windows permissions, firewall configuration, compatible Sage 50 versions, and where applicable remote or hosted infrastructure.
For help installing, configuring, or troubleshooting Sage 50 Connection Manager, call Gotaxtation at +1-844-269-707
The terminology can vary by Sage 50 release and documentation. Connection Manager and Database Connection Manager are commonly used to describe the service responsible for managing Sage 50 database connections in a networked environment.
Not necessarily in the same way as a multi-user network installation. Connection Manager becomes especially important when company data is hosted on a server and accessed by multiple Sage 50 workstations.
Connection Manager is generally provided as part of the appropriate Sage 50 installation package rather than as a universal standalone download. Use the installer appropriate for your Sage 50 edition and release.
Some Sage 50 installations use TCP ports in the 13531–13545 range. However, required ports can depend on the Sage 50 release and configuration. Verify the ports applicable to your installation before creating firewall rules.
Open Windows Services by entering services.msc, locate the applicable Sage 50 service and check its status. If it is stopped, start or restart it. If it immediately stops again, investigate permissions, dependencies, installation damage, and Windows Event Viewer.
Sage 50 desktop products are generally designed around compatible Windows environments. A Mac or Linux computer should not be assumed to function as the Sage 50 database server simply because it can access a network share. Deployment options depend on the specific Sage 50 product and release.
Do not assume that a NAS or generic network storage device will work for hosting active Sage 50 company data. File sharing alone does not guarantee compatibility with Sage 50’s database requirements. Check the documentation for your exact Sage 50 release before moving company data to NAS storage.
No. Connection Manager is associated with a network/server-based environment, while Sage Drive is a separate Sage feature involving synchronization and remote access. They should not be treated as interchangeable technologies.
Sage 50 Canada Support: Avail Reliable Services
Jun 22, 2026
© 2026 GoTaxation | All Rights Reserved