Sage 100

Client Running on 2018 PU1. The Windows Schedular for their VI Jobs that run at night leaves processes running on the server, which uses their Sage licenses. They have been having to reboot the server several times a week to clear those stranded processes to have all 11 of their licenses available for them to use. We've logged Sage cases to no avail. (And yes, we did try the Sage Task Scheduler but there was an issue there). Any suggestions how to clear those stranded processes and free up their licenses without having to continually reboot their server?

Standard, Advanced or Premium??

If Standard: You must logon as Windows user defined for Windows Account in Task Scheduler and setup a real default printer. You can not default to a PDF printer as that requires a location as to where to save that Sage can't get an answer to. The log that is printed at the end of each job run is hanging. If this is Advanced or Premium and the program runs as a service then you will do the same process but Logon as the User account that is starting the Sage 100 ADV, Premium service on the Server.

We ended up writing a batch file that ran at night to shut down open pvxwin32 processes. Sent from my cell phone. Please forgive any misspellings.

that would work too :)

@CarmenCruz It is so nice to have you here! That has been plaguing me forever! Good to know!

What @Carmenator said! I've worked around it these ways: 1) Cooper's way which can also done via PowerShell scripts 2) By pointing it to a real printer which was actually a fake local printer I added that was set to ""Use Printer Offline"" so it would collect in the print spooler queue. 3) Choosing Deferred and then worrying later how to delete thousands of Deferred Print jobs. 4) If instead of V/I, it's a journal/register, if Paperless is configured for it then by pointing the task to a regular printer. Just like regular Paperless, it will PDF to Paperless instead and not pop up any Paperless prompts (like ""Do you want to print additional xxx to PDF?"")

Thanks Everyone! And now we have a new nickname for Carmen thanks to @Alnoor.Cassim!

Actually Sue she's had that name for a while now. It's very befitting. I'm sure she'll be happy to share the backstory in San Diego.