System Requirements for Microsoft Dynamics NAV 2017

10/13/2017 

Applies to: Microsoft Dynamics NAV 2017. See Microsoft Dynamics NAV 2018 version.

The following sections list the specifications of minimum hardware and software requirements to install and run Microsoft Dynamics NAV 2018. Minimum means that later versions (such as SP1, SP2, or R2 versions) of a required software product are also supported.

Client components

·         Microsoft Dynamics NAV Windows Client Requirements

·         Microsoft Dynamics NAV Development Environment Requirements

·         Microsoft Dynamics NAV Web Client Requirements

·         Microsoft Dynamics NAV Tablet Client and Phone Client (in a Browser) Requirements

·         Microsoft Dynamics NAV Universal App Requirements

Server components

·         Microsoft Dynamics NAV Server Requirements

·         Microsoft Dynamics NAV Web Server Components Requirements

·         Microsoft Dynamics NAV Database Components for SQL Server Requirements

·         Microsoft Dynamics NAV Help Server Requirements

Additional components and features

·         Microsoft Dynamics NAV as an App for SharePoint Requirements

·         Automated Data Capture System Requirements

·         Business Inbox in Microsoft Outlook Requirements

·         Microsoft Outlook Add-In Requirements

·         Microsoft Dynamics CRM Integration Requirements

·         Automated Deployment on Microsoft Azure Requirements

Note

Dynamics NAV Setup installs some software if it is not already present in the target computer. For more information, see the "Additional Information" section for each component.

1            Microsoft Dynamics NAV Windows Client Requirements

The following table shows the minimum system requirements for the Microsoft Dynamics NAV Windows client.

Supported operating systems	- Windows 10 Pro, Enterprise, or Education (32-bit and 64-bit editions). - Windows 8.1 Professional or Enterprise (32-bit and 64-bit editions). - Windows Server 2016 Standard, Essentials, or Datacenter. - Windows Server 2012 R2 Standard or Essentials (64-bit edition). - Windows Server 2012 Standard or Essentials (64-bit edition).
Hardware resources	- Hard disk space: 200 MB. - Memory: 1 GB.
Reports	- Microsoft Report Viewer 2015 to run reports that use RDLC report layouts. - SQL Server Report Builder 3.0 for Microsoft SQL Server 2014 or     Microsoft SQL Server 2012 SP1 to edit RDLC report layouts. - Microsoft Word 2013 or later to edit the layouts.
Instant messaging and Telephony API	- Microsoft Lync 2013 or Microsoft Lync 2010.
Outlook client integration and mail merge	- Microsoft Office 365, Microsoft Office 2016, Microsoft Office 2013 Service Pack 1 (SP1),    or Microsoft Office 2010 Service Pack 2 (SP2).
Import and export with Microsoft Excel and Office XML, and SharePoint links	- Microsoft Office 2016, Microsoft Office 2013 SP1, Microsoft Office 2010 SP2,    or Microsoft Office 365.
Editing in Excel using the Excel Add-in	Excel 2016, For more information, see Setting up the Excel Add-In for Editing Dynamics NAV Data.
OneNote integration	- Microsoft Office 2016, Microsoft Office 2013 SP1, or Microsoft Office 2010 SP2.
Email logging	- Active Directory and Microsoft Exchange Server 2010 or Microsoft Exchange Server 2013. - Microsoft Exchange Online, or Exchange Online as part of an Office 365 subscription.
Additional software	- Microsoft .NET Framework 4.5.2.
Additional information	·         Dynamics NAV Setup installs the following software if it is not already present        in the target computer:           o    Microsoft .NET Framework 4.5.2.           o    Microsoft Report Viewer2015. ·         The Microsoft Dynamics NAV Windows client is available in a 32-bit version and        64-bit version. On a 32-bit Windows operating system, the 32-bit version is run.         On a 64-bit Windows operating system, the 64-bit version is run by default;        however, you can also run the 32-bit version if it is required. ·         Dynamics NAV Setup can only install the Excel Add-in        if Excel is present on the target computer. ·         Outlook synchronization is not supported on 64-bit versions of Office. ·         Note: We’ve had reports that .NET framework 4.7 can cause the        Windows client environment to crash. In this case the solution is to uninstall .NET framework 4.7.

2            Microsoft Dynamics NAV Development Environment Requirements

The following table shows the minimum system requirements for the Microsoft Dynamics NAV Development Environment.

Supported operating systems	- Windows 10 Pro, Enterprise, or Education (32-bit and 64-bit editions). - Windows 8.1 Professional or Enterprise (32-bit and 64-bit editions). - Windows Server 2016 Standard, Essentials, or Datacenter. - Windows Server 2012 R2 Standard or Essentials (64-bit edition). - Windows Server 2012 Standard or Essentials (64-bit edition).
Hardware resources	- Hard disk space: 200 MB. - Memory: 1 GB.
Reports	·         Microsoft Report Viewer 2015 to run reports that use RDLC report layouts. ·         Microsoft Visual Studio or SQL Server Report Builder for creating and editing RDLC report layouts. The following versions and editions are supported: o    Microsoft Visual Studio 2015 Professional or Enterprise edition with SQL Server Data Tools installed. Important: Before you install Visual Studio, install Microsoft .NET Framework 4.6; otherwise, an error will occur when you compile or run RDLC reports. For more information, see Report error "Visual Basic Command Line Compiler has stopped working". o    Microsoft Visual Studio 2013 Professional, Premium, or Ultimate edition. o    Microsoft Visual Studio 2012 Professional, Premium, or Ultimate edition. o    SQL Server Report Builder 3.0 for Microsoft SQL Server 2014 or Microsoft SQL Server 2012 SP1. ·         SQL Server Report Builder 3.0 for Microsoft SQL Server 2014 or Microsoft SQL Server 2012 SP1 to upgrade reports. ·         Word 2013 or later to create Word report layouts.
Additional software	- Microsoft .NET Framework 4.5.2.
Additional information	·         Dynamics NAV Setup installs the following software if it is not already present in the target computer: o    Microsoft .NET Framework 4.5.2. o    SQL Server Native Client 11.0. o    Microsoft Report Viewer2015. o    SQL Server Report Builder 3.0 for Microsoft SQL Server 2014. This is not installed if a version of SQL Server Report Builder or Microsoft Visual Studio is already present on the target computer ·         If the development environment and Microsoft Dynamics NAV Server are on the same computer, then only a 64-bit operating system is supported. ·         Note: We’ve had reports that .NET framework 4.7 can cause the Windows client environment to crash. In this case the solution is to uninstall .NET framework 4.7.

3            Microsoft Dynamics NAV Web Client Requirements

The following table shows the minimum system requirements for the Dynamics NAV Web client.

Supported browsers	- Microsoft Edge. - Internet Explorer 11. - Google Chrome 53.0 for Windows. - Mozilla Firefox 49.0 for Windows. - Safari 9.0 and 10.0 on OSX. For a list of browser limitations, see Browser Limitations with the Microsoft Dynamics NAV Web Client.
Business inbox in Outlook	- Microsoft Office 365.
Sending data to Excel	- Microsoft Office 2016, Microsoft Office 2013 SP1, Microsoft Office 2010 SP2, or Microsoft Office 365.
Editing in Excel using the Excel Add-in	Excel 2016. For more information, see Setting up the Excel Add-In for Editing Dynamics NAV Data.
SharePoint Online links	- Microsoft Office 2016, Microsoft Office 2013 SP1, Microsoft Office 2010 SP2, or Microsoft Office 365.
Printing reports to Excel or Word	- Microsoft Office 2016, Microsoft Office 2013 SP1, Microsoft Office 2010 SP2, or Microsoft Office 365.
Additional information	- The browser must be able to install the Report Viewer ActiveX control to be able to print. - If you experience problems using the Microsoft Dynamics NAV Web client, you can try to turn off browser tools, such as translator tools that may run in the background.

4            Microsoft Dynamics NAV Tablet Client and Phone Client (in a Browser) Requirements

The following table shows the minimum system requirements for the Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client running in a browser when used for development and testing purposes.

Server component	Identical to the Dynamics NAV Web client.
Supported browsers	The following desktop browsers are supported: - Microsoft Edge - Internet Explorer 11 (build 11.0.9600.17239) for Windows 10 and for Windows 8.1 (32-bit and 64-bit versions). - Google Chrome 53.0 for Windows. - Mozilla Firefox 49.0 for Windows.

5            Microsoft Dynamics NAV Universal App Requirements

The following table shows the minimum system requirements for the Microsoft Dynamics NAV Universal App. For the latest information, see Dynamics NAV for Windows, Dynamics NAV for iPad and iPhone, and Dynamics NAV for Android tablet and Android phone.

Supported operating systems	- Windows 10 Home, Pro, Enterprise, or Education (32-bit and 64-bit editions). - Android 5.0 or higher (tablet and phone). - iOS 9.0 or higher (iPad and iPhone). - Windows Phone 8.1 or higher.
Additional hardware	- 1 GB RAM for Android and Windows.
Additional software	- A third-party telephony or VoIP app such as Skype or Lync is required for placing calls from Dynamics NAV. - A third-party email program such as Outlook is required for sending emails from Dynamics NAV. - Microsoft Office 2013 SP1 or Microsoft Office 365 is required for sending data to Microsoft Excel or to Microsoft Word.
Additional information	- Device diagonal screen size 7” for tablets. - Screen resolution 960 × 510 for tablets. - Device diagonal screen size 4” for phones. - Screen resolution 854 x 480 for phones.

6            Microsoft Dynamics NAV Server Requirements

The following table shows the minimum system requirements for Microsoft Dynamics NAV Server.

Supported operating systems	- Windows 10 Pro, Enterprise, or Education (64-bit edition). - Windows 8.1 Professional or Enterprise (64-bit edition). - Windows Server 2016 Standard, Essentials, or Datacenter. - Windows Server 2012 R2 Standard or Essentials (64-bit edition). - Windows Server 2012 Standard or Essentials (64-bit edition).
Hardware resources	- Hard disk space: 500 MB. - Memory: 2 GB.
Reports	- Microsoft Report Viewer 2015 for Save as Excel, Save as PDF, and Save as Word functionality.
Microsoft Dynamics 365 for Sales integration	- Windows Identity Framework. For a list of supported Microsoft Dynamics 365 for Sales versions, see Microsoft Dynamics 365 for Sales Integration Requirements.
Additional software	- Microsoft .NET Framework 3.5.1. - Microsoft .NET Framework 4.5.2. - Windows PowerShell 3.0.
Additional information	·         Dynamics NAV Setup installs the following software if it is not already present on the target computer: o    Microsoft .NET Framework 4.5.2. o    Microsoft Report Viewer 2015. o    Windows Identity Framework.

7            Microsoft Dynamics NAV Web Server Components Requirements

Supported operating systems	- Windows 10 Pro, Enterprise, or Education (64-bit edition). - Windows 8.1 Professional or Enterprise (64-bit edition). - Windows Server 2016 Standard, Essentials, or Datacenter. - Windows Server 2012 R2 Standard or Essentials (64-bit edition). - Windows Server 2012 Standard or Essentials (64-bit edition).
Web server	·         Internet Information Server 10, Internet Information Server 8.5, Internet Information Server 8.0, or Internet Information Server 7.5.
Reports	- Microsoft Report Viewer 2015 to run reports that use RDLC report layouts.
Additional software	- Microsoft .NET Framework 4.5.2. - Windows PowerShell 3.0.
Additional information	·         Dynamics NAV Setup installs the following software if it is not already present on the target computer. o    Microsoft .NET Framework 4.5.2. o    Internet Information Server 10, Internet Information Server 8.5, Internet Information Server 8.0, or Internet Information Server 7.5 depending in the operating system, with the required features enabled. ·         For more information about installing IIS, see How to: Install Internet Information Services for Microsoft Dynamics NAV Web Client. ·         To avoid crashes on the IIS server with many concurrent users, download and install the update from here Update for the .NET Framework 4.5 in Windows 8, Windows RT, and Windows Server 2012.

8            Microsoft Dynamics NAV Database Components for SQL Server Requirements

The following table shows the minimum system requirements for Dynamics NAV database components for SQL Server.

Supported operating systems	- Windows 10 Pro, Enterprise, or Education (64-bit edition). - Windows 8.1 Professional or Enterprise (64-bit edition). - Windows Server 2016 Standard, Essentials, or Datacenter. - Windows Server 2012 R2 Standard or Essentials (64-bit edition). - Windows Server 2012 Standard or Essentials (64-bit edition).
Hardware resources	For more information, see Hardware and Software Requirements for Installing SQL Server 2016. From this page, you can also access requirements for other versions of SQL Server.
SQL Server	- Microsoft SQL Server 2016 Express, Standard or Enterprise. - Microsoft SQL Server 2014 Express, Standard or Enterprise. - Microsoft SQL Server 2012 Service Pack 2 Express, Standard, or Enterprise (64-bit editions only). - Azure SQL Database V12 Standard and Premium service tiers. For more information, see Installation Considerations for Microsoft SQL Server.
Service Packs and Cumulative Updates	Unless explicitly stated, all released Service Packs and Cumulative Updates of the above Microsoft SQL Server versions are supported. It is recommended to always be on the latest released Service Pack and Cumulative Update.
Additional information	Dynamics NAV Setup installs the following software if it is not already present on the target computer: ·         SQL Server 2016 Express (64-bit edition). If the operating system on the target computer does not support SQL Server 2016 Express, Setup displays a pre-requisite warning. In this case you should exit Setup and then update the operating system on the computer to one that does support SQL Server 2016 Express. Then run Setup again.

9            Microsoft Dynamics NAV Help Server Requirements

The following table shows the minimum system requirements for the Dynamics NAV Help Server.

Supported operating systems	- Windows 10 Pro, Enterprise, or Education (64-bit editions). - Windows 8.1 Professional or Enterprise (64-bit edition). - Windows Server 2016 Standard, Essentials, or Datacenter. - Windows Server 2012. - Windows Server 2012 Essentials.
Hardware resource	- Hard disk space: 500 MB. - Memory: 2 GB.
Web server	·         Internet Information Server 10, Internet Information Server 8.5, Internet Information Server 8.0, or Internet Information Server 7.5. The following features must be enabled: o    .NET Extensibility 4.5.2. o    ASP .NET 4.5. o    ISAPI Extensions. o    ISAPI Filters. o    Request Filtering. o    Windows Authentication. o    Static Content. o    HTTP Activation.
Additional software	- Microsoft .NET Framework 4.5.2.
Additional information	·         Dynamics NAV Setup installs the following software if it is not already present on the target computer. o    Microsoft .NET Framework 4.5.2. o    Internet Information Server 10, Internet Information Server 8.5, Internet Information Server 8.0, or Internet Information Server 7.5, depending on the operating system, with the required features enabled. ·         For more information about installing IIS, see How to: Install Internet Information Services for Microsoft Dynamics NAV Web Client ·         Windows Search must be enabled on the computer that you install the Dynamics NAV Help Server on. If you install on Windows Server 2012, and Windows Search is not enabled as a file service, Dynamics NAV Setup adds the service. However, the changes do not take effect until the computer has restarted.

10        Automated Data Capture System Requirements

The following table shows the minimum system requirements for Automated Data Capture System (ADCS) for Dynamics NAV.

Additional software	- MSXML version 6.0. - Telnet or Microsoft Windows HyperTerminal. - VT100 Plug-in for each computer on which you install ADCS. - Microsoft Loopback Adapter.
Additional information	- HyperTerminal is no longer included with Windows. For more information, see What happened to HyperTerminal? in the Windows Help. - VT100 Plug-in acts as a virtual Telnet server.

11        Business Inbox in Microsoft Outlook Requirements

The following table shows the minimum system requirements for using Dynamics NAV as your business inbox in Outlook.

Supported Outlook Applications	Outlook 2013 or later, Outlook Web App, OWA for iPad, OWA for iPhone, and OWA for Android.
Supported Exchange Servers	Exchange Online, Exchange Server 2016, or Exchange Server 2013. In deployments that use Exchange Server, the Exchange PowerShell endpoint must be accessible by Microsoft Dynamics NAV Server.
Supported Authentication	The Microsoft Dynamics NAV Server must be configured to run with NavUserPassword, ACS, or AAD Credentials Type. Also, the Microsoft Dynamics NAV Web client must be configured for Secure Sockets Layer (SSL).
Supported Browsers	When using the Outlook Web App (OWA), your computer must be running a supported browser listed in the Microsoft Dynamics NAV Web client Requirements.
Supported Operating Systems	When using OWA for iPad, OWA for iPad, or OWA for Android, your mobile device must use a supported Operating System listed in Microsoft Dynamics NAV Universal App Requirements.

12        Microsoft Outlook Add-In Requirements

The following table shows the minimum system requirements for the Dynamics NAV Add-In for Outlook for synchronization with Outlook.

Supported Outlook Applications	Outlook 2016, Outlook 2013 SP1, or Outlook 2010 SP2 (32-bit edition).
Supported Exchange Servers	Exchange Server 2016, Exchange Server 2013, or Exchange Online.

13        Microsoft Dynamics 365 for Sales Integration Requirements

The following table shows the system requirements for integrating Dynamics NAV with Microsoft Dynamics 365 for Sales.

Additional software	- Microsoft Dynamics CRM Online 2016, Microsoft Dynamics CRM Online 2016 Update 1, or Microsoft Dynamics CRM 2016. - Microsoft Dynamics CRM Online 2015, Microsoft Dynamics CRM Online 2015 Update 1, or Microsoft Dynamics CRM 2015.
Additional information	- Item Availability is not supported on Dynamics CRM 2015, versions Update 1 and Online. You can obtain the item availability support by running the DynamicsNAVIntegrationSolution.zip file on the Dynanmics NAV 2016 product DVD. For more information, see How to: Prepare Microsoft Dynamics 365 for Sales for Integration.

14        Microsoft Dynamics NAV as an App for SharePoint Requirements

The following table shows the minimum system requirements for Dynamics NAV as an App for SharePoint.

Supported operating systems	- Windows Server 2016 Standard, Essentials, or Datacenter. - Windows Server 2012 R2 Standard or Datacenter (64-bit edition). - Windows Server 2012 Standard or Datacenter (64-bit edition).
Additional software	- SharePoint 2013 Service Pack 1. - SharePoint Online.

15        Automated Deployment on Microsoft Azure Requirements

Automated deployment of Dynamics NAV on Microsoft Azure by using the provisioning tools is only supported on Azure virtual machines that are running Windows Server 2012. For additional requirements for specific Dynamics NAV components, refer to the other sections in this topic.

source: https://docs.microsoft.com/en-us/dynamics-nav/system-requirements-for-microsoft-dynamics-nav-2017

Setting Up SSL for Web Services on Dynamics NAV 2009 R2 and Server 2008 R2

Published by Michael Wong on March 31, 2015 - 10:00pm

NOTE: For the purposes of explaining we will be using the port 7047; however, you can use any port configured for your Web Service.

Requirements

·         Existing Microsoft Dynamics NAV Web Services

·         SSL Certificate installed in Personal Certificates

·         Administrative rights to server

Configure Web Service to use SSL

1.     Run notepad As Administrator and open theCustomSettings.config file on the computer where the Microsoft Dynamics NAV Server is installed. The default location is:

“C:\Program Files\Microsoft Dynamics NAV\Service\CustomSettings.config”

2.     Locate the key:

false">

and change the value from false to true

true">

3.     Open the Services Snap In by going to Administrative Tools > Services.

4.     Restart the Microsoft Dynamics NAV Business Web Services service.

Import the SSL Certificate into the local computer store

If you already have the Certificates Snap-In, open the certificates Snap In and skip to step 8.

1.     Go to the Start menu and click Run.

2.     Type mmc and click OK.

3.     On the File menu, click Add/Remove Snap-in.

4.     Locate the Certificates Snap-In and click Add.

5.     Select Computer Account and click Finish.

6.     Select Local Computer and click Finish.

7.     Click OK to close the Add or Remove Snap-ins window.

8.     In the left pane of the console, expand Certificates (Local Computer).

9.     Right Click on Personal and click Import.

10.  When the wizard opens click Next.

11.  Browse to your certificate and click Next.

12.  If the certificate has a password enter it and click Next

13.  Select Place all certificates in the following store and click Next.

14.  Click Finish then OK to confirm that the import was successful.

Obtain the Certificate’s Thumbprint

1.     In the Certificates snap-in, expand the Personal folder and select Certificates.

2.     Locate the certificate you wish to use and double-click it.

3.     In the certificate window, click on Details.

4.     In the Details pane, scroll down to find the Thumbprint field.

5.     Copy the text to a text editor and remove all spaces. Save this for later

Figure 1. Certificate window with Details pane displayed and the Thumbprint field highlighted.
 

Configure the server’s Access Control List and the Web Services Port

1.     Open a command prompt window with elevated (administrative) rights.

2.     If the service is already running and configured, you will need to remove its entries.

3.     Run the following command to show all port mappings for the server:
netsh http show urlacl

4.     The system should return a list of ports and you should see one registered to DynamicsNAV:http://+:7047/DynamicsNAV/

Figure 2. The + after the http signifies localhost

5.     You will need to delete all entries associated with the port for DynamicsNAV. In the example above you see both http://+:7047/ and http://+:7047/DynamicsNAV.

Both will need to be removed.

6.     Remove them by using the following command:

netsh http delete urlacl url={your url here}

Replace the highlighted text with the url from the previous command, e.g., http://+:7047/

7.     You will now need to register the service back with a URL using https.  Run the following command to add the base service:

netsh http add urlacl url=https://+:7047/ sddl=D:(A;;GX;;;NS)(A;;GX;;;BA)

If your port is not 7047, you can adjust the URL to your needs. Make sure that the https is set in the url.

8.     Run the following command to register the DynamicsNAV web service port:

netsh http add urlacl url=https://+:7047/DynamicsNAV/ user={your service username}

Replace the highlighted portion with your service user account e.g. CONTUSO\navservices

Notice that to register the base port, I used “sddl,” and for the Web Service Port, I used “user.” You can use “sddl” for both; however, in order to do so, you will need to get the active directory SID of the user. The format will be as follows:

D:(A;;GX;;;{user SID here})

Configure the port to use the SSL Certificate

1.     Verify that the port you wish to use does not already have an SSL certificate assigned to it by typing the following:

netsh http show sslcert

2.     If you see any entry where the IP:port is bound to the same port as your Web Service, you will want to remove it by typing the following:

netsh http delete sslcert ipport=0.0.0.0:{your port here}

3.     Register your SSL certificate to your Web Service port with the following:

netsh http add sslcert ipport=0.0.0.0:{your port here} certhash={certificate thumbnail here} appid={00000000-0000-6002-0022-0000836BD2D2}

Make sure to change the highlighted areas with your appropriate information. The appID is any valid GUID in your system. The example above is the GUID for the NAV Server.

4.     Restart the Microsoft Dynamics NAV Business Web Services service.

5.     Test the service by going to the following address in your web browser:

https://localhost:7047/DynamicsNAV/WS/Services

Source: http://www.archerpoint.com/blog/Posts/setting-ssl-web-services-nav-2009-r2-and-server-2008-r2?utm_source=linkedin&utm_medium=social&utm_content=Oktopost-linkedin-group&utm_campaign=Oktopost-2015-04+General+Campaign

How to open a restored SQL backup in a different Network (pc)

You may have come across situations where you need to open a MS SQL backup file in a new environment. For example, you may have taken the MS SQL Database Backup from your client location. Now you may need to restore it your local pc and open the database using your NAV 2015 client. These are the steps that you need to follow;

•   Restore the database
•  Open the following table using SQL Server Management Studio and delete all existing data.  (Obviously, the Windows User Account names available in the tables need not be using anymore)

            Access Control

            User
            User Metadata
            User Property

•  Setup the new database by configuring the CustomSettings.xml file and run the RTC Client. In  other  words now you can open the database without any issues. You may now create  whatever the new  accounts using your RTC client.

How to Kill a NAV Application Server Windows Service

You may have many experiences where you were in need of killing a NAV Application Server or NAV Service Tier Windows Service which has been stuck at stopping. Basically, you may  have wanted to get this done without needing to reboot a server in the middle of the day.

Here’s what you need to do:

Step 1. Find out the Service Name

To do this, go in to services and double click on the service which has stuck.  Make a note of the “Service Name”.

Step 2. Find out the PID of the service

Open an elevated command prompt and type in:

sc queryex servicename

Make note of the PID

Step 3. Kill the PID

From the same command prompt type in:

taskkill /f /pid [PID]

Be careful of what you are killing though.  If you kill a critical windows service you may end up forcing the machine to reboot on it own.

Dynamics Navision Full User and Limited User Structure

• Full User 
  
  Full User licenses provide users full read and full write capabilities to all of the licensed solution functionality through any and all modes of access, including the Microsoft Dynamics NAV Windows client, the Microsoft Dynamics NAV Web client, or any other mode of access including web services. Full User licenses are for users requiring unlimited read and write access. As long as the number of users needing simultaneous access to the solution does not exceed the number of Full User licenses you have acquired, these users are properly licensed for full read and write access to the complete solution functionality.
• Limited User 
  
  Limited User licenses provide users full read, but limited write, capabilities to all of the licensed solution functionality through any and all modes of access including the Microsoft Dynamics NAV Windows client. The Limited User license is designed to give customers a lower-cost alternative for extending ERP to users who only require limited access to the Microsoft Dynamics NAV application:
• Read access to data contained in the solution through any client accessing the application, including but not limited to the Microsoft Dynamics NAV Windows client, the Microsoft Dynamics NAV Web client, and web services.
• Write access to a maximum of three application tables in the object range 0 – 99,999,999 other than the General Ledger Entry table, through any client accessing the application. Access to the General Ledger Entry Table requires a Full User license.
• Device Only User 
  
  Device-only licenses enable a user to connect, provided there is an enabled device available to use. Devices can be full or limited. Device users have either full or limited access, as determined by the device.
• Windows Group 
  
  Use this license type to create a Microsoft Dynamics NAV user based on a Windows group. All members of the group inherit permissions for the user.
  
  Windows Group licensing is a form of license multiplexing. Multiplexing does not reduce the number of user licenses required to access a Microsoft Dynamics NAV solution.
• External User 
  
  This license type is specific to individual users of Microsoft Dynamics NAV 2013 R2. External user licenses must not be shared with other individual users. You do not need concurrent user CALs for external users. External users must not use any clients provided by the Microsoft Dynamics NAV 2013 R2 Application Programming Interface (API), such as the Microsoft Dynamics NAV Windows client or the Microsoft Dynamics NAV Web client. External user licenses must not be used for business process outsourcing purposes.

Source : http://msdn.microsoft.com/en-us/library/jj551750(v=nav.71).aspx

Job Queue and NAS in Microsoft Dynamics NAV

This article explains how to configure and use the Job Queue functionality in Microsoft Dynamics NAV together with the Navision Application Server (NAS) to run background tasks automatically, without user intervention.

---

Background: Job Scheduler vs Job Queue

The Job Queue feature was introduced in Microsoft Dynamics NAV 5.0 as a replacement for the earlier Job Scheduler functionality available in NAV 4.0.

The key improvement with Job Queue is that it allows multiple background tasks to be scheduled and executed automatically by NAV, without requiring a logged-in user. These tasks are executed by NAS in the background based on predefined schedules.

---

What Is Job Queue and What Is NAS?

Job Queue provides a centralized queue where background tasks are defined, scheduled, enabled, or disabled. Using Job Queue, you can control:

• When a task starts

• How often it runs

• Whether it repeats

• Whether it is active or paused

NAS (Navision Application Server) acts as the execution engine. It continuously monitors the Job Queue and triggers the defined tasks at the scheduled times.

In short:

• Job Queue = task definition and scheduling

• NAS = background task execution

---

Main Components of Job Queue

The Job Queue functionality is supported by the following system tables:

• Job Queue Setup (Table 470)

• Job Queue Process (Table 471)

• Job Queue Entry (Table 472)

• Job Queue Response (Table 473)

• Job Queue Log Entry (Table 474)

The most important table is Job Queue Entry (472), which stores the actual job definitions.

---

Steps to Use Job Queue with NAS

Step 1: Install Microsoft Dynamics NAV Application Server (NAS)

1. Install the Microsoft Dynamics NAV Application Server.

2. Ensure the NAS service is correctly registered in NAV.

3. Configure the NAS Startup Parameter as:

   JOBQUEUE
   

This tells NAS to process tasks defined in the Job Queue.

Important:
NAS must always run without any user interface. Any GUI-related code must be disabled.

---

Step 2: Create Job Queue Entries

To schedule a background task, you must create a Job Queue Entry.

Example: Automating “Adjust Cost – Item Entries”

Suppose you want to automate Report 795 – Adjust Cost - Item Entries.

Before scheduling:

• Make sure the report does not use GUI elements

• Use GUIALLOWED() checks where required

---

Step 3: Define Job Details (Job Queue Entry Card)

Open Job Queue Entry Card (Form 673).

In the General tab:

• Object Type to Run: Report

• Object ID to Run: 795

• Earliest Start Date/Time: First execution date and time

This defines what will run and when it can start.

---

Step 4: Configure Recurrence

In the Recurrence tab, define how often the task should run.

Example 1: Run every 2 minutes between 8:00 AM and 6:00 PM

• Set recurrence interval to 2 minutes

• Define start and end times accordingly

Example 2 (NAV 2013):

Run Adjust Cost – Item Entries at 2:00 AM on weekdays only:

• Set execution time to 2:00 AM

• Select Monday–Friday

• Exclude weekends

---

Step 5: Activate the Job

Once all details are defined:

• Click Set Status to Ready

This marks the job as active and eligible for execution by NAS.

---

Step 6: Enable Job Queue Processing

Open Job Queue Setup (Form 670).

• Ensure Job Queue Active is selected

If you need to temporarily stop all background jobs, simply clear this checkbox.

---

Summary

The Job Queue combined with NAS allows Microsoft Dynamics NAV to:

• Run reports and codeunits automatically

• Execute tasks without user login

• Schedule recurring background processes reliably

This functionality is essential for automation scenarios such as:

• Cost adjustments

• Data synchronization

• Periodic batch jobs

• System housekeeping tasks

Understanding Job Queue and NAS is critical when maintaining legacy NAV systems and during upgrades to newer platforms.

How Job Queue and NAS Work Together (Visual Explanation)

The diagram above illustrates how Job Queue and Navision Application Server (NAS) work together in Microsoft Dynamics NAV to execute background tasks automatically, without user interaction.

---

Step-by-Step Flow Description

1️⃣ Job Definition (Job Queue Entry)

The process begins when a job is defined in the Job Queue Entry table.
Here, you specify:

• Object Type (Report / Codeunit)

• Object ID

• Start date and time

• Recurrence rules

• Status (Ready / On Hold)

This defines what should run and when.

---

2️⃣ Job Queue Setup Validation

The Job Queue Setup determines whether background processing is enabled globally.

• If Job Queue Active = TRUE, processing continues

• If disabled, no jobs are executed, even if they are marked as Ready

---

3️⃣ NAS Monitors the Job Queue

The Navision Application Server (NAS) runs continuously in the background with the startup parameter:

JOBQUEUE

NAS periodically checks the Job Queue for:

• Jobs marked as Ready

• Jobs whose Earliest Start Date/Time has been reached

• Jobs matching the defined recurrence rules

---

4️⃣ NAS Executes the Job

When a job is due:

• NAS triggers the specified Report or Codeunit

• The execution happens without any user interface

• All GUI-related logic must be suppressed using GUIALLOWED()

This allows NAV to run batch jobs safely in the background.

---

5️⃣ Job Processing and Logging

During execution:

• Processing details are written to Job Queue Process

• Execution results are recorded in Job Queue Log Entry

• Success, warnings, or errors are logged for review

If an error occurs, the system records the failure and may retry based on configuration.

---

6️⃣ Recurrence Handling

If the job is recurring:

• NAS calculates the next run time

• The Job Queue Entry remains active

• The cycle repeats automatically

If the job is one-time only:

• It completes and stops unless reactivated manually

---

High-Level Summary (One-Glance Understanding)

Job Queue Entry
     ↓
Job Queue Setup (Active?)
     ↓
NAS (JOBQUEUE)
     ↓
Execute Report / Codeunit
     ↓
Log Results
     ↓
Next Run (if recurring)

---

Why This Architecture Matters

This design allows NAV to:

• Automate heavy processing tasks

• Run jobs outside business hours

• Eliminate dependency on logged-in users

• Centralise scheduling and monitoring

It is especially critical for:

• Cost adjustment jobs

• Data synchronisation

• Period-end processing

• System maintenance routines

---

Important Note for Business Central Upgrades

While NAS is specific to classic NAV, understanding this flow is essential when upgrading to Business Central, where similar functionality is handled by:

• Job Queue Dispatcher

• Server task scheduler

• Background sessions