- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
If you are unable to logon to Sage you can try deleting the Queue.dta
file. All users MUST be logged out of Sage and Sage should not be
running. Sage will recreate the queue.dta file when it is restarted. The
Queue.dta file can be found in the ACCDATA folder for the Sage Company
Data that is experiencing the problem.
Note that the "Username already in use" message from Sage can occur if
Sage wasn't shut down tidily for that users session. If you are sure
that the user is not actually logged in it's OK to allow Sage to clear
the session and log in.
If you are unable to logon to Sage you can try deleting the Queue.dta file. All users MUST be logged out of Sage and Sage should not be running. Sage will recreate the queue.dta file when it is restarted. The Queue.dta file can be found in the ACCDATA folder for the Sage Company Data that is experiencing the problem.
Note that the "Username already in use" message from Sage can occur if Sage wasn't shut down tidily for that users session. If you are sure that the user is not actually logged in it's OK to allow Sage to clear the session and log in.
×