Technical and Installation Discussions

[RosieD]

Morning!

I'm using MAS90 v4.4 with Ascent Business Solutions Automated Service attached (same version).   We upgraded in June from 4.2.  I have full administrator rights to all companies.

I'm in the middle of physical inventory this morning and getting ready to get my users out and freeze inventory in about an hour or so.  I've got a user that has an irritating habit of logging on at the wrong time.  Currently, this user refuses to answer phone calls.  While I can disable his login for the remainder of the day, I still need to get him out now, and this question might prove to be helpful anyway.

I note the red "x" is gone from master console, and I don't see a "toggle" anywhere in role maintenance, user maintenance, or general setup screens to turn it back on.  Am I missing something or was this feature removed?  It worked at one time, because I remember doing it.

Probably not the best time to ask this... haha. Nothing like waiting until the last second.  But, can I still kill users from master console on my software version?

[zip]

The red X is there in 4.40.  Make sure you have full security access, and upon single clicking a line in the Master Console, the red X should be accessible.  Also note that it's not recommended to kill a user logon if they're in a data entry screen.

[jnelsonut]

I think you can only do this in Mas200.

In Role Maintenance - Security Events, it reads "Allow User to Kill Tasks through Master Console (Mas 200 only)"

Joe

Edited:  At least that's in 4.5 not totally sure for 4.4

[Heather]

That's what it is in v4.4 MAS90 as well. 

The red X appears only when I highlight my own sessions

[rmikolainis]

You can also do this from the server, go into computer/server management and you can look at the open files, highlight all the MAS90 files the user has open and close them.

I'd check to make sure they aren't in a data entry screen from within MAS first though.

Then disable there login from user maintenance until you are done.

[RosieD]

Sorry for the length of time it took to reply here--inventory was a little busier than expected. 

I'm a full rights administrator; there is absolutely nothing unchecked in library master for the role that I've assigned myself (administrator).  Essentially, I'm the company's super-user.

The red X only appears for my own tasks--no one else's. 

I do not have server room access (my machine is the point of entry for our group of users). 

Any other ideas?

-Rosie

[BigLouie]

Alnoor might add something to this or correct me if wrong but I THINK your issue is that you are on MAS90 and not MAS200. With MAS200 you have to ability to control other processses because this is a client server application. With MAS90 it is a file server and you really have no interaction with other users processes which is why you only see the red X for your task only.

[TheOtherGuy · Accepted solution]

Louis is spot on Kill tasks will not work in MAS 90 only MAS 200 butthe 'Shut Down All' will kick everyone out.

Remember when you use "Shut Down All" everything will close except an ok button on your desktop. 

You have to press that 'OK' or no one will be able to get back into the system.

[SPyle]

I reported this as a complaint, enhancement request to get it put back the way it was in the old 3.x days.  It might have been in the early 4.0/4.05.

Now in 4.4 and 4.5, if you shut down all, it closes everything, including yourself.  Yes, you used to be able to lock everything out but the terminal you were on.  Now, I'll shut down all, and I have some clowns that thinks it is a game (or network error) and will log back on as quickly as I do.  There is no way that I know of, short of editing the user id's, to perform some maintenance without some joker disrupting the process. 

It sure would be nice to have that kill option back, and also a "lockout / maintenance being performed" supervisor function and message to users trying to get back in when things like the (now daily) resorts have to be done.

I have seen the red X once or twice, but most of the time not, almost to the point that I wonder if I dreamt it worked.

[kanes]

What I've done is modify my sota.ini to add another "server" to the "Servers" section. It's my production server, but with another port number. I boot everyone out (clowns and all), go to the server, stop the application on the "production" port, restart the application on the "maintenance" port, then login from my workstation using the "maintenance" port. Clowns foiled.

When I'm done, I reverse the process.

Hope this helps.

Steve

MAS200 V4.30.21