The client version does not match the server version

djkdjk

Hello,

I have an installation of NAV 2015. For testing purpose I have multiple Build version installed on the same Server / Client.
This configuration works except two components.
1) The Excel Add-In

---------------------------
Microsoft Excel
---------------------------
Microsoft Dynamics NAV Excel Add-in encountered an external error: The client version does not match the server version. You can only connect to a server with a matching version.
Client version: 8.0.39663.0
Server version: 8.0.41370.0
---------------------------
OK   
---------------------------

2) Administration Shell

Import-NAVServerLicense : The client version does not match the server version. You can only connect to a server with a matching version.
Client version: 8.0.41370.0
Server version: 8.0.39663.0

Did anyone know, what is to change, to have the possibility to work with different Build Version of the Excel Add in and the Administration Shell?

Thanks in advanced
Jeannot

JonasA

I believe the Excel Add-In reads from the Registry in windows, but I am not completely sure.

The administration shell actually imports a powershellscript on startup. The management DLL is only compatible with the build version of your servicetier.
If you want to create an administration shell for your specific version, you should make a shortcut to this path:

C:\Windows\system32\WindowsPowerShell\v1.0\PowerShell.exe  -NoExit -ExecutionPolicy RemoteSigned " & ' <Path to serviceTier>\NavAdminTool.ps1 ' "

This shortcut imports the correct DLL for usage with your version.

2 examples from me:

C:\Windows\system32\WindowsPowerShell\v1.0\PowerShell.exe  -NoExit -ExecutionPolicy RemoteSigned " & ' C:\Program Files\Microsoft Dynamics NAV\80\Service\NavAdminTool.ps1 ' "

C:\Windows\system32\WindowsPowerShell\v1.0\PowerShell.exe  -NoExit -ExecutionPolicy RemoteSigned " & ' C:\Program Files\Microsoft Dynamics NAV\80 - 40262\Service\NavAdminTool.ps1 ' "

That way you can start the correct administration shell.

djkdjk

Hello JonasA

Thank you for your Suggestion. Worked in PowerShell ISE. I imported the module of the corresponding Build and I get the error message.
As you mentioned I also create a shortcut to call the ps1 file, but also with the shortcut I receive the same error.

Did the PS command take the Version somewhere from the registry? Who can I find this key?

Best regards
Jeannot

JonasA

I'm sorry my first answer was wrong.
If you open NavAdminTool.ps1 with notepad, you should see why.
The script reads from the registry.

You can change this line:

$managementDllPath = Join-Path (Get-ItemProperty -path $nstPath).Path '\Microsoft.Dynamics.Nav.Management.dll'

To this:

$managementDllPath = 'C:\Program Files\Microsoft Dynamics NAV\80 - 40262\Service\Microsoft.Dynamics.Nav.Management.dll'

Please note that your editor might require administration rights to change files inside the Program Files folder.
You could also make a copy of the NavAdminTool.ps1 and edit that one so you still have the original file.

davmac1

NAV 2016 is different - I tried changing $nstpath - did not like that - any suggestion on what to change?

jbl@cool.is

I also tried changing the $nstpath, and that seemed to work for me. Did you rembember " "?


But you can edit the path in the registry:
"HKLM:\SOFTWARE\Microsoft\Microsoft Dynamics NAV\90\Service"

Both worked for me.

Edit: Sorry, changing the path didn't work. I had edited the wrong file and not changed the Registry path, so I Just thought it worked when it infact didn't