Skip to main content

What do you do when your NAV 2017 Job is not triggering through Job Queue Entries

Introduction:
Working with failed Scheduled Jobs can be a tiresome process. This is exactly the case where one of my client has an Invoicing & Payment Jobs which run once a day and Job Queue Entries fail to trigger these Jobs. No Errors in the Logs, No Execution Entry, Simply No Way of Figuring it out as to why Job didn't trigger.
Contacting Microsoft Support, they are asking to simply Upgrade the Application to latest version.
Which is not a preferred option as the database size is around 200GB.
Let's see how to resolve this in a smarter way.

Pre-requisites:
Microsoft Windows Task Scheduler
Microsoft Windows Powershell
Microsoft Dynamics NAV(Administration Module for PowerShell & Development Environment)

Books & References:
https://docs.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.management/?view=businesscentral-ps

Demonstration:
1. Building Objects to Run through a Codeunit:
As you know that Job Queue Entries support Reports and Codeunits and NAV Administration Module only supports Codeunit. So, inorder to make it work, create a Codeunit to execute all the Reports and Codeunits.

2. Creation of PowerShell Script:
This PowerShell Script execute with the help of NAV Administration to Run the Codeunit. Prior to running the Script you need to set the Execution Policy.

Syntax:
Invoke-NAVCodeunit <Codeunit No.> - ServerIntance <ServerInstanceName> -CompanyName  <Company Name> -Force



3. Setting Up Task Scheduler Triggers:
By Setting up the Triggers, you can decide recurrence to execute the Codeunit. It can be Hours, Daily, Weekly, Monthly, One-Time or Infinite. You can also set the time for precise execution.


4. Setting Up Task Scheduler Commands:
Whenever we execute the PowerShell Script through CMD, we run the commands as follows.
Command: PowerShell.exe <PS Script File Path>
Here, we pass the PowerShell.exe into the script and PS Script File Path as Parameter.


Conclusion:
Thus, using NAV Administration Module, PowerShell and Task Scheduler I was about to replicate Job Queue Entries functionality.
Although, this works perfectly for NAV and Business Central - On Premise, it work for Business Central on SaaS. In my upcoming blog I'll also show we can acheive this.

Hope you guys find this blog useful 😇


Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe