If you are using Sage 50 on a regular basis, chances are that you've experienced this message at least once.
"Another user is already logged in" or
"Sage 50 is already logged in on this computer"
And the worst part? You already know everyone else is logged in.
The error doesn't typically mean Sage isn't functioning properly. This error means sage 50 customer support believes that that a user's session continuing to be active. It could be due an improper closing, interruption to the network, or a background program that didn't close correctly.
The good news is that, generally this issue can be corrected without reinstalling Sage or contacting supportand only If you can identify the issue creating the issue.
Let's break it down properly.
Sage 50 uses session and lock files to identify who's accessing the company's data. Once everything is shut down the files are deleted from the system automatically.
The error occurs when:
Sage closes unexpectedly
The system shuts down or restarts
Drops in connectivity to the network
Unintentionally, a user logs out.
Sage processes continue to be active in the background
In short, Sage believes a user session is always open, even if it isn't.
You'll usually see this error in one or more of these scenarios:
Sage opening Sage following a power outage
Switching users on the shared system
Accessing Sage 50 when it is in a multi-user setup
Open the same company file twice
Logging into the system after a forced Windows update
Remote desktop sessions ending abruptly
Knowing the time it happens helps determine how to address the issue.
Before trying any technical fixes ensure you follow the basic steps, but right.
Close Sage 50
Restart your system
Log back in and try opening Sage once more
Restarting can end any hidden background processes faster than you'd imagine.
For instance, if Sage was installed on multiple systems:
For other users, ask them to log out
Inspect if someone has Sage at a minimum or that is idle
Restart the server if necessary.
There are many "already logged in" errors are caused by open sessions that have been closed on a different computer.
Sometimes Sage may appear to be closed but she's not.
Press Ctrl + Shift + Esc
Open Task Manager
You can look for:
Peachw.exe
PeachwServer.exe
PeachTree.exe
Choose each and click End Task
Once done, reopen Sage 50.
This is the only way to fix the issue of a large number of users.
This is the most efficient remedy when the error fails to go away.
Sage creates locked files within the data folder of the company. If these files remain after the exit process is not properly completed, Sage blocks any new login attempts.
A typical place to be:
C:\Sage\Peachtree\Company
or one shared network drive, if you're using or a shared network drive if you're using multi-user access.
In the folder for companies You should look for files that have extensions such as:
.lck
.dta
.pta
.tmp
In the event that Sage is not working then you are free to clean these lock data files.
It is important to
Always delete or delete files while Sage is open for any operating system.
After deleting them, open Sage and try logging into the system again.
In multi-user environments Sage relies in background services for database. If these services cease to function there are login issues.
Press Windows + R
Type services.msc
Be on the lookout for:
Sage 50 Database Connection Manager
Sage 50 SmartPosting
Right-click - Restart
After restarting, wait for some time before opening Sage once more.
This step is very important for those who have Sage has been installed onto a server.
Sometimes, the error can be traced to permissions mismatches and not actual logins.
Register as Administrator (if it is possible)
Verify the rights granted to users.
Verify that the user's access isn't restricted to just one login
Check that the company's file isn't set to single-user mode
If Sage shut down while switching users, it could be in the process of resetting the session for the previous user.
Sage 50 is vulnerable to interruptions in the network.
If your system:
Does not use LAN, but Wi-Fi.
Has unstable connectivity
Infrequently, the server will disconnect from it.
You'll notice login-related problems more often.
Make use of wired LANs for Sage access
Avoid opening company documents via VPN unless it is configured properly
Ensure that client and server systems are on the same network
Network drops trigger ghost sessions. Sage does not receive the signal to end them.
To rule out issues with the network:
Transfer the company file to your local drive
Simply open it in Sage
If it starts without error, the problem is unrelated to data, but not network-related.
This test can help pinpoint the exact cause rather than thinking about the possible cause.
It sounds simple, but permission blocks can cause false login mistakes.
Just right-click Sage 50 shortcut
Select Run as an administrator
If this resolves the issue If this is the case, you can modify your system's permissions so that it doesn't happen again.
More recent Sage versions may be vulnerable to session lock issues especially following Windows updates.
Check:
Your current Sage version
Support for your Windows version
Installing the most up-to-date update frequently resolves recurring "already logged in" errors automatically.
Avoid quick fixes if:
Another user is authentically and is logged in
Sage is mid-process (posting and backing up, as well as restore)
The server was not checked.
Enforcing deletions even when Sage is active could cause damage to company data.
If not sure, wait and ensure before acting.
If none of the above measures can be completed, the problem may include:
Profiles of users with fraudulent information
Database of company damaged
Unsufficient server-client configuration
At this stage at this point, professional Sage support is recommended for avoiding data loss.
"The Sage 50 "already logged in" error is a bit scary, but in the majority it's simply Sage hanging onto a session that didn't close properly.
It is important to follow the following steps:
Confirm no active users
Clear background processes
Do not remove files from lock without care.
Stabilize the network
After being fixed the issue is rarely recurred unless there's another improper shutdown.
A clean and tidy exit can go an extremely long way in Sage.