Openaccounts Clear Ghost users

Creation date: 7/16/2024 5:31 PM    Updated: 7/16/2024 5:31 PM    ghost user locked user
When OA user is locked out and no connection the the DB exists this is called a Ghost user. EPS must be contacted to get the daily password.
Then the following must be done.

How to Remove Ghost Users within OpenAccounts

Answer
NOTE: to prevent having to do this regularly, users need to ensure they are logging out of the system properly (do not click X in upper right hand corner).

There are sever; methods of resolving this message, both of which include closing the user’s session which is prohibiting access in System Utilities.

First, please check oasystem > logged on users to check and see who it is showing as logged in. If any of those users are showing, they need to first try logging in and log out properly.

The next method is to run the ‘Ghost Users’ routine to log off all users. This will also free up any ‘ghost users’ in OpenAccounts (sessions where the user has disconnected or logged out, but a database connection remains) which can also prevent user logging in, where a “Maximum Licensed Users Exceeded” or similar issue occurs.

Please be advised that this will disconnect all active user sessions. Therefore, please inform all users before carrying out the following:
  1. Log all users out of OpenAccounts, apart from the user who will be running these routines
  2. Press CTRL-W in OpenAccounts on the logged-in machine to display the System Environment Information window. For Version 8 Patch 5 onward you will need to access oasystem>>Tools>>Toolkit Routines (BS99)>> System maintenance - Run System Jiffy to get to the same window. Please note that you will need to obtain a password from support to run this.
  3. In the File Name box of the Information window type:
oa_menu/menujob.r
(or Browse to find the file - C:\openacc\oalive80\oapro91(10)\app\oa_menu\menujob.r)
  1. Click Run
  2. Close the session where the process was run
This will disconnect the user sessions from the database, please now try to amend the user in System Utilities again.