// SAGE 50 MULTI-USER
Sage 50 multi-user cannot connect to shared data
Your team opens Sage first thing and one — or every — PC throws up a ‘can’t connect to the shared data’ message, and the whole office grinds to a halt. Here’s the honest fix sequence, in the right order, and how we get everyone back in — usually the same day, working remotely. Rated 4.9 on Google.
- ● No fix, no fee
- ● Usually same-day remote fix
- ● Family-run since 1995
/01 — WHY IT HAPPENS
Why one PC can’t open the shared Sage 50 data
When a Sage 50 workstation cannot connect to your shared company data, it is nearly always because the one computer that holds the data has become unreachable — that ‘host’ PC is off or asleep, the Sage 50 Data Service running on it has stopped, a firewall is blocking the connection, or the workstation is running a different version of Sage 50 to the host. Fix those four things, in that order, and the shared data almost always comes straight back.
Here is the architecture, because it explains everything. Sage 50 keeps your accounts in a folder called ACCDATA, which sits on a single host computer or server. A background program on that host — the Sage 50 Data Service — controls the flow of data in and out of ACCDATA so everyone in the office works on the same live figures. Every other PC in the office does not keep its own copy; it reaches across the network and asks the host’s data service to open the same live folder.
So if the host is switched off, if its data service has stopped, if the network path to it is broken, or if the versions do not match, the workstations have nothing to talk to — and Sage stops. The steps below work through each cause the way we would on a call-out, cheapest and quickest first.
/02 — THE HOST & DATA SERVICE
Step 1: Check the host computer and its data service
Start at the host — the computer or server that actually stores ACCDATA. If you are not sure which machine that is, on a working PC open Help > About in Sage 50 and look at the data path; the computer name at the start of that path is your host.
Is it on and awake? The host must be powered on, logged in or at least running, and not asleep, before anyone else can open the accounts. A host that hibernates overnight or after a Windows update is a very common reason a whole office ‘loses Sage’ first thing in the morning. Wake it, or restart it, and try again.
Is the data service running? On the host, press the Windows key + R, type services.msc and press Enter. Look for two Sage services named for your version — for example Sage 50 Accounts Service v33 and Sage 50 Accounts Control v33. Both should show as Running. If either is stopped, right-click it and choose Start; if a service is running but Sage still cannot connect, right-click it and choose Restart. Sage also provides a Data Service Manager (search the Start menu for ‘Data Service Manager’, or open it from the Tools menu inside Sage) that lets you stop and restart the service and confirm it has started.
/03 — THE NETWORK PATH
Step 2: Check how workstations point to the data
Once the host and its data service are healthy, check how each workstation reaches the data. In Sage 50, Help > About shows the current data path. That path should point to the folder that contains ACCDATA — it never includes the ACCDATA folder itself.
UNC path or mapped drive? There are two ways a workstation can point at the host: a mapped drive letter such as S:\, or a UNC path such as \\SERVER\Sage\Accounts. Sage supports both, but a UNC path is the more reliable choice and it is what we recommend, because a mapped drive letter can silently drop off the network — the PC boots, Windows has not reconnected the drive yet, and Sage reports that it cannot find the data. If your mapped drives keep dropping, our guide on a mapped network drive that keeps disconnecting walks through switching to a more reliable UNC path.
Permissions. The Windows user on each workstation needs full read and write access to the shared folder on the host. Read-only access, or a share that was rebuilt after a new PC or a Windows update, will stop Sage opening the data even when everything else is correct. If your data lives on a desktop PC being used as an office server, double-check the share and its permissions there first.
/04 — FIREWALL & ANTIVIRUS
Step 3: Firewall, antivirus and the Sage ports
If the host is on, the service is running and the path is right but a workstation still cannot connect, a firewall or antivirus is the usual culprit — especially on a PC that has just been replaced, or straight after a Windows or security-software update.
Each version of Sage 50 talks over its own set of TCP ports — a control port, a service port and an application port. Version 33, for example, uses ports in the 34233 / 32233 / 32333 range; other versions use their own numbers, so always check Sage’s current firewall requirements article for the exact ports for the release you run. Those ports need to be open on the host and on every workstation, not just on the server.
To narrow it down quickly, temporarily disable the third-party firewall or antivirus on the affected PC and try Sage again. If it connects, do not leave protection switched off — instead add the Sage ports and program files as permanent exceptions, then turn protection back on. It is also worth a quick ping from the workstation to the host (Windows key + R, type cmd, then type ping followed by the host’s name or IP address) to confirm the two machines can see each other on the network at all.
/05 — VERSION MATCHING
Step 4: Make sure every PC runs the same Sage 50 version
A version mismatch is a sneaky one, because Sage will often let a workstation start but then refuse to open the shared company — or show an upgrade prompt — because the data has been converted to a newer format than that PC understands.
Every computer that shares the data must run the same version and build of Sage 50 as the host. A workstation still on last year’s release cannot open data that the host has already upgraded to this year’s. On each PC, check Help > About and confirm the version number matches the host exactly.
The safe upgrade order matters too: upgrade the host first, let it convert the data, then upgrade each workstation to the same version before anyone tries to log in. Upgrading one workstation ahead of the host, or leaving one behind, is a classic way to knock the whole office out of Sage. If your renewal or update has just landed and half the team can get in while half cannot, a version split is almost certainly why.
/06 — WHEN TO CALL US
When to call us — and how we fix it
Most Sage 50 connection problems are a quick fix once you know which of the four causes you are looking at — but when the office is at a standstill and invoices are not going out, you often do not have time to work through it yourself. That is exactly when to call us.
We work on your Windows network remotely first, usually the same day, so most offices are back into Sage without waiting for anyone to travel. We check the host and its data service, the network path and permissions, the firewall and the versions across every PC — in the right order — and we do not stop until your whole team can open the shared data again. It is no fix, no fee, and if you want us on hand for next time, business remote support starts at £24.38 per computer a month. For anything bigger, we also offer full server and network support.
One honest note: we are IT engineers, not accountants. We fix the connection — the network, the service, Windows, permissions and firewalls — and we always make sure your data is backed up before we change anything. Questions about postings, year-end or the figures inside your accounts belong with your bookkeeper, accountant or Sage. If you look after clients’ books yourself, our IT support for accountants is built around exactly this.
FAMILY-RUN SINCE 1995 · ★ 4.9 ON GOOGLE · 200+ COMPUTERS UNDER OUR CARE · NO FIX, NO FEE · SAME-DAY REMOTE SUPPORT
// GOOD QUESTIONS
Frequently asked
What does ‘cannot connect to the shared data’ actually mean?
It means the workstation could not reach the live company data held on your host computer. Sage 50 stores your accounts in an ACCDATA folder on one host PC or server, and a background program on that host — the Sage 50 Data Service — opens the data for everyone. If the host is off, its service has stopped, the network path is broken or the versions differ, the workstation has nothing to connect to.
How do I know which computer is the host or server?
On any PC that can open Sage, go to Help > About and look at the data path. If it is a UNC path such as \\SERVER\Sage\Accounts, the name straight after the first two backslashes (here, SERVER) is your host. If the path is just a local folder, that PC itself is the host. That host is the machine that must be on, awake and running its data service before anyone else can log in.
Do all our PCs need to run the same version of Sage 50?
Yes. Every computer that shares the data must run the same version and build of Sage 50 as the host. Once the host upgrades and converts the data, a workstation left on an older release simply cannot open it. Always upgrade the host first, then bring each workstation up to the same version before anyone logs back in.
Should we use a UNC path or a mapped drive for the Sage data?
A UNC path, such as \\SERVER\Sage\Accounts, is the more reliable choice and it is what we recommend. A mapped drive letter can silently disconnect when a PC starts up — Windows has not reconnected it yet, so Sage cannot find the data. A UNC path does not rely on the drive letter being reconnected. If your mapped drives keep dropping, see our guide on a mapped network drive that keeps disconnecting.
I turned off the firewall and Sage worked — is that the fix?
It tells you the firewall or antivirus was blocking Sage, but leaving protection switched off is not the fix — it leaves the whole office exposed. Instead, turn it back on and add the Sage ports for your version, plus the Sage program files, as permanent exceptions. Those exceptions need to be on the host and every workstation, not just the server.
We keep seeing ‘data service unavailable’ or that Sage can’t connect to the data service — what is that?
That points squarely at the host’s data service being stopped, blocked or unreachable. On the host, open services.msc and confirm the Sage 50 Accounts Service and Control services for your version are running, restarting them if not. If they are running, check the firewall ports and that the workstation can ping the host by name. If it will not stay started, the service or its ports usually need a closer look.
Can you just sort this out for us?
Yes — that is exactly what we do. We connect remotely, usually the same day, and work through the host, the data service, the network path, permissions, firewall and versions until your whole team is back in Sage. It is no fix, no fee. Call 01202 775566, text 07520 615332 or get in touch and we will get moving.
Can you fix problems inside our accounts or recover corrupt data?
We fix the connection — the network, the data service, Windows, permissions and firewalls — and we always back up your data before changing anything. Questions about postings, year-end or the figures inside your accounts are for your bookkeeper, accountant or Sage. If the data files themselves are damaged, that usually needs Sage’s own repair tools; we will tell you honestly if that is where you have landed.
How fast can you get us back into Sage, and what does it cost?
Most offices are back in the same day, because we start remotely rather than waiting to travel — and it is no fix, no fee. If you would like us on hand ongoing, business support starts at £24.38 per computer a month. We are remote-first across the UK, with home visits and collection across Bournemouth, Poole, Christchurch and the rest of Dorset if hands-on work is needed.
Sage down and the office at a standstill?
Call and we’ll get your team back into Sage — usually the same day, working remotely across the UK. No fix, no fee.
01202 775566 · help@365techies.co.uk · MON–FRI 9AM–5PM