Docker – unable to add endpoint

Original URL…


Quick Fix : Visual Studio displaying NAV Report Layout as XML

Original URL…

I got this issue with Visual Studio 2015 Enterprise Edition. 

Every time I open a Dynamics NAV report layout in Visual Studio, RDLC is rendered as XML file instead of visual layout with all the fields and tool boxes. 

How the report layout looks: 

FIX : In order to fix the issue you need to install “Microsoft SQL Server Data Tools”

To install “Microsoft SQL Server Data Tools” you need to go to 
Control Panel  -> Programs and Features – > Microsoft Visual Studio <Edition> -> Change

Or you can re run the installation setup. 
From the features list, enable “Microsoft SQL Server Data Tools” option and proceed. 

Once the installation is completed you are good to go. This time report layout will open in correct design layout. 
Hope this helps you to resolve the issue. happy designing. 

Dynamics NAV – Reporting

ERROR: Component Model Cache



Al intentar abrir el layout de un report, en este caso de Dynamics NAV 2013 R2 con Visual Studio 2012, salta el error de la figura.

Solución: Borrar o renombrar el archivo “ComponentModelCache“, que podemos encontrar en la siguiente ruta: “%AppData%\..\Local\Microsoft\VisualStudio\11.0\“.

Referencia: articulo.

ERROR: Dynamics NAV App – No se puede conectar al servidor


Solución : Ejecutar el cmd

CheckNetIsolation.exe LoopbackExempt -a -n=microsoft.dynamicsnav_8wekyb3d8bbwe

Notas: see Link… – How to Connect Dynamics NAV Mobile Client – Published: January 19, 2015 (copy of contents link)

My intention of this post is to show you how to setup the mobile client when using a Windows 8.1 PC or laptop with Dynamics NAV installed in the 3-tier on one computer configuration.  The NAV Team Blog post How to get Microsoft Dynamics NAV for tablets to connect using a self-signed certificate covers how to connect but you must complete a step that is shown in the last comment to fix a loop back issue if using non-server windows.

You need to have Dynamics NAV 2015 already installed with the web client working and be able to connect.  If you need to install NAV, then you can look here to the Installation and Configuration Walkthroughs.  To verify the web client is ready please test the connection by opening a browser and going to the URL http://<machine name>:8080/DynamicsNAV80/WebClient/ . The URL you use should be similar if you used the default settings when you installed NAV.  In my case, 7mz8g12 (this is important later for creating the certificate) is my machine name so my URL is http://7mz8g12:8080/DynamicsNAV80/WebClient/

Moblie Nav-1

You can also see the tablet URL by just adding tablet.aspx to the end of the Web Client URL :8080/DynamicsNAV80/WebClient/tablet.aspx”>


Moblie Nav-2

Once NAV have been verified, download the mobile client from windows store.  Go to the Store and search for

Dynamics NAV: 

    Moblie Nav-3

You should be brought to a page similar to this:

Moblie Nav-4Click Install and follow the dialogs if this is the first time you are using the store.
You can also ignore:
Moblie Nav-5

The app will work with a mouse and keyboard for non-touch enabled pc and laptops.

Moblie Nav-6

Once you have the app installed you are ready to create the certificate and enable SSL for the NAV tablet app.

1. Create self-signed certificate (These steps are copied from the NAV Team blog post listed above)
a. Download and save the PowerShell script from:
b. Open a PowerShell prompt with the option Run As Administrator. I like to use Powershell ISE (C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe) since there is so much more going on with NAV and Powershell in current versions.
i. Go to the directory where you saved the New-SelfSignedCertificateEx.ps1 file and run the following commands:
1. cd <file location>
2. Import-Module .\New-SelfSignedCertificateEx.ps1
ii. Then run the following command (hint: Use the IP address of your computer instead of machine name when creating the certificate, that way you can connect an external tablet to you NAV server):

Moblie Nav-7
As you can see I used only 7mz8g12 (or if IP then for me) for what they call <your site name>
2. Manage the certificate:
a. Open the mmc.exe.
Moblie Nav-8

b. Go to the File menu, and then choose Add/Remove Snap-in…+

Moblie Nav-9

c. Select Certificates.
d. Choose Add.
e. Select the computer account.
Moblie Nav-10

f. Choose Next.

Moblie Nav-11
g.  Finish and then OK.
h. Locate and copy the certificate you just created in the personal/certificates folder.
Moblie Nav-12

i. Copy the certificate and Paste the certificate into the Trusted Root Certification Authorities/Certificates folder. Moblie Nav-13
3. Enable https
a. Here is the official guide:
i. Walkthrough: Configuring Web Services to Use SSL (SOAP and OData)
b. Open IIS Manager
i. Find NAV 2015 Web Client
ii. Click on Edit Site -> Bindings…
iii. Then click Add…
iv. Once in the Add Site Binding dialog select the Type to https and then select the certificate you created.
Moblie Nav-14I have found the IP one more useful:
Moblie Nav-15       

c. Click OK and the certificate should be set.
4. Fix the loopback issue:
a. This part is key for using a non-server pc.
b. If you prefer command line then you can run the following command in Powershell:
CheckNetIsolation.exe LoopbackExempt -a -n=”microsoft.dynamicsnav_8wekyb3d8bbwe”
Moblie Nav-16      

c. Use Fiddler – The free web debugging proxy for the visual approach:
i. Open Fiddler
ii. Select Win8 Config
Moblie Nav-17           
             iii. Make sure the checkbox is checked next to Dynamics NAV if you ran the Powershell command.  If you didn’t, check the box now.

You can test the NAV app connection by entering in the following URL:
https://<machine name>/DynamicsNAV80/
Moblie Nav-18

If everything is correct then you should see:
Moblie Nav-19

If you would like to connect an android and/or iOS device then please complete the steps listed in the How to get Microsoft Dynamics NAV for tablets to connect using a self-signedcertificate.

For more information, feel free to reach out to me at

Microsoft Dynamics NAV 2017 tablet client testing using OpenSSL certificates


OpenSSL> genrsa -out navClient.key 4096
Generating RSA private key, 4096 bit long modulus
e is 65537 (0x010001)
OpenSSL> req -new -key navClient.key -out navClient.csr
problem creating object tsa_policy1=
13168:error:08064066:object identifier routines:OBJ_create:oid exists:crypto\objects\obj_dat.c:689:
error in req


En, openssl.cfg, Comentar las líneas: tsa_policy.


Power BI desktop gives error (415) Unsupported Media Type with only certain OData feeds from NAV

Si os encontráis que, al crear una nueva conexión Odata  desde el desktop, obtenéis el siguiente error, es debido a que PowerBI utiliza una cache para para los datos que provienen de Odata la primera vez que se consume una fuente de datos Odata

Cuando quieres añadir una nueva conexión Odata, al entrar la URL, es cuando se obtiene el error.

Para corregir el error en PowerBI Desktop, has de ir a Archivo/Opciones y configuración/opciones. En el apartado “Carga de datos” has de pulsar en borrar todo. More…

SSRS ERROR: Failed to register url=http://+:80/ReportServer/ for endpoint 2, error=5

Error que se puede dar al ejecutar SQL Server Reporting Services.

  1. Reporting Services: Error creating HTTP endpoint – Access is Denied (Solución del error HTTP Error 503. The service is unavailable)
  2. Y la solución del otro error “Los permisos otorgados al usuario ‘Dominio\usuario’ son insuficientes para realizar esta operación. (rsAccessDenied)” (Solucion).
    1. Start IE as an administrator and load your SSRS site
    2. Go to Folder Settings and add your user name and assign relevant Role(s)
    3. Start IE or any other browser for that matter and the SSRS site comes up good