If you are using Sage 50 regularly, chances are you've come across this message at some point:
"Another user is already logged in" or
"Sage 50 is already logged in on this computer"
And the worst part? You can be sure that that nobody else is logged in.
This error doesn't usually mean Sage isn't working properly. It's a sign that Sage is thinking the session of the user is still active somewhere--often due to an inadvertent termination, network break or a background process that did not end properly.
The good news is that, the majority of times, this error can be solved without reinstalling Sage or calling support-to- only if you know what's creating the issue.
Let's break it all down into a more precise manner.
Sage 50 uses session and lock files to identify who's accessing company data. Once the system is completely shut down those files are removed automatically.
The error is apparent when:
Sage closes unexpectedly
The system may crash or restart.
Drops in connectivity to the network
A user logs out incorrectly
Sage processes are still active in the background
In the simplest terms, Sage believes a user session is open even when it's not.
The most common error you'll see is within one of these scenarios:
Sage is opening Sage after a power outage
Switching users in the system
Accessing Sage 50 when it is in a multi-user setup
Opening the same company file twice
Logging in after a forced Windows update
Remote desktop sessions ending abruptly
Knowing when it appears helps decide the best way to correct it.
Before you try technical fixes, be sure to follow the rules, but do it in a way that is safe.
Close Sage 50
Restart your system
Log back in and try opening Sage again
A restart clears hidden background processes faster than you'd hope.
You have Sage installed, but Sage can be installed on multiple systems:
Request other users to log out
Verify that nobody has Sage minimalized or running slow
Restart the server if needed
Some "already logged in" errors result from open sessions that were not opened on another machine.
Sometimes Sage may appear to be closed but she's not.
Press Ctrl + Shift + Esc
Open Task Manager
Search for:
Peachw.exe
PeachwServer.exe
PeachTree.exe
Select each one and click End Task.
Once done, reopen Sage 50.
This alone will fix the issue for a large variety of users.
This is the most effective remedy when the error fails to disappear.
Sage creates locking files in the data folder of the company. If these files persist after an improper exit Sage prohibits logins from new users.
Habitual location:
C:\Sage\Peachtree\Company
or the shared network drive in case you're using or a shared network drive if you're using multi-user access.
In the folder for companies search for files that have extensions such as:
.lck
.dta
.pta
.tmp
If Sage is not functioning you are able to erase these lock files.
It is important to
Don't delete any files while Sage is running for any operating system.
After you delete them, reopen Sage and log in.
In multi-user environments, Sage is dependent on the background service of the database. If these services cease to function the login process, errors with logins occur.
Press Windows + R
Type services.msc
Be on the lookout for:
Sage 50 Database Connection Manager
Sage 50 SmartPosting
Right-click - Restart
When Sage is restarted, let it sit for one minute before opening Sage again.
This step is especially important in the event that Sage was installed on an server.
Sometimes the error appears due to mismatches in permissions, not authentic logins.
Log in as Administrator (if you are able to do so)
Verify user access rights
Make sure that the user isn't limited to only single login sessions
Make sure the company file isn't set to single-user mode.
If Sage crashed while switching users, it might be trying to hold the previous user's session.
Sage 50 is highly sensitive to interruptions in the network.
If your system is:
Uses Wi-Fi instead of LAN
Has unstable connectivity
It often disconnects from the server
Login-related issues will appear more often.
Utilize a wired connection to your LAN Sage access
Be wary of opening files for your company over VPN unless it is configured properly
Make sure that the server and client systems are connected to the same network
Ghost sessions are created by network drops. Sage never receives the signal needed to close them.
To rule out issues with the network:
Copy the company's data to your local drive
Then, open it directly in Sage
If it's opened without error message, the problem is connected to network and not with data.
This test helps determine your cause and avoids just guessing.
It's easy to understand, but permission blocks could cause misleading login errors.
Make a right-click Sage 50 shortcut
Choose Run as administrator
If this solves the issue alter your system's permissions to avoid repeating the problem.
Some older Sage version are much more susceptible to issues with session locks, particularly after Windows updates.
Check:
Your current Sage version
The compatibility of your Windows version
Often, installing the latest version can fix any recurring "already logged in" errors automatically.
Avoid quick fixes if:
A different user is actually signed in
Sage is mid-process (posting back, restoring, or posting)
The server hasn't yet been checked.
Letting deletions be forced while Sage is active may cause damage to information from the company.
If you're not sure, pause and examine before deciding.
If none of these steps can be completed, the problem may result in:
User profiles that have been fraudulent
Database of company damaged
Incorrect configuration of server and client
At this stage Professional sage support (https://covolunteers.com/members/flowercord34/activity/1342519/) is recommended in order to prevent data loss.
In the Sage 50 "already logged in" error can be intimidating, but in the majority of, it's just Sage keeping a session that wasn't closed properly.
Treat it methodically:
Confirm no active users
Clear background processes
Be sure to take care when removing lock files
Stabilize the network
Once the issue is resolved it's rare for the error to return after a shutdown that was improperly shut down.
The ability to be patient and clean up after yourself goes well with Sage.