Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Justin Reed]

I have recently developed an issue with my Business Central Task Scheduler.

• I have an on prem instance of business central
• Version: NA Business Central 16.2 (Platform 16.0.14073.14195 + Application 16.2.13779.0)

We recently rebooted our app server that runs all the service tiers, and now my Task Scheduler is not running as expected. We run a separate service for our task scheduler.

Now, if I restart my task scheduler service, my reoccurring job queue tasks will all run once on their earliest start date/time, increment the date/time by the No. of Minutes between runs, but then never run again. I have no errors in my log entries. If i restart my Task scheduler service and restart the jobs in the job queue, they will run one time again but then “Freeze up” for lack of a better term.

The only warning (no errors) i have in event viewer has the Task Scheduler as its source and states “The Object Access Intent Override table is empty.” with a big stack trace.

I have tried creating new jobs to test it, create entries for the objects i am running in the Database Access Intent List within BC, changing the credential type from windows to NavUserPassword. So far no joy.

Any advice and/or ideas?

Thanks in advance!

/justin

——————————
Justin Reed
North America Fuel Systems Remanufacturing
——————————

[Jason Wilder]

I am on an earlier version than you but this should still apply to you:

It sounds like maybe your Scheduled Table is not being populated after the first try. There is a system table 2000000175 “Scheduled Task” that actually is what kicks off the actual job queue entry.  You might need a developer to expose this table for you but you can then get to the next level of why things are not re-running.  The Job Queue has a field called System Task ID which should match the ID field on the Scheduled task table.  If you do not find the ID in the Scheduled task table then you are a bit closer to figuring out what is going on.  Also curious if you hit the Restart button in the Job Queue Entries page if it creates the Scheduled Task and runs the job (guessing it will).

In regards to something happening after a reboot, did you accidentally change a setting in the service tier and now it is taking effect when you rebooted?  Double check your service tier settings to make sure nothing has changed.  Consider creating a new one just as a test to see if that works the same.

——————————
Jason Wilder
Senior Application Developer
Stonewall Kitchen
York ME
——————————
——————————————-