Settings Parameter

ta5

Hello
Has anybody used the settings parameter to start RTC with a specified ClientUserSetting.config-File?

I've tried but the security message concerning the standard server does pop up anyway, so I guess the settings parameter is ignored ](*,)

This is the message text:

---

Microsoft Dynamics NAV Security Notice

---

You are about to connect to '<service name>' on server '<servername>', which is not your current default connection setting.
This can create a security risk.
Do you want to continue?

I would like to use this on a development server, so I can start different RTCs with different databases. The service tiers are already up an running, port sharing is not used. RTC can connect, Servicename and company is specified in the link, so everything works but not to omit the security message.

Any suggestions welcome. Thanks.
Thomas

ta5

Nobody?
Any hint would be very appreciated.
Thanks.
Thomas

dr75

Can you give an example of what arguments you are passing when starting up to specify a different ClientUserSettings.config file?

ta5

This is the string behind the start icon:

"x:\Customer_xy\NAV200901\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe" "dynamicsnav://servername:7048/serverinstance/CRONUS (Schweiz) AG/" -settings:"x:\Customer_xy\NAV200901\RoleTailored Client\ClientUserSettings.config"


X is the drive where all our customer installations are copied to. Of course Nav needs to be installed once on every development machine, but then it starts from x, as it always did with the classic clients since version 1.x. As you can see, we try to give every customer installation a unique icon with a unique ClientUserSettings.config.

Thanks in advance
Thomas

dr75

Is the connection settings the same in both the hyperlink argument and in the clientusersettings.config file? The warning you are seeing, is issued when the connection settings in the argument is different than the settings in the clientusersettings file.

Please check that. Casing could be an issue.

dr75

Do you need the hyperlink argument? You can specify the connection settings in the ClientUserSettings.config file.

ta5

Thanks!
Do you think the way (calling the Microsoft.Dynamics.Nav.Client.exe from a network share) I'll try could be the issue?
Btw: How would the target string in the icon look like without the hyperlink?
Thomas

dr75

The warning you are seeing, should not come from starting the application from a network share, unless we fail to pick up the specific ClientUserSettings.config file. The warning is issued based on different servername and serverinstance, when comparing the hyperlink arguments and the settings coming from the config file.

I can see, that the company cannot be specified in the ClientUserSettings.config file, so you need the hyperlink for that.

I would double check, that the arguments in the hyperlink matches the entries in the ClientUserSettings.config file.

I would assume, based on this URL "dynamicsnav://servername:7048/serverinstance/CRONUS (Schweiz) AG/", that you should have the following entries:

<appSettings>
<add key="Server" value="servername" />
<add key="ServerInstance" value="serverinstance" />
<add key="ServerPort" value="7048" />

geordie

Sorry for bumping old threads but today I encountered this problem, assisting a client for a 2009 SP1 -> 2009 R2.
RTC is exposed trough a Citrix web interface which manage 2 balanced servers: following dr75's suggestion I cross checked launch string and CustomSettings.config file, finding out they were coherent; therefore client opens the right db/company (which is specified in the string). Even more odd some users didn't face the message and the only difference I was able to find was in ClientUserSettings.config.

Error:

<appSettings>
  <add key="Server" value="localhost" />
  <add key="ServerInstance" value="DynamicsNAV" />
  <add key="ServerPort" value="7046" />

Fine:

<appSettings>
  <add key="Server" value="xx-app.xx.local" />
  <add key="ServerInstance" value="xx2009R2" />
  <add key="ServerPort" value="7048" />

Does anyone have any clue why in some cases the parameters in run strings seem not be read? It's a brand new interface, so a "fresh" environment with no users previous access.