Sage 100

We are trying to automate a VI job from a workstation. The third party programmer for this only has access to the workstation, not to the server. He writes a file, then immediately kicks off the VI job batch (cannot user the task scheduler), which is supposed to import his file. I've spoken with our programmers and with Sage. I've gone thru Sage KB articles. In this example, we are importing to Job Cost, older files layout. Customer is on 2016, Advanced. Here is his VI job batch: @echo off C: cd ""C:\Sage\Sage100Workstationv2016\MAS90\Home"" ""C:\Sage\Sage100Workstationv2016\MAS90\Home\PVXWIN32.EXE"" -HD ../launcher/sota.ini *client -ARG ""server1"" ""9530"" ""VIWI0X""-ARG= DIRECT UION web web123 BBB VIWI0X AUTO exit If I enter the ""VI"" job name ""VIWI0X"" or the ""in English"" name ""JC_Master"" or ""SAGE"" (that is the application server name) directly after the port , I get an message: WindX Client Connection. Acess to Application [whatever is entered there] is denied. If after the port 9530, I enter ""MAS 200"" it kicks off Sage, and asks for a sign in. Thanks, Roberta

Did you follow the KB article about setting up the service? It is done differently for Advanced.

AppName is the name of what you add to the service. (VIJobs in my example above).

Also, you have already changed to the home directory so you don't need ""C:\Sage\Sage100Workstationv2016\MAS90\Home\PVXWIN32.EXE"". Just start the line with PVXWIN32.EXE.

In Kevin's example you replace the ""VIWI0X"" after the ""9530"" with ""VIJOBS"".

@DougHiggs and @KevinMoyes , This information is great. Thanks so much.

Great Info. This is very cool!!