Sage 100

Anyone have any insite on Sage Task Scheduler running VI jobs on 100 Advanced? Have them setup and clicking Run Now - it just clears the screen. Log says No Data. Checking the job in VI shows last time it ran was 12/18 (manually). There's stuff on Sage re a printer being available (Microsoft XPS is available - does it have to be a ""real"" printer?) and the users (am fighting with IT over that). What is the MOST IMPORTANT thing to make them run in Adv? (Or should I just go the batch file route?)

I create a user called Task Scheduler (this way if a real user's sign on is deleted, your tasks will still work). Be sure this Task Scheduler user has all the needed rights. I sign onto the server as administrator and set up the task from there. Be sure there is a printer set up on the server. I instruct the users that if they need to modify the task, go into the server as administrator. It's been awhile since setting this up, but I have had some success, after pulling my hair out.

Well, damn, that's pretty much what we did. ARGH.

Set up a bogus default printer to LPT1 or a COM port. ?Task Scheduler log will display an error in the print queue, but pvxwin32.exe will close and not hang. If you go the batch route, there is a KB article that covers the steps for advanced, attached.

I may just go the batch route for now - I've never worked with IT here before and batching is probably going to get me there quicker. Thanks! @MoiraGoggin

You do have to have a real printer, because XPS will require a file name to create which causes an error. I ask IT for a IP networked printer that the user Task Scheduler will have access to.

On the server, I just set up a printer with a port pointing to a path such as ""C:\Sage\TaskSchedulerPrinter.txt"". Give it the ""Generic/Text"" driver. Make sure the user that the task will be running under has modify rights to the above path. After setting up the task via sage 100, use the windows task scheduler to test it.

Related thread on Task Scheduler: https://90minds-com.socialcast.com/messages/39286273

Setup batches with all the attendant ADV BS, and it appears to work. At least I passed it off to IT for them to add to the Windows Scheduler and it worked for me MANUALLY. Fingers crossed!

For VI we use batch files... and only use the Sage Task Scheduler option for things that cannot be done any other way (running Aging report, auto-post...).