Hi Niall

Sounds like Phil01_740 is the problem. Is there another user that might be logged in, or who may have had a problem with their workstation (maybe shutdown without logging out of Sage?)

No great expert but that's where I would start.

HTH

Bill

Hi Niall

Still sounds like an interuption occured during the ledger update process, so it thinks it is still running.

I have had a good look around Ask Sage but no luck. There are plenty of other fixes for ghost users, still accessing resources but none I could find for your problem. It may be one for Sage

Bill

this was an interesting one so I have received support from Sage.


This message indicates that the last time the person logged in using the user name indicated in the message, the program was not properly shut down. To resolve the problem, you should try to log into the program using that user name, and when prompted to remove the user from the request list, select yes. If you are not given this option, you should:

1) Open the problem company, then select About from the Help menu.
2) Within About, click the System Information tab, then from the left-hand pane, click Directories.
3) On the right-hand pane, right-click the data directory and select Open Folder.
4) Minimise the window that opens, then close Sage 50 Accounts altogether.
5) Ensure no other users are logged into that data set, then maximise the window that you minimised in step 4.
6) Locate and delete the queue.dta file then close all open windows and re-open Sage 50 Accounts.

In either instance, I would strongly recommend that you run Check Data within File Maintenance to ensure that there are no errors in the data. This is because the most common cause of data corruption is the program not being properly shut down, and we need to ensure that the data is not corrupt before you continue to process.