More NAV 2013 builds on the same server

Ivan_Jurka

I created more services on one server to be able maintain different build of NAV as described in article http://blogs.msdn.com/b/nav/archive/2012/10/18/how-to-have-few-microsoft-dynamics-nav-2013-services-on-the-same-server.aspx (with separate Service folder for new build).

All is working smoothly, only debugger is not working, by using development client 34902 i got an error:
The client version does not match the server version. You can only connect to a server with a matching version.
Client version: 7.0.33781.0
Server version: 7.0.34902.0

Any idea or experience what setting has to be changed?

tedl30

You must have same build in client folder and server folder

Ivan_Jurka

Of course this is what I have. I want to have the old standard DVD build in default folders and the new build in new folders (C:\Program Files\Microsoft Dynamics NAV\70_Latest\Service and C:\Program Files (x86)\Microsoft Dynamics NAV\70_Latest\RoleTailored Client).

My question is: What have I to change that I can call from the latest development client (the latest folder) the latest RTC client when debuger is called? Is there any setup file or registry?

mohana_cse06

Yes, here is the registry path
HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command

Ivan_Jurka

Thank you for your reply.
By changing of this registry I'm able run debugger with the latest build but the debugger is not working with the old build (this I expected).
Any other suggestion?

rsaritzky

I really would like NOT to have to make a registry change each time I switch NAV2013 builds in order to run the debugger - I am actively working on 2 projects, and using 2 different builds of NAV2013. Sometimes, I have both environments open at the same time.

We don't seem to have the same problem with NAV2009 - we have several client builds installed and can switch back and forth. The problem though is the debugger which of course NAV2009 doesn't have.

Has anyone found a solution to this?

Sam_Morris

Have you tried

http://www.mibuso.com/dlinfo.asp?FileID=1443

rsaritzky

Thanks for the reply - I actually found a workaround for this issue.

If you create a shortcut to the NAV2013 RTC, then in the "Target" property line of the shortcut, add /debug to the end, e.g.

"C:\Program Files\70 Build 37907\RoleTailored Client\finsql.exe" servername="server\navdb",database="DATABASE_700",ntauthentication=yes,id=%NAVZUP%\%username%-RON /debug

Then, when you run this shortcut, it will open the "Sessions" window and allow you to attach to the correct session.

The only issue after that is that sometimes, the debugger won't "activate" or "trigger" when you start your action in the regular RTC window.

To make it activate, there are two options:

1. Click "Break" inside the debugger window, then start your action (this to me seems like the easiest)
2. Add code to your object to generate an error, e.g. ERROR().

Many thanks to Mike Doster from Microsoft Support for cluing me in on this hint - saved me a LOT of hassle.

Saga

Hi, that sounds good to me - unfortunately it don't work in my environment.

I get an error like: "/debug is a not known parameter"
My build is 35201.

Do you have any suggestions?

THX
Saga