Skip to main content
Dynamics 365
·
1 min read

Microsoft Dynamics NAV Universal app for Windows devices: basic troubleshooting

You can manage the use of the Microsoft Dynamics NAV Universal app using Windows PowerShell.

How to get the version of the app through PowerShell

  1. Run an elevated Power Shell ISE (Run As Administrator) and type the following: 
    Get-AppxPackage -Name *dynamicsnav*

  2. Inspect the output

How to check if the app has not been granted for Loopback Exemption

Currently there are 2 ways – and a dirty trick.
The easy way is to check and/or enable Loopback Exemption via GUI tool called “Loopback Exemption Manager”

  1. Download GUI Loopback Exemption Manager from https://loopback.codeplex.com/
  2. Run the executable file (Loopbackmanager.exe) and check the Enabled field to inspect which app has the loopback exemption
  3. Make sure that the Dynamics NAV app is checked, otherwise you have to check it manually

The second way is to go through the almighty PowerShell scripting:

  1.  Determine who has the Loopback Exemption assigned by running the following 
    CheckNetIsolation loopbackexempt -s

    This would return a list of SID related to AppContainers (App Families)

  2. Determine the PackageFamilyName of the Dynamics NAV app using 
    Get-AppxPackage -Name *dynamicsnav*
  3. If the PackageFamilyName of the Dynamics NAV app is not listed in the one provided above, then you have to add Loopback Exemption manually in the following way: 
     CheckNetIsolation LoopbackExempt -a -n='microsoft.dynamicsnav_8wekyb3d8bbwe'

    Where microsoft.dynamicsnav_8wekyb3d8bbwe is the PackageFamilyName determined by running the Get-AppxPackage with point B.

There is also a third way – a dirty trick – to determine if there is potentially a missing Loopback Exempt.
If you download and use Fiddler (http://www.telerik.com/fiddler) to capture network traffic to troubleshoot the Dynamics NAV Universal app, and this suddenly can connect or behave as expected or in a different way than when Fiddler is turned off, then probably the issue falls back into the missing Loopback Exempt exception.
This is happening because Fiddler grants Loopback Exempt while performing network capture and typically it reverts this back when stopped.

 

These postings are provided “AS IS” with no warranties and confer no rights. You assume all risk for your use.
Duilio Tacconi (dtacconi) and Mohamad Vajid (mvajid)
Microsoft Dynamics
Microsoft Customer Service and Support (CSS) EMEA

navteam

Related posts