NAV2016 ClickOnce

vremeni4vremeni4 Member Posts: 323
Hi all,

Could some confirm this bug during the installation of NAV2016 via Clickonce.
When I run
mage -update Microsoft.Dynamics.Nav.Client.exe.manifest -fromdirectory .
I am getting following error message:

Warning MSB3110: Assembly 'C:\inetpub\wwwroot\Demo\Deployment\ApplicationFiles\Microsoft.Dynamics.Nav.Client.x86.exe' has mismatched identity 'Microsoft.Dynamics.Nav.Client', expected file name: 'Microsoft.Dynamics.Nav.Client.exe'.
Warning MSB3187: Referenced assembly 'C:\inetpub\wwwroot\Demo\Deployment\ApplicationFiles\Microsoft.Dynamics.Nav.Client.x86.exe' targets a different processor than the application.

I am aware that Microsoft introduced a new 64-bit window Client .
https://msdn.microsoft.com/en-us/library/mt299401%28v=nav.90%29.aspx

Now we have following files in the ApplicationFiles folder, 32- bit client
Microsoft.Dynamics.Nav.Client.x86.exe with Microsoft.Dynamics.Nav.Client.x86.exe.config
and 64-bit client
Microsoft.Dynamics.Nav.Client.exe with Microsoft.Dynamics.Nav.Client.exe.config

The problem is that both files have the same description, so when mage is run it reports above error.
The only way to resolve this issue was to remove the 2 files for 32-bit client from ApplicationFiles folder.
Microsoft.Dynamics.Nav.Client.x86.exe with Microsoft.Dynamics.Nav.Client.x86.exe.config

The problem in this case is that only 64-bit client is deployed.

Thanks.

Answers

  • lyngelynge Member Posts: 85
    edited 2015-12-05
    I've also seen this - and was also concerned until i tried my clickonce install on a x86 system and it worked (after deleting the x86 files as you tried)...
    Have you actually tried it on a x86 system?
  • vremeni4vremeni4 Member Posts: 323
    Hi,

    Thank for your conformation.
    I tried to use clickonce installation from above deployment on a 32bit machine and the client crashes on starting Windows(RTC) client, no error message is reported. :-(
    I think Microsoft should at least show an error message in this case, rather then to allow a client to crash.
    Currently it crashes with this error message
    Problem signature:
      Problem Event Name:	CLR20r3
      Problem Signature 01:	Microsoft.Dynamics.Nav.Client
      Problem Signature 02:	9.0.43402.0
      Problem Signature 03:	562a3482
      Problem Signature 04:	Microsoft.Dynamics.Framework.UI.WinForms
      Problem Signature 05:	9.0.43402.0
      Problem Signature 06:	562a3575
      Problem Signature 07:	e79
      Problem Signature 08:	2
      Problem Signature 09:	System.IO.FileLoadException
      OS Version:	6.1.7601.2.1.0.256.48
      Locale ID:	2057
      Additional Information 1:	0a9e
      Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
      Additional Information 3:	0a9e
      Additional Information 4:	0a9e372d3b4ad19135b953a78882e789
    
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
    

    In other words the above deployment only works for users with 64-bit machines.

    Annoyingly there is no nice error message for 32bit machines.
    I guess the only solution is to create two deployments one for 32bit clients and one for 64bit clients.

    Thanks.
Sign In or Register to comment.