Sage 100

Sage Task Scheduler - v2017 Adv - I am a newbie in this environment. Client wants to rebuild the new search index on a nightly basis. So I set up the Sage Task Scheduler. Now it appears that it is ACTIVE all the time. See below. Is it supposed to be? The schedule for running is set for 11:50 PM. Client is having a hissy because they are tight on user licenses. Can't blame them. This method will not work if a user license is in use all the time. Help!!!

Do they have inventory installed and activated? I ran into this and activating inventory resolved it. Also, is the default printer on the computer you scheduled it on a valid printer?

Hmmm. Valid printer. Will look at this. My RDP session does not have a valid printer. Could I use the deferred? Or a fax? I get a warning when I run a print but I ignore it as I always just preview,

Nope - it needs a valid printer. There's an enhancement request submitted. Search for this and vote please. Allow prining Task Scheduler Log to Deferred printer

Just changed the default printer to a valid one. Will a report actually print now? If so, what is the purpose of the log report?

I think the purpose is supposed to be to prove that it ran. Really it's useless.

Haha. I know it sounded familiar. That was my original request more than a year ago. https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/12636

Well, we are up to 20 votes. Another 80 or so and we might get their attention.....

Seems to work with a good printer defined. Though it appears that the log file is purged when the paper prints. I assume it is the activity log. Need to check

I ran into Task Scheduler issues today, and found that a local print queue is required. A mapped print object was not enough (the task left threads running in Master Console). These things should not be so finicky!

Problems hanging again! @KevinMoyes issue with threads running in master console. How do you kill the task? From the master console, nothing happens. Task manager?? - Update. Go into task manager, click on view to display the PID column. Once on, you can match up the rogue hanging task PID with the task manager PID and terminate the process.

(I assume your update indicates you properly killed the extra tasks). Recent headaches indicate the default printer / print queue used for the task log must be a local queue (not mapped to a print server).

Yep, tasks are history. Frustrating that they won't die from the system console.