Sage Connection Issues
Woosage50 connects (logs on) to Sage using the Username and Password from Settings>Sage at the start of each operation within the processing cycles and disconnects (logs off) when that operation is complete. The Woosage50 login credentials from the Settings>Sage must not be used by any other user, as this will prevent Woosage from connecting to Sage.
Occasionally, if Sage is terminated while Woosage50 is processing (e.g. power failure) then Sage shows that the Woosage user as still being logged on when it resumes, which results in error 10065 (The Sage username used by Woosage is already logged into Sage).
Remove Woosage User from Active Sessions
If this happens, login to Sage as MANAGER and select Settings>User Management>Active Sessions. Highlight the Woosage username in the list and click Remove. You will then get a warning that data may be lost and you will need to confirm by clicking Yes. Woosage should then run as normal on the next processing cycle.
Warning! This is the removal of the active session for the Woosage user NOT the deletion of the Woosage user from the system.
Alternative Method
If Sage has stopped unexpectedly there may be multiple users that can't login. In this case you may need to remove the QUEUE.DTA file as described in the following Sage knowledgebase article.
Related Articles
Sage Data Service
According to Sage, the Data Service acts as a gateway and controls the reading and writing of data and is intended to increase the robustness of the system, improve data security, and help to optimise performance. It is installed and runs ...Installation and Setup of Woosage for Sage Accounting
Woosage for Sage Accounting is intended to be a self-install application and everything you need to do this is contained is right here in just 4 easy steps. Install the Woosage plugin Add your subscription Identifier Authorise Woosage to access your ...Issues with the Woosage50Service Connecting to the Website
Occasionally, Woosage50 encounters issue when the Woosage50Service tires to connect to the website. This is usually due to website or server security measures and common causes and solutions are: Server/site blocks API requests - solution is to is ...Resolving Woosag50 Remote Service Issues
The Woosage50 plugin on the website interacts with a Windows service that runs remotely on your local network. The service, called Woosage50Service, runs in the background and acts as a bridge between Sage and your website. It runs continuously, ...Sage Backup conflicts
Historically, Sage would not run backups while other users where logged in to the same company in Sage. If Woosage tried to run when a backup was running, then it reported an "exclusive mode" error and paused until the next processing cycle was due. ...