Luedi
March 2, 2016, 3:37pm
1
Hi All,
I have the same issue as already described at:
dynamicsuser.net/…/75871.aspx
But for NAV 2015 and 2016.
I have already tried the solution there, and 2013 + 2013R2 are working correct.
But In 2015 and 2016 if a do a run of an object from the Dev-Client always a new client is opened.
Im not sure since when this happens but it could be that it was happend by updating 2016 to Rollup 4.
A also tried to add the Default company with noch change of the behavior.
Any Ideas?
Greetings
Thomas
Luedi
March 7, 2016, 9:20am
3
Thanks Jonathan for the advice, but this doesn’t help.
On my PC the Registry Link points to:
C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe -protocolhandler “%1”
I have already tried to change it to 70 but nothing happend.
Also I don’t have the problem that the client doesn’t start, my problem is that the client starts a new instance for every run from the Dev-environment, just like the dev-environment is loosing the connection to the already started client…
Hi,
you get a new client, if you have startet a runmodal page or report in the actual RTC. I have tested it in NAV 2016 (CU4).
What happens, if you do this?
no RTC is running
run a report of the development environment
close the requestpage, but the rtc is still open
run the report again of the development environment
Do you get a new rtc or opens the report in the existing session?
best regards
Robert
Luedi
March 8, 2016, 7:31am
5
Hi Robert,
i know, if a runmodal page is still open you will get a new instance of the RTC.
But in my case no modal page is open.
I did the follwing test:
Run Report 1 (chart of accounts) - close the request page.
Run Report 1 again.
Run Page 1 (Company information) - close company information page.
Run Page 1 again.
Run Table 3 Payment Terms - close the opened table.
Run Table 3 again.
After that I have 6 instances of the RTC open.
I usually get the message that this not my standard connection when I start the client, so i thought this could be the reason.
I fixed this in the ClientUserSettings.config so that the RTC starts without any warnings, but this also doesn’t help.
so far thanks for your help, it seems that I am the only one who has this problem.
Luedi
March 9, 2016, 8:10am
7
The Solution behind the Link in Ivans Blog worked perfect, thanks for your help!