共用方式為

App-V 4.6SP1: Issue with Sequencing the Dynamics NAV 2009 R2 Client

  • 發行項

There is an issue that currently being investigated by the App-V support team regarding virtualization of the Microsoft Dynamics NAV 2009 R2 client with the new App-V 4.6 SP1 sequencer. It appears the issue is tied to the Classic Client more and not the Role-Tailored client. In addition to the workflow being slightly different from the workflow outlined here:

https://msdn.microsoft.com/en-us/library/gg670188.aspx

The Role-Tailored client will also need to be sequenced using a VFS path rather than an SFT mount (MNT) path. You will need to change this part of your recipe:

Section: “To run Microsoft Dynamics NAV 2009 R2 Setup”

In Step 5: Do not specify the destination directory. Use the default directory.

It is also recommended to install the  Visual C++ 2008 SP1 run-time module on the Sequencer in advance.

Package Accelerators

There may be a maximum path limitation being hit preventing the creation of a package accelerator resulting from a VFS installation. This is caused by 3 factors: 1.) Lengthy paths created by the Dynamics installation. 2.) The package accelerator creation process adding additional 7 characters to the package root. 3.)  If the sequencing machine is a single volume machine where the Q:\ drive is actually a substitution.

You can work around this by creating a second partition for the Q:\ drive on the sequencing workstation.

Comments

  • Anonymous
    January 01, 2003
    Can you please tell me if installing to the MNT path is still applicable. I tried this and noticed the client is installed to "C:Program Files (x86)Microsoft Dynamics NAV60" on my sequencer machine. How will this be installed on my machine where the package is pushed to? Furthermore I'm also running into the same installation memory error as I have with installing an AX client. For AX this is resolved by stopping the "Windows Presentation Foundation Font Cache 3.0.0.0" service, but unfortunately this was already done.

  • Anonymous
    January 01, 2003
    mheijkant - for some reason, I did not notice your comment until now. I apologize for the long delay. I would advise sequencing VFS (install to the defaults) on a 32-bit sequencer instead of a 64-bit sequencer even if you are deploying to x64.

  • Anonymous
    October 10, 2012
    Hi, I am also facing the same above mentioned memory error when run/installed Nav  to default path and when changed the path where the package was created the entire process gets hanged up. Stopping the services also did not solve the problem.Hence I am uanble to sequence NAV :( Could you please let me know how it can be achieved.