repair
Sage 50 Multi-User & Network Repair
Sage 50 dropping to single-user, timing out, or locking people out? We get the whole office back on.
The situation
The company file opens on one machine but not another. Sage 50 drops the office to single-user without warning. A user is told the file is locked and cannot get in. Or the program simply will not connect to the data at all.
These are network and multi-user problems, not damage to the accounting data - but they stop work just as completely, and they are the kind of murky, environment-specific issue that is very hard to diagnose from the inside.
The failure looks different on each product
- Sage 50 US (Peachtree) runs on the Actian Zen (Pervasive) database. The classic symptoms are “Sage 50 is unable to connect to its database, Actian Zen, on computer X,” records or files reported in use by another user, and workstations quietly running a different engine version from the server after a Windows update - which produces failures on some machines and not others.
- Sage 50 Canadian (Simply Accounting) reaches the data through a Connection Manager service on the computer that hosts the company. The classic symptoms are “the Connection Manager is not installed on the machine that hosts your data” or is not running, a firewall or blocked port, “this file is locked by user X at computer Y,” and the maximum number of users being reached.
The wording is the product’s; the underlying causes are ports, permissions, service state, engine versions, and where the file physically lives.
The one that is really a self-inflicted wound
A large share of these calls come down to the company file sitting in a cloud-synced folder - OneDrive, Dropbox, Google Drive. Sage 50 is not built to have its live data files synced out from under it, and the result reads exactly like corruption or a locking failure. Sage’s own guidance is to keep the company out of a cloud-storage folder, and moving it to a proper server or shared location is often the whole fix.
What we do
Through a remote session, once we understand your setup, we sort out the Connection Manager or Actian service, the ports and firewall, and file permissions; reconcile mismatched engine versions across the workstations; clear stale locks left behind by a crashed machine; and, where the file is on a fragile share or a cloud-synced folder, move it somewhere Sage 50 can actually hold it. You end with an office that stays connected in multi-user without dropping out.
If the disconnection has left the company file itself damaged, that is handled as Sage 50 file repair alongside the network work.
What happens next
Tell us what is happening - the exact message, how many workstations need in at once, which machine hosts the data, and where the company file lives. We will confirm what is involved and what it costs before any work begins. The evaluation is free.
If the disconnections specifically involve a shared Sage Drive company, start with Sage Drive connection & sync repair - that one has its own careful recovery order worth following.