Skip to main content

NAV 2013 R2 - How to Create a New Service Instance..

Hi all,

Most of us know it but i still would like to have a post on this because a keep on getting questions about it.

This post is just list down the steps for creating a new service in NAV 2013 R2. So if you know it you don't need to read ahead.



Steps to Create a New Service-

1. Open Microsoft Dynamics NAV Administration.

2. From Left Hand Menu Right Click Microsoft Dynamics NAV (Local) and Select Add Instance.


3. A new window will Popup with Title Server Instance. In this window you need to specify Following Parameters.

a) Server Instance (Name of Service)

b) Port Numbers from Management Services , Client Services (Used by all the clients to connect), SOAP Services (Read & Write Web Service) & ODATA Services (Read Web Service).

c) Login Account (Account used to Run the Service - Default Value NETWORK SERVICE)

You can specify any valid Port Number which is currently no in use in your system. The Default Ports are 7045, 7046, 7047 and 7048 Respectively.

For the Demo i am using Port No. 10045, 10046, 10047 and 10048 respectively as shown below.

4. Once i click ok the service is created and it will be stopped by default. What the tool did is -
" It Creates the copy of standard service and change the port numbers as specified in step 3"

5. we may require to point this service on a different server or a different database or May be both.

6. Click on Service from left hand panel, the details of services will be available in center panel as shown below.


From General Tab you can change the Database Name, Database Server and Database Instance. For Changing anything you need to select Edit which is placed at Right Below in Screen.

If you want to change the Login Account, then From Action Pane in Right Select Login Account and Edit the setting as per your requirement.


I hope you will now be able to create services as per your requirement.

Thanks & Regards,
Saurav Dhyani
saurav-nav.blogspot.in

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.