RTC issue

Comments

• Options

  mohana_cse06 Member Posts: 5,503

  2013-03-22

  You need to re-install/repair NAV2013.
  
  After that you can run pages directly from Development environment. you will miss from NAV2009

  
  -Mohana
  http://mohana-dynamicsnav.blogspot.in/
  https://www.facebook.com/MohanaDynamicsNav

  0
• Options

  Ravi_Prakash_Goyal Member Posts: 72

  2013-03-22

  This is a limitation, i guess. When you run pages from dev env, system will pick last installed NAV version and open your RTC for that version.
  
  However, I found the root which triggered this (or you can call this workaround without reinstall NAV2013)
  
  Follow these steps:
  1. Go to Registry (Start -> Type 'regedit')
  2. Go to HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command
  3. Here you will find one registry entry with 'Default' name.
  4. Double click on this, the value data is nothing but the last installed NAV RTC client exe path. So if you installed NAV2009R2 after NAV2013, you should be able to see NAV 2009 R2 RTC client exe path.
  5. Here you can change this exe to NAV 2013 client exe path, which should be
  C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe -protocolhandler "%1"
  
  Please note that there is additional parameter in above command <-protocolhandler "%1">. This is required for NAV 2013 exe (not for NAV2009R2). Don't ignore this, otherwise it will not work.
  
  6. click ok.
  7. Now reopen NAV2013 dev env, try to run page. It should open in NAV2013 RTC client.
  
  This is just a workaround.
  
  I did not try, but you can run a batch file to change the registry key value based on which client version you are running. May be in the RTC client shortcut.
  
  Hope this helps.

  0
• Options

  kine Member Posts: 12,562

  2013-03-24

  Or you can try to use my protocol handler app... :-)
  
  http://navprotocolhandler.codeplex.com/

  Kamil Sacek
  MVP - Dynamics NAV
  My BLOG
  NAVERTICA a.s.

  0