Answered

JOBS not running in JOB QUEUE ENTRIES

(0) Share

Report

Posted on by mbr

5,136

Hello Experts, we have had incidents were the jobs in the job queue entries DO NOT RUN even though the next start date says current date. This usually happens when we have to restart the SQL Services due to some server problems. Is there anything I need to do to watch out for in case we have to do a reboot of our sql server?

Problem: a job is set up to run every day at 4 pm. The server runs into problems which requires us to reboot. Then the system comes back and I check the job queue entries for that job it still looks like it's okay and is set to run today at 4 pm. The following day, I would check and the job did not run. It would only increment the date to the ff day but the job did not run the day before. The only way for the job to be reset is for me to stop and restart the job. has this happened to anyone? Any advice so I can plan for this the next time we run into system problems? It would be very tedious to stop and restart each job in NAV when we have to restart Nav but I will if this is the only solution.

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (1)

Suggested answer

Amol Salvi 18,698 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

Check the event viewer for the erroneous information.You will have more idea from event viewer

Was this reply helpful? Yes No
ManishS 86 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

Check if your SQL Agent is running after server restarts.

Was this reply helpful? Yes No
mbr 5,136 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

yes it is. The problem is in the NAV job queue entries. the job doesn't seem to run anymore and the date would just increment.

Was this reply helpful? Yes No
mbr 5,136 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

the event viewer only shows what happened to the server. NO nav related errors found in the event viewer. The reason for the restart of sql server can be for any number of reasons. The problem is Nav's jobs just don't seem to run as they should anymore after a force restart. I would have to stop and restart the job for the job to run continuously given the interval.

Was this reply helpful? Yes No
ManishS 86 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

What does the Job Queue Log Shows ?

Was this reply helpful? Yes No
Verified answer

Yogesh Kulkarni_ 1,762 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

Check what is mentioned in Job Queue Log Entry.

https://msdn.microsoft.com/en-us/library/hh879461(v=nav.90).aspx

Find if https://community.dynamics.com/nav/b/navalexchow/archive/2014/04/19/restarting-job-queue-when-it-hits-an-error-on-dynamics-nav-2013 is helpful.

-Yogesh Kulkarni
Please verify, if you find answer helpful.

Was this reply helpful? Yes No
mbr 5,136 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

I think I may just modify how the jobs are run as well. thank you Yogesh!

Was this reply helpful? Yes No
Suggested answer

Lorentz 75 on at

Like (1)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

Hi,

I have the same problem with NAV 2013 and NAV 2015...

After the restart the MSSQL server or instace, the Nas is always running but the jobs with status "Ready" are frozen.

I'm looking for the solution about this issue.

Lorenzo

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

I experienced the same issue in 2016. It seems that the only available options are to:

1. Restart the job, or

2. Change code unit 448 as described here:

community.dynamics.com/.../restarting-job-queue-when-it-hits-an-error-on-dynamics-nav-2013

This is a great article, but with slightly misleading title because jobs can stop due to any NAS interruption, including service restarts, and not necessarily from a job error.

As a result of NAS interruptions, job log will not show an error but the job will simply not have been run and therefore not appear in the log.

Bottom line, it seems prudent that someone needs to check the log daily and restart jobs that failed for whatever reason, especially in cases that can result in financial penalties (such as EDI chargebacks).

Was this reply helpful? Yes No
Pratama R 5 on at

Like (0)

Report

RE: JOBS not running in JOB QUEUE ENTRIES

My current solution for this issue , BC Version 19.X

1. Check service, SQL server agent

2. Enable Task scheduler (BC Administrator > Task Scheduler > Enable Task Scheduler)

3. Restart BC Administrator

4. Restart Job Queue

i hope this solution can resolve same issue (specially for BC 19.X)

thanks.

Was this reply helpful? Yes No