DynamicsNAV protocol handler

Now, when NAV 2013 beta was released, many partners could struggle from the problem of side-by-side installation of the NAV clients. Problem is, that the development environment is using the URI (hyperlinks) to open the objects in RTC. Because the protocol is handled by default only the latest installed version, you can have problem if you need to use it with more versions. And because that, I have created this handler for you.

Download v1.0.2.0


After you copy the files somewhere and run the exe, you can activate the handler. Since that, instead the RTC my app will be started for each opened URI. The app will try to find correct version of RTC to run. This could be a problematic, but if you open the URI directly from active classic client, it should work. If you run the hyperlink e.g. from “Run” dialog of windows, the default RTC will be used (there is no way yet to check version of the target NST I know). If you have some tip how to check that…


P.S.: Using this handler, the Windows 7 "Jump Lists" will not work for NAV. It means, you will not have the new feature of Windows 7, when you can directly from the application icon start some functionality without opening the client first. This is working only when the handler is deactivated and you run the RTC once after that.

P.S.: 18.5.2012 11:11 - download updated to v1.0.2.0 (.NET v3.5)

Have a fun with NAV!

Posted: 2012-5-18 7:13 by Kine | with 8 comment(s)
Bookmark and Share


# re: DynamicsNAV protocol handler


Just tried to use v1.0.2.0 with .net v3.5, but it doesn't work for me. I always get the message

"Same version of RTC was not found"

I have a directorystructure as described in 2) in the txtfile. I use for example the directory C:\Program Files (x86)\Microsoft Dynamics NAV\6_0_32580_0_20120518112742\ with the Classic, service and RoleTailored Client directory. the finsql.exe is in the C:\Program Files (x86)\Microsoft Dynamics NAV\6_0_32580_0_20120518112742\Classic\ dir, the RTC client is in C:\Program Files (x86)\Microsoft Dynamics NAV\6_0_32580_0_20120518112742\RoleTailored Client\.

There are a lot more directories in C:\Program Files (x86)\Microsoft Dynamics NAV\, all with different versions. I think it should work, but it doesn't...

If this works, it would be a great help for me and a lot of my collegues...

Friday, May 18, 2012 11:44 AM by John van Poelgeest

# re: DynamicsNAV protocol handler

You must be sure that the build numbers of both exe (finsql.exe and the RTC exe file) have same build number. In your case, the tool will look into all folders in C:\Program Files (x86)\Microsoft Dynamics NAV  for the correct file version.

Friday, May 18, 2012 12:31 PM by Kine

# re: DynamicsNAV protocol handler

hi Kamil

Did need it today. And luckily I knew you did wirte soemthing about it. Quick and easy instal, but I am getting the same error as John van Poelgeest even though my NAV 2009 R2 RTC and Server exe do have the same buildnumber 33949. Any suggestions?

b rg


Wednesday, November 07, 2012 12:58 PM by Luc van Vugt

# re: DynamicsNAV protocol handler

Hi Kamil,

Did you test this with the new NAV 2013 R2? I eventually got it to work "out of the box" with NAV 2009 and NAV 2013, but now with NAV 2013 R2 (preview release) it is broken again.


Wednesday, September 11, 2013 12:12 PM by Erik P. Ernst

# re: DynamicsNAV protocol handler

Not yet, I will check...

Friday, September 13, 2013 10:26 AM by Kine

# re: DynamicsNAV protocol handler

Try the latest version For me working without problems.

Tuesday, September 17, 2013 4:16 PM by Kine

# re: DynamicsNAV protocol handler


i've installed Version on my Window 7 PC, with .net 4.5.

And Dynamics NAV 2009 R2, 2013, 2013 R2.

at moste it works fine. I can now Run Objects from each Client, the right database will be started.

When i run from 2009 the Mapping window open to define a Connection.

When i run from 2013 & 2013R2 the Mapping window dont open.

At fist call ist not a Problem the Right RTC and Company open.

But when i will run a second time and the RTC is still open, nothing happends.

At the Error log there are an unexpected Exeptions for this Event ExeptionInfo:"System.AccessViolationException"

Monday, October 28, 2013 11:28 AM by Me

# re: DynamicsNAV protocol handler

@Unknown "Me": Look there> navprotocolhandler.codeplex.com/.../basic

There are known issues. You can add your issue there. With 2009 there are problems when URL "explosion" is used (2009 work ok when you pass the dynamicsnav:////... URL without the server name etc. But than it uses the Last used server and instance and we do not want that. But URL with server name and instance name sometime do not work...). When starting from 2013, the client is sending full URL already, because you are selecting the instance inside the C/Side. Than I do not need to open the mapping, because it is known...

Tuesday, October 29, 2013 7:54 AM by Kine

Leave a Comment