'You cannot access (option) for (record) because (user name) is accessing (option) for this record on machine (computer name)' when working in Sage 50 Accounts

Summary

If you get this error message in Sage 50 Accounts, this article will explain how to resolve it.

Description

Some options in Sage 50 Accounts are classed as partial zones, which means that a particular account or record can only be accessed by one Sage user at any time. If you try to access a record and another user is working on the same record within a partial zone option, a message similar to the one below appears.

Resolution

If the other user is currently working on the record

Wait until the other user closes the required record, then try and access the record again.

If the other user doesn't appear to be logged in

You need to try and log in as the MANAGER user:

If you can log on as MANAGER - Click here >

Steps for v27 and above

Log on as MANAGER.
On the menu bar click Settings
Click User Management, then click Active Sessions.
Select a user except for MANAGER, then click Remove then click Yes.
NOTE: If you remove users, we recommend that you run a check data. If any errors are reported, please refer to My data.
Repeat step 4 until MANAGER is the only one on the list, then click Close.
Try and access the required record again.

Steps for v26 and below

Log on as MANAGER.
On the menu bar click View, then click User List.
Select a user except for MANAGER, then click Remove then click Yes.
NOTE: If you remove users, we recommend that you run a check data. If any errors are reported, please refer to My data.
Repeat step 3 until MANAGER is the only one on the list, then click Close.
Try and access the required record again.

If you can't log on as MANAGER - Click here >

Log on using the username mentioned in the error message.
When prompted, click Close session or Yes, then close out of Sage Accounts.
Now log on and try and access the required record again.

NOTE: It's likely that you've received this message because Sage Accounts has previously closed unexpectedly. We recommend that you run a check data, if any errors are reported, please refer to My data.

Issue persisting?

If the issue persists, please refer to the article - How to delete the queue.dta file.