Sage 100

I have a customer on Sage Advanced 2015. We would like to create a batch file to run a VI export job nightly. According to the attached article, we have to use the Application Server to run the batch file. Is that true?

Yes and No? I have used Task Scheduler to run a basic batch file. The problem you run into there is the pvxwin32 session gets stranded and uses a license, and after so many days, all the licenses are used up and no one can log in. So the work around is to create a batch file to kill any open pvx tasks shortly after the VI Job is done, mine is set for 1 hour after the VI Job (also.. using it as a service so as not to kill the actual application server). I have not ever been able to get the application server instructions you attached to run a batch to work reliably, but I haven't put too much effort into it either.

Those steps have worked for Advanced for me. I've had some stuck sessions like @MichelleForsey mentioned, but it's been very rare.

I've never used the Sage 100 Appl Serv for this. I've always just created a .bat file and then used Windows Task Scheduler. If however you can upgrade them, you can leverage the Sage 100 Task Scheduler in L/M to schedule VI Jobs - although I haven't had the opp to use it myself as of yet.

@BrettZimmerman, did the batch file look like the examples in the document? I keep getting an Error 12, File in use error.

For Advanced / Premium, we set up the service to have an import program (as in the KB instructions), and use that for scheduled import batch files (instead of doing the imports MAS90 style, without referencing the port #...). Windows Task Scheduler to run the batch files... usually including a check for a missing input file first (because that will lock up the job).

@MichelleForsey I've used the Task Scheduler method and then set the job to stop automatically after a specific amount of time, like 1-2 hours, depending on the job. Wouldn't that 'kill' the process and release the user license?

or you can write the batch file to ship the import if the source file does not exist.

Re: your error 12, do you maybe need quotes ("" "") around any pathing that has spaces? Although in some cases the quotes shouldn't be used, as is evident below. Here's a sample .bat I last used for a VI Export: d: cd \ cd D:\Sage\Sage 100 Advanced ERP\MAS90\home pvxwin32.exe ..\launcher\sota.ini ..\soa\startup.M4P -ARG DIRECT UIOFF user password Z99 viwx07 AUTO And prior to that I believe I did not use an actual .bat file. I'm pretty sure I just did it all within Windows Task Scheduler, but that might have been due to the nature of the task we needed to perform - e.g.: Program/script: ""E:\ERP\Sage\Sage 100 Advanced ERP\MAS90\home\pvxwin32.exe"" Arguments: -hd../launcher/sota.ini ""E:\ERP\Sage\Sage 100 Advanced ERP\MAS90\FX\FX_GetCurrencyRates.M4P"" Start in directory: ""E:\ERP\Sage\Sage 100 Advanced ERP\MAS90\home"" -Due to ""directory name is invalid"" error when trying to run the job (http://matthewcevans.com/blog/2010/08/11/windows-task-scheduler-the-directory-name-is-invalid-0x8007010b/), had to set as E:\ERP\Sage\Sage 100 Advanced ERP\MAS90\home\

I was wondering if the error 12 was due to missing the server info in the batch file and maybe it should look like this: C: ? CD ""C:\Sage\MAS 200 Client\Version4\MAS90\HOME"" ? ""C:\Sage\MAS 200 Client\Version4\MAS90\HOME\pvxwin32.EXE"" -hd ../launcher/sota.ini *Client -ARG ""Server Name"" ""Port"" ""App Name""-ARG= DIRECT UION John Doe ABC VIWI00 AUTO But your batch file works and it doesn't have the server name or port info. Tried both with quotes and without. I may have this backwards, but with quotes opens a box that looks like it is going to launch Sage and then doesn't and without quotes gives the error 12. I will use your sample.bat and see what happens.

Note: we only use VI for imports. Visual Cut is much more reliable for querying and formatting export data on a schedule.

@MoiraGoggin I've not tried that, I will on my next one and see! Good Idea!

Success! Thanks everyone.

What was the secret to your success????

I followed Brett's example to the letter. I think I had an extra carriage return in my original file and that threw the error 12.