Skip to main content

NAV 2013, NAV 2009 R2, NAV 2009 SP1 & NAV 2009 on Same Machine with Same Ports

Hi all,

As discussed in my most of the Earlier post when we install NAV 2013, it is the best practice to Uninstall all
previous version that are installed.

Reason - When we install multiple versions of Navision after 2009 and try to run the object from the object designer it gives us an error message.

Today we will be discussing the extended part of the Posts -
1) NAV 2009 SP1 and R2 on Same Machine
2) NAV 2009 SP1 & R2 on same machine with Issue Resolution

As new version of NAV, i.e NAV 2013 have been released so we need to change some of the setting.

First of all, i will delete all the services that i have created for Post 1 and 2 by using below command -

1) Run Command Prompt as administrator.
2) Run The command sc Delete <ServiceName>
Service name can be found in services.msc.

Now i will un-install the NAV 2009 R2 Version from my Computer.

Steps to configure the NAV 2013 and other version on same machine-

1) Install NAV 2013 on your machine, I installed the Demo Version of Product.
2) The components get installed in  c:\Program Files\Microsoft Dynamics NAV\70.

3) After successful Installation i created a new folder Named 60_OLD in c:\Program Files\Microsoft Dynamics NAV\ Directory.

4) I Copied the RTC and Service Files and ClientUserSettings Files of NAV 2009, NAV 2009 SP1 & NAV 2009 R2 inside New Folder as shown below.

 * If you don't know how to create ClientUserSetttingsFile Please read the post 2.

5) Now the Default Service that Comes with NAV 2013 have not set to have port sharing and if we want to use the only port that is 7046 we need to enable it.

6) Open the command prompt as administrator and extract the service name from services.msc as shown below.

7) Run the following command as shown above.

sc config MicrosoftDynamicsNavServer$DynamicsNAV70 depend= NetTcpPortSharing/HTTP

* This command will add dependency of Port Sharing on the New service created.

8) Now we will create the service for NAV 2009, SP1 & R2, we will use the same port 7046 for all the services.
(If you are following all the steps as listed above then please read ahead otherwise in the command change the binpath as the path of the folder where you kept the RTC and Service Folder)

9) Here is the command to create a service for NAV 2009.

SC CREATE MicrosoftDynamicsNavServer2009 binpath= "C:\Program Files (x86)\Microsoft Dynamics NAV\60_OLD\NAV 6.0 IN\Service\Microsoft.Dynamics.Nav.Server.exe" start= auto obj= "NT Authority\NetworkService" type= own depend= NetTcpPortSharing

10) Here is the command to create a service for NAV 2009 SP1.

SC CREATE MicrosoftDynamicsNavServer2009SP1 binpath= "C:\Program Files (x86)\Microsoft Dynamics NAV\60_OLD\NAV 6.0 SP1 IN\Service\Microsoft.Dynamics.Nav.Server.exe" start= auto obj= "NT Authority\NetworkService" type= own depend= NetTcpPortSharing

11) Here is the command to create a service for NAV 2009 R2.

SC CREATE MicrosoftDynamicsNavServer2009R2 binpath= "C:\Program Files (x86)\Microsoft Dynamics NAV\60_OLD\NAV 6.0 R2 IN\Service\Microsoft.Dynamics.Nav.Server.exe" start= auto obj= "NT Authority\NetworkService" type= own depend= NetTcpPortSharing 

12) Now we need to start the Service NetTcpPortSharing as all the service created above depends on this service. You can find the service in Services.msc.

13) As in NAV 2013 Xp_Ndo.dll Concept has been removed but we need it for our older version. So for adding Xp_Ndo please refer  Post 1 Xp_Ndo & Post 2 Xp_Ndo.

14) Now lets change the config file of the Service i.e Custom Settings. (Remember while doing this you need to run Notepad as administrator)

15) As shown below -
    I have three database for 2009, SP1 and R2.
    I have Used the same ports 7046 For all services.
    But i have changed the Service instance
            DynamicsNAV2009,DynamicsNAV2009SP1,DynamicsNAV2009R2 Respectively.

16) Once done the part is left to change the ClientUserSettings Files so that we don't get a Startup Error.

17) As shown below i have changed the config files too with proper instance and port.

* if you don't know how to create it refer to post.

18) Now i will create shortcuts of NAV 2009, SP1, R2 & 2013 in Desktop. For 2009, SP1 & R2 i will create shortcuts from the same location where i copied them in my case for 2009 it is- C:\Program Files (x86)\Microsoft Dynamics NAV\60_OLD\NAV 6.0 IN\RoleTailored Client.

19) Now the part left is just to map the clientusersetting files with these shortcuts.

20) In the end of target line of the shortcut properties i just appended these strings -

For 2009
-settings:"C:\Program Files (x86)\Microsoft Dynamics NAV\60_OLD\NAV 6.0 IN\ClientUserSettings2009.config"

For 2009 SP1
-settings:"C:\Program Files (x86)\Microsoft Dynamics NAV\60_OLD\NAV 6.0 SP1 IN\ClientUserSettings2009SP1.config"

For 2009 R2
-settings:"C:\Program Files (x86)\Microsoft Dynamics NAV\60_OLD\NAV 6.0 R2 IN\ClientUserSettings2009R2.config"

19) Start the services will proper credentials in Logon Tab.

20) Click on all the icons in desktop and yeah we have all RTC versions working on same port in same machine as shown below.

* Remember after following all these steps you will not Run Objects from Object Designer for NAV 2009, SP1 and R2.

Let me know if anyone face any issues, or how you like this post.

Waiting for your feedback.

Thanks & Regards,
Saurav Dhyani


  1. Thank you so much. really appreciated..

  2. Much Appreciated..

  3. Superb!
    Thank you very much!

  4. Hi Saurav

    I have installed Nav2013 recently. Now i have to run Nav2009 R2(RTC) also. So I'm trying steps you have given above. But i cant proceed Step 13 and after step 17. Kindly guid me to create for multiple instance in the same port. Thank You.

    With Regards

    1. Hi Kavi,

      Let me know the detailed issue. If possible drop me a mail on
      If required you can call me on +91-7838267334 (any time after 6 on 24-mar-2013 or today after 10).

      Saurav Dhyani


Post a Comment

Popular posts from this blog

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 - 

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.

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.