Unable to open company at this time due to Sage Drive lock conflict" explained
The message means another session or device is holding the Sage Drive copy of your company, so yours cannot open it.
The message “Unable to open company at this time due to Sage Drive lock conflict.” sounds like a technical failure, but it usually is not one. Sage Drive lets one copy of the company hold the live lock while other computers work from a downloaded copy. This message means Sage believes that lock is already taken, or is stuck in a state where it cannot tell who holds it, so your workstation is refused.
In most cases the lock is simply held by someone else. In some cases the lock is stale: a session that crashed, a machine that was shut down mid-sync, or an interrupted upload left Sage Drive thinking the company is still checked out when nobody is actually using it.
Check whether someone else has the company open
Ask around before changing anything. If a colleague has the company open through Sage Drive, the message is working as designed. Their session holds the master copy, and yours opens as a read-mostly downloaded copy or waits, depending on your setup. The cleanest fix is for that person to close the company properly, let Sage Drive finish syncing, and then open it from your machine.
Close Sage completely on every machine
A crashed or still-running session is the most common cause of a stale lock. On each computer that uses the company, close the company file, exit Sage 50 entirely, and check that no Sage process is lingering in the background before restarting. A restart of the workstation, done after everything is closed, clears most one-off lock states.
Sign out and back in to Sage Drive
The lock information lives on Sage’s cloud side, not only on your computer. Signing out of Sage Drive and signing back in, on the machine that normally holds the master copy, forces the service to re-check who owns the lock. Do this only after all sessions are closed, or you may simply recreate the conflict.
Wait, then try again
If the lock was left behind by an upload or sync that was interrupted, it can clear itself once the sync times out and retries. Give it some time with Sage closed on the other machines, then attempt to open the company again. If it opens, let the first full sync finish before others reconnect.
When the lock will not release
Sometimes the conflict persists no matter what you do. That usually points to a deeper problem: a damaged local copy of the company, a sync state that cannot reconcile, or data corruption inside the file itself. Repeated lock conflicts, especially after a crash, are a reasonable sign the company file should be checked before more work is entered into it.
Our engineers repair damaged Sage 50 (Peachtree and Simply Accounting) databases and can also convert Sage 50 data to QuickBooks if you would rather move off Sage Drive entirely. If the lock refuses to clear, send us the file for a free evaluation and we will tell you what is wrong and what the options are before anything is charged.