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

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.