Sage 100

Client is asking why they can't kill users from master console anymore in newer versions. Does anybody know a work around to this since is so hard to correlate task manager tasks to specific users?

What version is ""newer""? I ask because I am on v4.30 and do it all the time with no problem.

If MAS 200 you have to turn on Spawn Tasks from Server.

In Taskmanager I had PID and in the Master Console I had PID and they match up for me.

@LouisAraiza How do you kill them. Just via the task manager or via master console? @RobertWood What will turning on spawn tasks do for you? (other than show a million little tasks on the task bar)

Also, is there a way to lock out users other than one group from logging in? They want the accounting department to be able to go through closing operations but prevent others (especially jobops timekeepers) from logging in while they are doing this (goes back to the concurrency issues in MAS90/200)

It usually let's you kill them from master console.

It can cause the system to run slower.

I jsut kill them from the master console.

I only use the Task Manager if something is really really stuck but that is rare.

On the preventing users during closing, If they are on 200 you can setup a link to run as MAS90 and then stop the Service or App Server and run as 90.

@LouisAraiza Thats a great idea. I forget, how do you create that link?

M:\best\MAS 200\Version4\MAS90\Home\pvxwin32.exe"" -hd ../launcher/sota.ini ../SOA/Startup.m4p

Just change the first part to their path

@LouisAraiza Thanks. I don't have 4.x up in front of me, but could you theoretically create a group called 'non-accounting' and put all people not involved in the closing process in the group. Then disable that group somehow so that all those users would temporarily lose rights?

Don't think so. You could go in and lock out the individual users, but I don't see it as a group setting.

Mark, I kill tasks in task manager if I have easy access to the server since it is usually faster. Otherwise I kill them from the Master Console. The key to killing them at the server is to add the process ID to the columns displayed in Task Manager on the server. Open Task Manager and click on the Processes tab then click on View, Select Columns.

If it's MAS 90 you can only kill your own workstation's task because the pvxwin32.exe process is running at the client. If running thru TS/Citrix presumably you can kill. If it's MAS 200 Kill Tasks button will light up in M/C and kill the task so long as: 1) You're on version 4.05+ 2) Role Maint / Sec Events / check ""Allow Users to Terminate Tasks ... "" 3) The task being attempted to kill is not launched as a stand-alone ""mas90 type"" process. Ex 1: S/O Entry task launched from SLX Ex 2: V/I Import Job run through a shortcut / bat file / script Although Master Console will have a record of those mas90 style tasks it cannot actually manage those. 4) @BertoWud in 4.10, the combination of running as a service + No Spawn Task prevented killing of tasks. This was a bug I wrote up and it got fixed at some later point. The bug part was with the service. Also on 4.10, Spawn Task did make a screen load (task off the Launcher) appear slower but App Server is much better since.

Mark: could always just get the accounting people in and then create an instlock.txt file. Or even create a quick batch file to do it for you. Not perfect but it would work.

Sage 100 Adv v2013 (running as an Application) - We seem to be unable to kill hung tasks via Master Console (which prevents them from performing certain tasks). Is this a known issue? I wonder if running it as a Service would help. Our workaround: 1. Make sure no one isn't really in anything (i.e., non-Launcher). 2. Remote into the server. 3. Close the Appl Serv. 4. Kill all pvxwin32.exe's via Task Mgr. 5. Re-launch the Appl Serv. 6. Check Master Console.

Per @GeneUlrich's above post (which is a neat trick): Rather than just killing all Sage 100 sessions, you can just kill the ""hung"" session(s) by doing the following: 1. Log into the server and launch Windows Task Mgr. 2. On the Processes tab/screen > View menu, select ""Select Columns"", and select PID (Process Identifier). 3. Obtain the PID of the hung session(s) from Master Console (far right column), and kill that Process in Task Mgr.