Sage 100

Need some help. Working with Sage 100 Adv v2016 and Windows Server 2012 R2. I have two VI export jobs that are scheduled to run in Windows Task Scheduler. In the history tab of Task scheduler is shows the jobs have completed. When I look to see if the data is in the folder, nothing is there. If I go back into Sage and review the job status of the job it shows ""not running"" but if I look inside master console the job name shows it still running. If I manually run the jobs inside Sage, they both take less than 3 mins to complete. Any suggestions on what I need to troubleshoot next with Windows Task Scheduler? TIA

While logged in, I would manually run the Task Scheduler to see if it actually happens. Also make sure the Task is configured to run without being logged in.

Create a batch file with the VI commands (tuned to not require a UI). Make sure it runs, then schedule it. Or better yet, don't use VI for exports... use Visual Cut instead.

I did try to create a batch file with the VI commands and it still doesn't produce any data results @KevinMoyes . I also ran it manually in TS and changed the option to run without being logged in and it completes the task with no data results @SteveIwanowski . @KevinMoyes I'm not familiar with Visual Cut does it work similar to task scheduler? Any other ideas....I normally have better luck with task scheduler running the jobs. The user account is part of the admin group.

Visual Cut webinar: https://www.dropbox.com/s/rurv82aoz8tnc3e/90%20Minds%20Visual%20CUT%20Webinar.mp4?dl=0

It could be a few things: I'd try running the batch file step by step through a command line, changing the AUTO to MANUAL to see if you even get the right V/I job to trigger. If that works, then see if you are trying to save the files to a mapped drive that the Task Scheduler account may or may not have access to. Maybe try a UNC path instead of a mapped drive letter. VisualCut is very awesome and a great value, but then you need to generate a Crystal Report to extract the data. I do these things in PowerShell nowadays, so maybe I need to create a simple script to share....

When I run the batch file manually and change the script to run as manual the job completes. When I run the batch file and change the script to run as AUTO it does not complete the job. I switched the jobs to run on the terminal server bc I thought the third party processing running on the main server could be causing the job not to complete. Do I need to add additional command line in my script? Attached a sample of the script. Could it be mapped to the wrong pvxwin32.exe location? TIA

Is the log file being created after the task is being completed? Since this is advanced and running as a service, I assume, logon to windows with that Account. While logged in with that account setup up a default printer. A real one not a PDF printer. If the Task Scheduler cannot print that to a printer or gets prompted for where to save the log file the job will not finish and will stay stuck in running mode

I will give that a try @CarmenCruz

Sage KB located with Sage 100 search: ""visual integrator"" + ""short cut"" gives a long doc on this. Title: ""How to create a short-cut or Windows batch file to run a Visual Integrator import job, export job, or other Sage 100 ERP task outside the program

I'd check how you configured the service...

I have re checked several settings and put the VI job and script on a workstation and it works running as manual or auto. Went back to the customers environment on the terminal server set it back up. If I manually run the bat file it completes the task on the server. When I edit the script to run switch it to AUTO it doesn't complete (it hangs and doesn't close out the cmd window). I'm logged in as Admin on the server, anti-virus is turned off, UAC is turned off and right clicked to run the bat as admin and still doesn't complete. IT person hasn't provided much help with troubleshooting. I'm thinking it's something environmental on the server that is causing the process not to complete but I'm out of ideas.

I think the VI job has to be added to the Apps tab of the Application Server Configuration before it will run via a batch job in Windows Task Scheduler. The attached may help.

I have added these steps and it still stalls

When you run the batch file in a command window (CMD), be sure to login as the user set in Task Scheduler that you said was in the admin group. Don't just run it in the Run field. You'll need to see any responses to the batch command.

Your start-in directory has a space... usually that requires the path to be wrapped in double-quotes.

The issue with the bat files hanging up (not running inside of task scheduler) was related to the cycle settings inside the VI jobs that I had setup at one time and decided not to use any longer. Thank you @AlnoorCassim for your help troubleshooting the issue. I really appreciate it!