Sage 50 has lost contact with the current Sage Drive company
Sage 50 cannot reach the cloud-hosted copy of your company file, usually due to a sync, network, or upload interruption.
When Sage 50 tells you it “has lost contact with the current Sage Drive company,” it does not mean your data is gone. It means the local copy of Sage 50 on your computer can no longer communicate with the cloud-stored version of your company file that Sage Drive manages. The connection dropped mid-session, and Sage 50 is refusing to continue reading or writing until it can confirm it is working against the right data.
What usually causes it
The message appears when the sync channel between your workstation and Sage Drive breaks. Common triggers: a brief internet outage or Wi-Fi hiccup, Sage Drive’s background service stalling, the hosting machine (the computer designated as the Sage Drive host) going to sleep or rebooting, or a previous upload that did not finish cleanly. Less commonly, the local cached copy of the company file itself is damaged or partially written, and Sage 50 will not trust it.
Wait and reconnect
The safest first step is to close Sage 50 completely, confirm your internet connection is stable, wait a few minutes, and reopen the company. If Sage Drive simply stalled, the connection re-establishes on its own and you can resume working. Try this before attempting anything more invasive.
Check the hosting computer
If your Sage Drive setup designates one machine as the host, that machine must be awake, online, and running Sage 50’s services. If the host went to sleep, lost its network connection, or was rebooted, every workstation sharing the company sees this message. Verify the host is up and Sage Drive is active there before trying again on your own workstation.
Re-download the company from Sage Drive
When the local cached copy has drifted out of sync or is suspected of corruption, Sage 50 can re-download a fresh copy from Sage Drive. This replaces the local cache with the last successfully uploaded version. Be aware that any entries you made after the last successful sync may not be in that cloud copy, so this step should be taken only when reconnecting does not work.
When the cached file is damaged
If re-downloading fails, or Sage 50 still cannot open the company afterward, the local cached file may be corrupt. In that situation the file needs professional attention. Our engineers regularly repair damaged Sage 50 and Simply Accounting databases, and we can evaluate yours at no cost. The right fix depends on what is inside the file and how far the damage extends, so we assess each one individually rather than guessing.
If repeated attempts to reconnect leave you locked out and you are considering moving away from Sage Drive or switching platforms entirely, we also convert Sage 50 data to QuickBooks when that is the direction you want to go.
The practical next step is to send us the cached company file for a free evaluation. We will tell you what is wrong, whether it can be repaired, and what is involved, before you commit to anything.