Sage 100

 View Only
Expand all | Collapse all

Clearing "Ghost" Users

  • 1.  Clearing "Ghost" Users

    Posted 04-04-2019 11:35
    Sage 100 Advanced v2015.  The  Sage 100 Master Console shows 13 users yet all of the user licenses are taken.  They have 17 user licenses.  re-booting the server resolves the issue.  Is there another method of freeing up the "ghost" user licenses, other than re-starting the server?  Can I selectively, by user, kill the pvxwin32.exe tasks?

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------


  • 2.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 12:09
    ​I've always found that rebooting the server was the most efficient method to clear those ghost tasks.  If you know the PID of the Sage Service, and the PID of the users in Master Console, I think you can manually kill those extra pvxwin32.exe tasks in Task Manager; but my experience is inconsistent with those results; so i normally just have them reboot the server. 

    It's always best to try and figure out what is causing the "ghost" session, although often elusive.

    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------



  • 3.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 12:38


    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 4.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 12:54
    It seems its never convenient to reboot, so I go into server management and look for files (in the MAS90 directory) that are locked by users who aren't actually active at the time, and I release them. P.S. Bustin makes me feel good.

    ------------------------------
    ==================
    Rhonda McNamara
    Customer Success Manager
    Stewart Technologies, Inc.
    rsm@stewarttechnologies.com
    ------------------------------



  • 5.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 13:10
    @Rhonda McNamara  They are on Server 2008.  Looking at open Files in Computer, Manage, all of the paths have "Administrator" as the owner except for the shares open by the local workstation.  I believe this is because adavnced and premium are server side processing.  So, I don't know how to distinguish those programs open by computer or Windows user logon. ​

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 6.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 17:19
    With Advanced you have the advantage that the PID listed in Master Console is the PID in the server's Task Manager.  Open files (Computer Management) lets you know if anyone has any MAS90 mode connections which might be locking things up.
    Adding Command Line to Task Manager can also help.  (The service should be easier to find).


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 7.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 21:56
    Edited by Alnoor Cassim 04-04-2019 21:57
    Exactly what @Kevin Moyes said on both points. Let me add V/I jobs run as BAT files or command line shortcuts via Windows Task Scheduler are common culprits especially when 2 V/I jobs run in the same BAT file (e.g. Job 1 for PO ROG, Job 2 to distribute S/N) but do not have a "TIMEOUT /T nnn" command in between to force a delay.

    Also V/I autorun export jobs that take a long time to complete and end up with a hanging pvxwin32.exe because the Sage user ID for the V/I job has Auto Logoff set and the 20 minutes have expired.

    But let me add a twist. ​

    If the specific program running with Mas90 style connection is not directly run from server, then it will NOT appear in the server's Task Mgr but still appears in the Master Console (M/C) and keeps a license. In this case the M/C PID corresponds to the wkstn. 

    E.g. A BOI app/script takes up a license but if not shut down properly retains it and pvxcom.exe will still be running. Starship BOI version comes to mind. In M/C, the User = "Starship" but the Station = the shipping PC in the whse. You can't kill that task with M/C. Why? Because it's running Mas90 style from the Shipping PC. You have to close Starship app from there or kill pvxcom.exe from there to release the license. But dude has gone for home the day already.

    ------------------------------
    Alnoor Cassim

    Free Agent Developer and Consultant
    CallForHelp.biz
    Email: alnoor@callforhelp.biz
    Orange County, CA
    ------------------------------



  • 8.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 22:17
    Thanks Alnoor.  Those examples give me some ideas of where to start sniffing around.

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 9.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 22:15
    How can I tell which pvxwin32.exe is associated with the service by looking at the command line reference in task manager?

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 10.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 22:31
    Edited by Alnoor Cassim 04-04-2019 22:31
    Doug that is hard to answer w/o a picture. Referencing Kevin's image, first of all, in Task Mgr on the Command Line column, if you see "ABC AUTO" at the end that means it's a V/I autorun import (or export). Otherwise, it's kind of hard to tell but you can cross-reference with the App Server Config. In there if you click on Session tab you can actually add columns there by rt-clicking on an existing column. If you add the  "Application Command Line Arguments" (I believe that's correct but I'm going by memory) you can match one of the arguments (it's a long number) in this column against the Task Mgr Command Line column. Hope that helps.

    ------------------------------
    Alnoor Cassim

    Free Agent Developer and Consultant
    CallForHelp.biz
    Email: alnoor@callforhelp.biz
    Orange County, CA
    ------------------------------



  • 11.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 23:00
    Thanks Alnoor.  That helps and I will check it out tomorrow.  I want to make sure I don't inadvertantly stop the host service.

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 12.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 23:15
    That service is easy to identify it looks like this (has the -s in it): 



    ------------------------------
    Alnoor Cassim

    Free Agent Developer and Consultant
    CallForHelp.biz
    Email: alnoor@callforhelp.biz
    Orange County, CA
    ------------------------------



  • 13.  RE: Clearing "Ghost" Users

    Posted 04-04-2019 23:38
    Got it.  Thanks!

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 14.  RE: Clearing "Ghost" Users

    Posted 04-05-2019 00:43
    So if we are talking about Orphaned Tasks I have a powershell script that will kill those. It looks at the install path for sage from the registry and looks at all processes with the same path. Then it looks at the parent ID for each one and checks to see if it gets an error looking for the parent. If it does, it sees it as an orphaned task and kills the task.
    -Todd

    ------Original Message------

    Got it.  Thanks!

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------


  • 15.  RE: Clearing "Ghost" Users

    Posted 04-05-2019 08:39
    That's really cool, I never thought about looking at the processes Parent ID.  I've always figured (when I eventually get around to writing that) I would check SY_Console against the server's active pvxwin32s.

    ------------------------------
    Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
    ------------------------------



  • 16.  RE: Clearing "Ghost" Users

    Posted 04-05-2019 13:41
    @Todd Martin  That's a great utility.  You should sell it to Sage!  I don't believe this customer is experiencing this issue frequently enough to justify the expense of a custom solution, but I will keep in mind that you have an option.  Thanks for posting. ​

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------