Sage 50 · 3 min read · Updated August 23, 2026

Your computer firewall is blocking one of those, or all, required processes" Sage 50

Sage 50 cannot reach your company data across the network because the firewall is blocking its connection, not because the file is damaged.


You are seeing this message because Sage 50 cannot open your company data from another computer on the network. The wording points at the firewall, and in most cases that is exactly right. Sage 50 on your workstation talks to the machine holding the data through specific network processes. When the firewall on either computer blocks those, the connection fails and Sage 50 reports that it cannot access the data.

The important thing to understand is what this message is not saying. It is not saying your company file is corrupt or damaged. It is a connectivity problem, not a data problem. Your data is almost certainly intact on the computer that hosts it.

Which firewall is doing the blocking?

There may be more than one. Windows Defender Firewall runs on every machine, and some antivirus suites ship their own firewall alongside it. The block can sit on the workstation you are using, on the computer hosting the company data, or on both. If the message appeared after a Windows update, an antivirus update, or a new security package, that change is the likely trigger.

What can you safely try first?

Start with the simplest checks. Confirm the computer hosting the data is on and that you can see its shared folder from your workstation. Restart both machines; this clears firewall rules that went stale after a sleep or a network change.

Next, check whether Sage 50 is allowed through the firewall. In Windows security settings, look at the list of allowed applications and make sure every Sage 50 entry is permitted on private networks, not just public ones. If your network is classified as public, Windows applies stricter rules; setting it to private often fixes access on its own.

If a third-party security suite is installed, check its own application rules as well. Some suites block unknown network traffic by default and need Sage 50 added to their allowed list.

When the problem is not the firewall

Sometimes the message appears even though the firewall is fully open. In that case the cause is usually one of these: the data-hosting service on the server machine is not running, the folder sharing or permissions were changed, or the network path itself is broken. Try opening the company file directly on the computer that hosts it. If it opens there but not from a workstation, the file is fine and the problem is purely network configuration.

If the file will not open even locally, the situation changes. That can indicate real damage to the data, and continuing to retry may make things worse. Stop and get the file looked at before anything else is attempted.

Where we come in

Our engineers handle both sides of this. If the file itself turns out to be damaged, we offer a Sage 50 and Simply Accounting database repair service that works directly on the data. If you are hitting this problem repeatedly and are considering a move instead, we also convert Sage 50 US to QuickBooks and Sage 50 Canada to QuickBooks.

If you are unsure which situation you are in, send us the file for a free evaluation. We will tell you whether it is a network issue or data damage, and what the fix would cost, before any work starts.