Sage 100

We have two customers, one on Sage 100 Premium V2016 and one on Sage 100 Advanced V2017, who regularly have hung pvxwin32.exe tasks at the end of the day. I'm talking about multiple dozens of hung tasks, every day. I don't know if the third party apps are effecting either customer, but it's something to consider. One customer is on-prem, using ISM's Ship Link, Visual Cut and Century Business Systems CC processing. The second is hosted in the cloud with Citrix, using Starship, Century Business CC processing, and Certipro's web with Mapadoc. We have a third customer using Century CC without any hung task issues. I know I can run a batch file to kill the tasks before the start of each day, but if possible, I'd like to fix it at the root.

Is my memory false or could one explanation be invalid printer throwing an error behind the scenes that never reaches a user desktop but may hang the process? I thought there was a conversation about that before and Alnoor gave some explanation. Of course, I could be thinking of something entirely different so this is more an FWIW than a solid reply to hang your hat on.

Can't you identify who is hanging by using the PID in the master console and to see who is running the PVX job via the server task manager? Might start you in the right direction.

Scripted pop-ups that are triggered by automated processes can cause this. Add filters to any scripts to limit them to when there is a UI (or down to a specific UI).

@WayneSchulz , I have seen something similar with invalid printers before. I'll ask our tech group if they can help. @JeffSchwenk , there is no PID entry in the master console that matches, which it what makes it so much harder! (Great thought, though. That's where my brain went to first.) @KevinMoyes , I'll contact the third parties (not sure if the issue is caused by them) to see if they know of anything similar happening to their other customers. If I find a resolution other than my bat file, I'll post it here, in case someone else does a search for the same issue. This is what I'm using for one customer, run about 1/2 hour before the first person gets to the office: echo off net stop ""Sage 100 Advanced 2017 (9540)"" taskkill /IM pvxwin32.exe /F Net start ""Sage 100 Advanced 2017 (9540)"" exit Thanks, everyone!

I was thinking more about UDS / Custom Office scripts (vs. enhancements). retVal = oSession.AsObject(oSession.UI).MessageBox(""..."") This type of pop-up will wait forever, since there is no UI to respond.

Roberta I was just remoted in with a client where I saw a bunch of stranded pvxwin32.exe tasks. I identified these as auto-run V/I jobs that didn't complete (no doubt because they ran into an error). Either there are chained jobs that started to run before it completed or another job entirely started to run for the same data files. That problem can be solved but in Task Manager this is is how I identified it: On the Details tab (or Processes tab depending on server o/s), sort by Image Name. Then rt-click one of the columns, choose Select Columns, add Command Line property. Now you will see full path to pvxwin32.exe and its arguments / parameters. V/I auto-run jobs have this pattern: ""d:\apps\mas90\home\pvxwin32.exe"" ../launcher/sota.ini ..\SOA\SY_StartupLegacy.m4p -DR=../home -ARG xxxx yyyy 0 CompanyCode AUTO Basically the 3-digit company code and AUTO at the end give it away it's V/I. So does ""SY_StartupLegacy.m4p"". Hope that helps.

If the pvxwin32.exe processes can be found, Alnoor's suggestion about looking at the Command Line property in Task Scheduler is a big help. (The way to add the column is different in other versions of Windows... it might be in the View menu within Task Scheduler).

Roberta - Very cool with the _taskkill /IM pvxwin32.exe /F_ ! Suggest you add a _TIMEOUT /T 15_ to it before the NET START (to force a wait of 15 seconds in case system is busy with the NET STOP or TASKKILL). Another way, just to put it out there is use Windows PowerShell scripts. It interacts directly with the o/s. Typically have one that kills all pvxwin32.exe's then another than runs later that starts up App Server and CS ODBC.

Do they have any Task Scheduler jobs set up? We have seen this before in Advanced. https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=75776&sliceId=1&cmd=¤tmsID=MS_Customer&docLink=true&isDocLink=true&languageId=&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl