Sage 100

KSync batch file successfully runs a VI import job but leaves a stranded PVXCOM.exe process: I thought I saw something recently on here about stranded processes from batch files but I cannot seem to find it now. The orphaned process gets created regardless of whether I run it from Task Scheduler or KSync, so I'm guessing there's something else I need to do with the file itself and not the program. There's nothing to the batch file...it's the same we've all ever used: C: CD C:\SageSoftware\MAS_v2014\MAS90\Home pvxwin32.exe ..\launcher\sota.ini ..\soa\startup.m4p -ARG DIRECT UIOFF XXX XXX SPI VIWI1D AUTO Please let me know if there's a way to make sure this process closes itself upon completion of the import. Thanks in advance!

I assume this is a standard install based on the above?

Goid morning! No, this is an Advanced client. Is there something different I should have in the batch file for Advanced?

I usually follow this article for advanced... not sure if it really makes a difference in your particular issue, but worth a shot! https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=19387&sliceId=1&cmd=displayKC&dialogID=139287&docType=kc&isLoadPublishedVer=&stateId=139290&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Thanks, Michelle. I saw that but didn't have a chance yet to try...got people being hit with viruses right and left.

Hey @AmberPrayfrock did you resolve this? I have a premium client complaining about the same thing.

I did implement the steps that included creating the new server in the Application Configuration for my Advanced client. I could not get the updated batch file to run through KSync afterwards though, only through Windows Task Scheduler.