If you are using Sage 50 on a regular basis, chances are you've come across this message at least once.
"Another user is already logged in" or
"Sage 50 is already logged in on this computer"
And the part that is most annoying? You are aware that that no one else is at the same time.
This error doesn't usually mean Sage is malfunctioning. It's because Sage thinks that a user's session active, which is usually the result of an inadvertent termination, network break or an unfinished background process that didn't close properly.
The good news: almost always, this error can be solved without reinstalling Sage or calling supportor - in the event that you can pinpoint what's making it happen.
Let's break it down properly.
Sage 50 uses session and lock files to track who is accessing company data. When everything shuts down cleanly, these files are removed in a timely manner.
The error is apparent in the following situations:
Sage closes unexpectedly
The system may crash or restart.
The network connectivity is reduced
An account user logs out in error
Sage processes remain active in the background
In the simplest terms, Sage believes a user session is open even when it isn't.
This error will usually be observed in any of these scenarios:
Sage opening sage support telephone number after a power outage
Switching users in the shared system
Accessing Sage 50 through a multiuser setup
The same company file is opened twice
Logging in after a force Windows update
Remote desktop sessions ending abruptly
Knowing the time it occurs helps you decide what to deal with it.
Before trying any technical fixes take the easy route, but do it correctly.
Close Sage 50
Restart your system
Log back in, and try opening Sage once more
A restart is a way to clear the background processes faster than you'd expect.
You have Sage installed, but Sage installs on multiple systems:
For other users, ask them to log out
You should ensure that no one is running Sage downsized or idle
Start the server again if you need to.
Most "already logged in" errors originate from closed sessions that were forgotten on a different machine.
Sometimes Sage looks as if she's closed, yet isn't.
Press Ctrl + Shift + Esc
Open Task Manager
Watch out for:
Peachw.exe
PeachwServer.exe
PeachTree.exe
Choose them all and click End Task.
Once done, reopen Sage 50.
This alone will fix the issue for a significant amount of users.
This is the best remedy if the error just refuses to go away.
Sage creates locked files within the company data folder. If the files remain there after an improper exit Sage stops new logins.
Habitual location:
C:\Sage\Peachtree\Company
or a shared network drive if you're using or a shared network drive if you're using multi-user access.
Inside the company folder, look for files with extensions like:
.lck
.dta
.pta
.tmp
In the event that Sage is not functioning You can easily remove these lock files.
Be careful:
Always delete any files while Sage is open across any platform.
After you have deleted them, open Sage and log into the system again.
In multi-user environments Sage depends on the background service of the database. If these processes stop and login errors are triggered, they will occur.
Press Windows + R
Type services.msc
Be on the lookout for:
Sage 50 Database Connection Manager
Sage 50 SmartPosting
Right-click - Restart
Once it is back up, wait at least a minute before trying opening Sage once more.
This is particularly important particularly if Sage is installed on a server.
Sometimes the error appears due to permissions not matching, rather than actual logins.
Connect as Admin (if it is possible)
Verify user access rights
It is important to ensure that the user's login is not restricted to a single login session
Verify that the company's file hasn't been set to single-user mode
If Sage was to crash while switching users, it may still be being held by the previous user's session.
Sage 50 is vulnerable to interruptions to networks.
If your system is:
Uses Wi-Fi instead
Has unstable connectivity
Sometimes, the server disconnects
You'll see login-related errors more frequently.
Use a wired or wireless LAN for Sage access
Avoid opening company files through VPN unless you have it configured correctly
Make sure that the server and client systems are connected to the same network
Ghost sessions are created by network drops. Sage doesn't get the signal to close them.
To rule out problems with networks:
Copy the company's files to your local drive
You can open it directly in Sage
If it is able to open without error message, the problem is related to the network, not data.
This test helps determine to the source of the issue instead of trying to guess the cause.
It may sound straightforward, but permission blocks can lead to misleading login errors.
Then right-click Sage 50 shortcut
Choose Run as an administrator
If this fixes the issue, adjust your system permissions to ensure that the issue doesn't recur.
More recent Sage versions can be more susceptible to issues with session locks, particularly after Windows updates.
Check:
Your current Sage version
The compatibility of your Windows version
Installing the latest update typically solves recurring "already logged in" errors automatically.
Avoid quick fixes if:
Another user is authentically not logged in
Sage is a mid-process (posting and backing up, as well as restore)
The server hasn't been checked
Forcing deletions while Sage is open can destroy the company's data.
If you're unsure, take a moment to check before taking action.
If none of the steps do the trick, the issue may have to do with:
User profiles that have been fraudulent
Database of company damaged
A wrong server-client configuration
At this stage at this point, professional Sage support is recommended to protect data from loss.
In the Sage 50 "already logged in" error is a bit scary, but in the majority it's simply Sage being held onto a session that wasn't closed properly.
Do it carefully:
Confirm no active users
Clear background processes
Take the lock files off with care.
Stabilize the network
After being fixed it's rare for the error to return The error isn't likely to occur again unless there's an additional shutdown that.
Be patient and have clean exits. an extremely long way in Sage.