Skip to content
logo Knowledgebase

User is already logged on

Created on  | Last modified on 

Summary

This guide explains how to resolve the error message advising a user is already logged in to Sage Accounts Production Advanced (SAPA)

Description

The warning will appear if

  • The user name is already being used on another Computer or session.
  • The user was using the software and it crashed or was not closed properly.

Upgrade your licence

Growing business? Add more companies, users, or employees to your licence with ease. Leave your details and we’ll be in touch.

Image

 

 

Resolution

In the first instance, ensure no-one is actively logged into the system with that username.

 NOTE: Check Task Manager to ensure no instance of SAPA is running the background. 

To reset access after a crash or freeze

  1. Ask a different user to log into SAPA.
  2. Click Tools then click  Users Logged On.

    TIP: If this area is 'greyed out', the user you are logged on as does not have the access rights to access this area and you will need to log in as a different SAPA user

  3. Click Reset Crashed Users.
    A message will appear: 'Check for and reset any crashed users' with a list will of any users reset.
  4. Click Close and log out of SAPA.
  5. Log back into SAPA as the crashed user.

 If this doesn't resolve the issue

  1. Ask a different user to log into SAPA.
  2. Click Settings then click System Setup.
  3. Click the Folders tab and make a note of the Base Folder.
  4. Log out of SAPA.
  5. Using Windows File Explorer, browse to the base folder noted in point 3 and delete 'username'_ha_lgn.
  6. Log back onto SAPA as the crashed user.

 If the issue persists

  1. Ask all users to log out of SAPA.
  2. Browse to the base folder location.
  3. Locate the locks32.lck and logon.lgn files and delete them both.
  4. Log back in as the crashed user.

You may not be able to delete these files because they are locked. If this is the case move on to the next steps:

  1. Reboot the PC/Terminal Server that crashed originally to cause the error message. This should unlock the user's account.
  2. Reboot the server machine, you may need to refer to local IT support before doing this. Before you reboot the server machine, please make sure that all users are logged out of all applications containing data on the server.
  3. If the issue still persists login to Windows using the administrator account. If using a network install ensure you login to windows as a domain administrator and attempt to login to SAPA.

    TIP: If the login works without errors, this indicates it's permissions related. Please have your local IT support review your permissions settings on your Windows user account.

Upgrade your licence

Looking to add a company or maybe more users to your licence? Leave your details on this form and we'll be in touch.

Leave your details

Image