Why do disconnected logins occur and how do you fix them in Sage 200 Professional?
Disconnected logins are a common issue for many Sage 200 users and can occur for a range of reasons.
In this Tip of the Week, we explain the reasons behind how your login could be disconnected, how to fix it and how to prevent it from happening again.
Additionally, you can watch the short tutorial here to help better your understanding.
Why Do Disconnected Logins Occur?
A disconnected login could be the result of the internet going down or you may have had to crash out of Sage unexpectedly.
Sage will try to hold on to the screen you are in at that time to preserve the data, but you will then have to clear this lock down later or you won’t be able to get back to what you were doing.
This won’t always be your own username either. If anyone else in the system has a disconnected login, they can block you from getting to where you need to be.
How To Fix a Disconnected Login
Have you ever come across a screen with this error message: ‘Unable to access SOOPOrder because you are currently accessing SOPOrder’?
You know this is incorrect, so why does the system think this and how do you get out of it?
To clear this, navigate to the ‘Tools’ option, which is located in the cog icon at the top right of your Sage window.
Next go to ‘User Login Status‘.
The first tab this opens is the ‘Disconnected Logins’ tab. Anyone in here should be cleared out, even if it hasn’t caused you a problem yet.
Highlight all users in this tab and click ‘Log off’. You can now access what you were trying to do before.
The second tab here is a record of users who are currently logged in and using the system, but don’t worry, you can’t accidentally end a ‘real’ session, this is just for information only!
Frequently Asked Questions About Disconnected Logins in Sage 200
What is a disconnected login in Sage 200?
A disconnected login in Sage 200 occurs when a user session is not closed correctly, often due to a system crash or internet interruption. The system may still think the user is logged in, which can block access to certain screens or functions.
Why do I get errors like “Unable to access SOPOrder” in Sage 200?
This error typically happens because Sage believes another session (often a disconnected login) is still using the same screen or record. Even if you are not actively using it, a lingering session can prevent access until it is cleared.
Can another user’s disconnected login affect my access?
Yes, disconnected logins are not always tied to your own account. If another user’s session is stuck, it can block shared records or modules and prevent you from working until it is cleared.
How can I prevent disconnected logins in Sage 200?
To minimise disconnected logins:
- Avoid closing Sage abruptly (e.g. forced shutdowns)
- Ensure stable internet connectivity
- Log out properly when finished
- Regularly check and clear disconnected sessions in User Login Status
These steps help prevent access issues and improve system performance.
Written by: Gary Butler, Sage Support Team Mentor at PKF Smith Cooper Systems
Reviewed by: Gary Butler, Sage Support Team Mentor
Last reviewed: May 2026
If you would like more support concerning disconnected logins or your Sage system, you can contact us via the enquiry form or contact our support team at sagesupport@pkfscs.co.uk.
To stay in the loop about our latest tips, make sure you are following us on LinkedIn and Facebook!
NB: Be advised that the information/accuracy in this article may differ depending on which version of Sage 200 you use, as a result, some options and processes might look different.
