Sage 100

Are there any alternatives to the Task Scheduler? Version 2015 Advanced but I have tested on 2016 and 2017 . It simply does not work. It only works if you click on ""Run Now"" and even then it's iffy. If there are no transactions to post in any of the modules the whole thing stops. Client wants to automatically update SO Invoicing, PO Receipts and Returns and GL entries every night. I have done everything including calling Sage. Task Manager on server says it started and completed successfully. TIA

I usually end up using BOI scripts assigned to Deferred or a specific PDF printer. It sucks since I really want to use Paperless Office...

Oh, and triggered by Windows Task Scheduler.

What does the log in Sage 100 say? Had a hellish experience with this on 2016, but finally got it working to auto update JE's, and generate paperless registers. Ensure you're on latest SP for 2016, as early SP's had a bug where it wouldn't generate paperless docs.

As I recall, when you run the Sage 100 Task Scheduler it writes the task to the Windows Scheduler. From the Windows Scheduler you can then control the job setting up the options you need. After that delete the job out of Sage scheduler.

@MarkKotyla The log just says that the task completed. One of the lines on the log says 'Invalid printer selected"". The printer is valid. We also have Paperless setup. When I click on Run Now ii saves to Paperless with no issues. Customer is on 2015 but I tested on my PC with the latest SP's on 2016 and 2017 and it still did not work. @MoiraGoggin How will the Windows Scheduler know which modules to update, which printer to send it to etc. Does Sage put out a file that is saved somewhere?

Is it a network printer? If so, the account that's running the scheduled task may not 'see' that printer. I would try using the users credentials to run the task, or try installing the printer on the Sage server as a local printer.

@SteveIwanowski yes, the printer is a network printer. I'll try installing a local printer, if that's what you mean. I am using the network Administrator credentials for server login and full access to Sage menus

Since all output is going to Paperless, I created a local HP LaserJet 4, named it Going nowhere, and used that as printer in Task Scheduler.

That has happened to me a few times where Task Scheduler manually worked only. Preview the Task Scheduler Listing. Do you get an error similar to this: ""Invalid selection table for column $"" ? If so, search SocialCast for that error. I posted about it a few years ago. It has to do with BIE keys in Sy_ReportSelection

@MarkKotyla I created a ""fake"" local printer pointed at LPT1. The task still does not run automatically. As a test, I opened Master Console just before the scheduled start time and waited. i could see that the Task started and the user is getting logged on to Sage100 but the task closed after 30 seconds and nothing got updated. I don't know why the task will not start updating once it's logged on. @AlnoorCassim, the only error I get in the log Is invalid printer selected. I tried Local printer, Network Printer, Deferred...nothing works. We are using paperless anyway so I'm not sure the printer matters. It all works fine when I manually click on Run Now.

If Deferred doesn't work, then something else is going on. What does Windows Task Scheduler History tab show? Does job run to completion or is there an error? Are you able to manually start the job from Windows Task Scheduler?

@MarkKotyla When it's on Deferred I can see the task start in Master Console but it freezes and never finishes. Had to Kill the task. Any other printer the task never even starts. In Windows Task Scheduler the task shows that it started and finished successfully but only ran for about 30 seconds. The task will not start manually from Windows Task Scheduler but will run from Sage if I click on Run Now. Sorry, I know it's all over the place but there is nothing that i can point to as being the root of the problem.

I'd try deleting the task in Sage 100 and creating a new one. Once established, ensure that it runs with highest privileges in Windows Task Manager. May have to play around with compatibility settings as well.