TaskScheduler does not run a scheduled Job Queue Entry

Hi All,

Really stuck with this so hoping someone has a solution.

Problem: The TaskScheduler does not run a scheduled Job Queue Entry with a ‘User ID’ other than the Service Domain Account. It changes the Job Queue Entry ‘Scheduled’ column to ‘No’(in Red) from ‘Yes’ and does not create a Job Queue Log Entry. You have to view the Event Viewer log to see the cause of the error (Event Viewer → Applications and Service Logs’ → Microsoft → DynamicsNAV → Common → Admin).

Error Detail:
Server instance: NAVServices
Category: TaskScheduling
ClientSessionId: {00000000-0000-0000-0000-000000000000}
ClientActivityId: {00000000-0000-0000-0000-000000000000}
ServerSessionUniqueId: {00000000-0000-0000-0000-000000000000}
ServerActivityId: {00000000-0000-0000-0000-000000000000}
EventTime: ‎2018‎-‎04‎-‎18T11:05:00.828986100Z
Message (COMException): The specified directory service attribute or value does not exist.

System Information: NAV GB 2018.CU3 NAV Server is running with Domain Account We followed all steps to provision the domain account. (here) Windows Server 2012 R2 There are multiple domains on the network
Observations:
Logging into NAV as the Domain Service account user and resetting the Job Queue Entry will set the ‘User ID’ on the Job Queue entry as the logged in User. The TaskScheduler will run the scheduled job without failure thereafter. If you then log in as a user (domain) and reset, the job fails again. My best guesses here are: Issue lies with Domain Service account setup Issue lies with Domain Service account impersonating the ‘User ID’ on the job queue task. Issue lies in the Domain itself or perhaps having multiple domains Issue is a NAV service issue requiring a Cumulative Update, see this article. We were on NAV2017.GB.CU10 and had the same issue, so thought upgrading to NAV2018 might help.
https://docs.microsoft.com/en-us/dynamics-nav/provisioning-the-microsoft-dynamics-nav-server-account#DUA

Update: We noted that in Cronus on the same app server we managed to get the Job Queue to run. But the moment we added one user (by default has to be a SUPER) to the Cronus database company the Job Queue stopped working.

Hi Mike,

Does the service account that you are using read permissions to your OU in AD?

This seems to be an AD problem. Do you run Dynamics NAV Server with local account? If you run it with local account, try to change to domain account.

Hi Erik.

Yes we tried that without success though. Thanks for the input.

And is your service account a local or domain account, as [mention:ba4af57369b949f2973760bde9ffb9a0:e9ed411860ed4f2ba0265705b8793d05] asked?