Skip to main content

Multiple RTC on Same Machine with Startup Error Resolved

Hi all,

I was just thinking that there should an way that when we start an different RTC Client that is not installed in machine, we should not get an error.

If you haven't read the post how to do it then go to the link.

Why it happens -

Role Tailored Client try's to pull up the last service that have been used successfully to connect. As in earlier post we created multiple services for multiple versions and every service is running. So how the RTC client will figure out which service to run when we click on shortcut of a particular version RTC.

OLD Story -

If you read this post about the command prompt parameter for Role Tailored client then it would be easier to Understand.

How we make RTC Icon to identify which service file it should Pick?

My current system status -

Services -
Version                 Port
NAV 2009            4046 & 4047
NAV 2009 SP1    5046 & 5047
NAV 2009 R2      6046 & 6047

Let's Search for a file Clientusersettings, you will find one HIDDEN file inside "C:\Users\username\AppData\Local\Microsoft\Microsoft Dynamics NAV\".
Lets see what this file contain, Below is the image for same.



If you want to find about all parameters then goto the link. I will describe only those are required right now.

Server -  consist of Navision Server Name where Service tier exist.
Server Instance - Instance of Service by default it is DynamicsNAV.
ServerPort -  Where you want to connect.
URL History -  THE URL Of navision that was last connected.

so what I will do is that I will copy this file and will save it inside the same folder where my .exe are present (C:\Program Files (x86)\Microsoft Dynamics NAV\60) 

and name them in the format like

FOR 2009         ClientUserSettings2009
FOR 2009 SP1 ClientUserSettings2009SP1
FOR 2009 R2   ClientUserSettings2009R2



Now lets do the configuration -

I went to Desktop where my shortcuts have been created for different versions. I went to properties of every icon and at the end of the Target line I specified the setting file that need to be used when I will try to run the client.

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

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

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

The whole command in Target for NAV 2009 R2 is now -

"C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 R2 IN\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe" -settings:"C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 R2 IN\ClientUserSettings2009R2.config"

Now when I will click on the particular icon it will start the specified RTC Database without an error.

Thanks & Regards,
Saurav Dhyani

www.sauravdhyani.com

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.