Sage kicks out user

Hi

I have 2 users: sysadmin and Steph.

My set-up:  Sage 50 premium, 2 computers and a wifi network. Data is stored in one computer, and sysadmin logs in this computer. Steph logs in a laptop.

After a while, Sage kicks out Steph, He can no longer log in. Sage tells that he is already logged in.

This happen often! We have to restart both computers, wich is boring needless to say!

How to manage to keep Steph logged in?

Any ideas?

Thank you!

regards, Danielle

Parents
  • 0

    The cause of the crashing could be a couple of things.

    1) The wifi network.  Database work should generally be done wired in.  Having said that I've seen wifi networks function ok but I don't like using them because they are generally slower than wired in networks and affected by the nearest microwave.

    2) If Steph's computer is set to sleep the network card or hard drive, the Sage 50 database could think the computer is no longer there and kick out the user.  This is different than Sage 50 removing the user and that is why when relogging back in the program thinks Steph is still logged in.  This is likely not the issue if Steph is constantly using Sage 50 when the crash happens.  But it might be the issue if he leaves the computer for an hour or two then comes back and is found to be kicked out.

    To correct the phantom log in issue without rebooting the computers, sysadmin can log into the database in single-user mode.  Just switching from mutli-user to single-user from the File menu may not work.  Close the software, leave it not running for a solid minute, then log back in directly as sysadmin in single-user mode.  If you get in, you can then use the File menu to switch to multi-user mode.

    If you don't get in, go in as mutli-user, then close the program and repeat the singe-user log in.

    If that doesn't work, there is a more technical way to fix it.  Close all versions of Sage 50, wait more than 1 minute.  Open the Task Manager, find the mysqld.exe process and kill it if it doesn't disappear in another minute.

Reply
  • 0

    The cause of the crashing could be a couple of things.

    1) The wifi network.  Database work should generally be done wired in.  Having said that I've seen wifi networks function ok but I don't like using them because they are generally slower than wired in networks and affected by the nearest microwave.

    2) If Steph's computer is set to sleep the network card or hard drive, the Sage 50 database could think the computer is no longer there and kick out the user.  This is different than Sage 50 removing the user and that is why when relogging back in the program thinks Steph is still logged in.  This is likely not the issue if Steph is constantly using Sage 50 when the crash happens.  But it might be the issue if he leaves the computer for an hour or two then comes back and is found to be kicked out.

    To correct the phantom log in issue without rebooting the computers, sysadmin can log into the database in single-user mode.  Just switching from mutli-user to single-user from the File menu may not work.  Close the software, leave it not running for a solid minute, then log back in directly as sysadmin in single-user mode.  If you get in, you can then use the File menu to switch to multi-user mode.

    If you don't get in, go in as mutli-user, then close the program and repeat the singe-user log in.

    If that doesn't work, there is a more technical way to fix it.  Close all versions of Sage 50, wait more than 1 minute.  Open the Task Manager, find the mysqld.exe process and kill it if it doesn't disappear in another minute.

Children
No Data