Great question. I've been looking for that answer for a while. What seems to cause it is some Sage component hasn't shut down correctly. If you can, try rebooting the server. Try looking for any running Sage components and, assuming that nobody is in Sage, remove the various a4w processes from memory.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.