Tag: 70

Categories
Dynamics NAV Microsoft Registry

Microsoft Dynamics NAV Administration does not work after installation of NAV 2013 R2

After I installed NAV 2013 R2 if I try to run Microsoft Dynamics NAV Administration tool of NAV 2013 I receive the following error message:

—————————
Microsoft.Dynamics.Nav.ManagementUI.dll
—————————
MCC has detected an error in snap-in and will unload it.

– Report this error to Microsoft, and then shut down MCC
– Unload the snap-in and continue running
—————————
OK
—————————

MCC has detected an error in snap-in and will unload it

If I run Microsoft Dynamics NAV Admin tool of NAV 2013 R2, it works only for the instance of the R2 version and if I try to Start/Restart/Stop a server instance of a previous version I receive the following error message:

Error
—————————

The Microsoft Dynamics NAV Admin tool can only manage version 7.1 or later. The ServerInstance ‘{ServerInstance}’ is Version ‘{ServerVersionNo}’.
—————————
OK
—————————

The Microsoft Dynamics NAV Admin tool can only manage version 7.1 or later

Cause:
NAV 2013 and NAV 2013 R2 use different common registry keys, so after installation of NAV 2013 R2 a part of these registry keys are updated with the information of the new installation the main difference are in the path the folder 70 changed with 71 and the version number from 7.0.0.0 to 7.1.0.0.

Microsoft Dynamics NAV Administration does not work after installation of NAV 2013 R2

Idea:

  1. Restore the key with the previous values to fix the functionality of Microsoft Dynamics NAV Administration tool of NAV 2013
  2. Create a new key (as copy of the previous) valid only for NAV 2013 R2

This is the current status in the Registry Editor (click on the image to show more details):
Before FIX Microsoft Dynamics NAV 2013 Administration Keys Status

Solution:

Create a .reg file, using a text editor like Notepad with the following lines:

FIX Microsoft Dynamics NAV 2013 Administration.reg
[sourcecode lang=”bash”]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Dynamics.Nav.Management]
"ApplicationBase"="C:\\Program Files\\Microsoft Dynamics NAV\\70\\Service\\"
"AssemblyName"="Microsoft.Dynamics.Nav.Management, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"
"Description"="Microsoft Dynamics Nav Management Snap-in"
"ModuleName"="C:\\Program Files\\Microsoft Dynamics NAV\\70\\Service\\Microsoft.Dynamics.Nav.Management.dll"
"PowerShellVersion"="2.0"
"Vendor"="Microsoft Corporation"
"Version"="7.0.0.0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Dynamics.Nav.Management, Version=7.1.0.0]
"ApplicationBase"="C:\\Program Files\\Microsoft Dynamics NAV\\71\\Service\\"
"AssemblyName"="Microsoft.Dynamics.Nav.Management, Version=7.1.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"
"Description"="Microsoft Dynamics Nav Management Snap-in"
"ModuleName"="C:\\Program Files\\Microsoft Dynamics NAV\\71\\Service\\Microsoft.Dynamics.Nav.Management.dll"
"PowerShellVersion"="2.0"
"Vendor"="Microsoft Corporation"
"Version"="7.1.0.0"
[/sourcecode]

or download the file FIX Microsoft Dynamics NAV 2013 Administration.zip

Alfter you run the file the status in the Registry Editor will be this (click on the image to show more details)
After FIX Microsoft Dynamics NAV 2013 Administration Keys Status

Note: You have to run the file only once, so after running you can remove it from your computer.

Results:

Now you can manage all the instances using the Microsoft Dynamics NAV Administration tool of NAV 2013 and use the new tool of NAV 2013 R2 to manage ONLY the instance of the new version.

Did my solution solve your problem? Leave a reply.

Categories
Dynamics NAV Microsoft Registry

The client version does not match the server version

—————————
Microsoft Dynamics NAV
—————————
The client version does not match the server version. You can only connect to a server with a matching version.

Client version: {ClientVersionNumber}

Server version: {ServerVersionNumber}
—————————
OK
—————————

The client version does not match the server version

Cause:
I’ve installed more builds of NAV 2013 in the same pc and I receive the error message when I try to run an object from the Microsoft Dynamics NAV Development Environment or activate the Debugger.
To install more builds in the same machine I created a copy of the subfolder 70 and renamed the copy in 70 – 34346.
You should receive the same error message if you install NAV 2013 R2 although it has a subfolder 71.

Solution:
To run an object you could create a different icon to run the correct version of the client before to try to run an object from the Development Environment but this workaround doesn’t work if you want to activate the Debugger.
Create a .reg file, using a text editor like Notepad, for each build or version that you’ve installed.
Each time you have to work with a particolar version or build you have to use the correct reg file to override the registry key.

NAV2013.reg

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command]
@="C:\\Program Files (x86)\\Microsoft Dynamics NAV\\70\\RoleTailored Client\\Microsoft.Dynamics.Nav.Client.exe -protocolhandler \"%1\""

NAV2013_34346.reg 

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command]
@="C:\\Program Files (x86)\\Microsoft Dynamics NAV\\70 - 34346\\RoleTailored Client\\Microsoft.Dynamics.Nav.Client.exe -protocolhandler \"%1\""

NAV2013R2.reg 

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command]
@="C:\\Program Files (x86)\\Microsoft Dynamics NAV\\71\\RoleTailored Client\\Microsoft.Dynamics.Nav.Client.exe -protocolhandler \"%1\""

NAV2009.reg
NOTE: for the version 2009 or 2009 R2 you have to remove the -protocolhandler parameter 

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command]
@="C:\\Program Files (x86)\\Microsoft Dynamics NAV\\60\\RoleTailored Client\\Microsoft.Dynamics.Nav.Client.exe \"%1\""

Did my solution solve your problem? Leave a reply.