Cannot Connect Web Client to NAV on Azure SQL

In my last two articles, I’ve showed you how to deploy Microsoft Dynamics NAV 2016 on Azure using Azure SQL Server. Now, if you already finished it any you want to use NAV Web Client, you have to install Web Server components on VM you configured as service tier and create Endpoint for WebClient on this VM, opening port 8080. Now you have to login with different username (for example, Admin username you already used on your VM). Now, you have to type the following URL: http://<AzureVM_Name>.cloudapp.net:8080/DynamicsNAV90/WebClient/

If you have problem with connecion and get the error message, this is probably because port 8080 is not opened. If you want to open this port, you have to open Remote Desktop Connection to your VM and run the following: Control Panel > Windows Firewall > Advanced Settings > Inbound Rules.

AzuWC_CP_Fw.png

If you can find “Microsoft Dynamics NAV 2016 Web Client” as rule, you need to add 8080 as Local Port. But if you cannot find it, create a new rule (using the command in the right pane) and add this name and local port.

Advertisement

How to Deploy BACPAC on Azure SQL

This topic is in connection with my session “Deploying and Managing Dynamics NAV 2016 with Azure SQL Database” on NAV TechDays 15 and I want to continue my previous article.

Before I start with BACPAC deployment, first I have to make a small correction of my previous article. Last time, I forget one important thing. Before you create BACPAC file, you have to delete all Windows users from your source database.

You can do it in following way. In SQL Server Management Studio, find your source database and collapse it until you find Security > Users. Then check all users (right-click > Properties > General).

You need to check User Type field; if you find Windows User, you need to delete it. Right-click on this these users and choose Delete.

sql1

Now, you can continue with all steps I’ve already described in previous article. Now, we can start with deployment.

First, we have to have Azure subscription and create Azure SQL Server. When you open your Microsoft Azure Portal (https://manage.windowsazure.com), choose SQL DATABASES and choose SERVER tab. Click ADD and type your Login Name, Login Password, Region and click on Complete.

sql2.png

You will get some weird name as Azure SQL Server. Click on this SQL Server, go to DASHBOARD tab and copy this SQL Server name. Add .database.windows.net to your SQL Server name; this will be your full SQL Server name. Now, go to CONFIGURE tab and Add Allowed IP address to Azure SQL firewall. This step is necessary if you want to use this SQL Server from your local computer (with this step, you added your computer IP address to Azure). Every time you want to connect from some other computer to your Azure SQL Server, you have to repeat this step.

Now, you need to make connection from your SQL Server Management Studio to your Azure SQL Server. In Server Name, you need to type your full Azure SQL Name and your Login and Password.

sql3

When we make connection, we can start with deployment. Go to Database, right-click and choose Import Data-tier Application. You need to choose your BACPAC file, your target Database file and continue until system finish with deployment.

sql4.png

Now we can check result. We can find new database on SQL Server Management Studio on Azure SWL connection. Also, we can see in on Azure Portal; choose DATABASE tab on SQL DATABASES.

In process of deployment, it is possible to have one issue. This is situation if you can only select the obsolete service tiers of Azure SQL Database, Web and Business, with a maximum database size of 150 gigabytes (GB), when you try to set target database. Of course, in this situation, there is no option to select the new service tiers, Basic, Standard and Premium. If you try to upload on obsolete service tiers, you will get the error message.

This issue occurs because SQL Server Management Studio 2014 is not updated to match the current service tier offerings. This issue was first fixed in the Cumulative Update 5 for SQL Server 2014. You just need to install this CU 5 and repeat deployment step.

NAV on Azure SQL on NAVTechDays

Last week we finished one of the best NAV conferences this year. NAV Tech Days this year had about 950 NAV passionate attendees from all around the world. Everything in organization was the amazing; Luc did a great job.

This NAV Tech Days was very special for me, because I was the speaker on this conference for the first time. My topic on NAV Tech Days was “Deploying and Managing Dynamics NAV 2016 with Azure SQL Database”. This is something new in Microsoft Dynamics NAV 2016. I know, a lot of partners still not use NAV on Azure, but by my opinion this feature can move all of us forward. Azure SQL can save a money and we finally have a good tool for managing our multitenant environment – Management Service Portal.

I gave a word to people on my session that I’ll publish my presentation and PowerShell scripts on my blog. You can find them here:

In few following scripts, I’ll describe all details about using NAV 2016 on Azure SQL Server and give you some answers on additional questions I already got.

2015-11-23_13-19-19.png

After NAV 2016, NAV ‘Madeira’ Is Coming

Unfortunately because of my backache, I cannot be involved in this year Directions EMEA as I really want. But I try as I can. On other side, I have more time to write.

Yesterday and today we’ve heard a lot of amazing news in NAV 2016. It is one of the best releases and I think we can say that people from Microsoft made awesome product. A lot of functional features and more technical really good things. We will speak about them in few following months. There will be a lot of documents, videos… I hope a new projects…

But what next. For now, we have information where will be the next Directions EMEA. It will be one of the most beautiful cities on the world – Prague, for the second time. And we also know what a code name of next NAV release is. It is NAV ‘Madeira’ and we can start to find it on an open see.

NAV-Madeira

What we can expect in this new release? Currently, we know only few initial priorities, but it looks pretty good:

  • Office 365: Further enhanced “in” Office 365 experience
  • Azure: Pre-packaged Azure ML services
  • Core Product: Developer experience, More service integrations
  • Deployment: Fast set up, Easy configuration

A now, let’s start to use NAV 2016 and waiting for new features the next year in the same time.

Deploying NAV 2016 on Azure SQL on NAVTechDays

I have already wrote about NAV TechDays 2015. By my opinion, this is the best global NAV technical conference. I didn’t introduce you in my session, because in this moment this topic was still by NDA. But now, we heard about it on WPC in Atlanta this week.

Now I can introduce you in my session about Deploying and Managing Microsoft Dynamics NAV 2016 with Azure SQL Server. You can learn a lot about this awesome feature. I have already introduced in this topic with small article on my blog, but on this session I will present full concept with lot of demos. You can find more about this session here.

But beside my session, there will be a lot of good sessions by other lecturers and you can find all of them here. I think all these sessions will be good reason to register for this conference in Antwerp.

See you there…

NAV 2016 on Azure SQL Server

NAV 2016 database can be deployed on Azure SQL Server. Until yesterday, this news was a secret. I wanted to write about it, but it was by the NDA. Now, this news was published at WPC in Atlanta and we can discuss about it. But, the most of this is still by NDA and I cannot speak everything about this topic.

AzureSQL

This feature will enable the better experience of NAV on Azure and better possibility for migration of NAV implementation to cloud.

Regarding that, I will have session with this topic on NAV Tech Days 2015 in Antwerp, Belgium. If you want to know how to deploy and configure NAV 2016 database on Azure SQL Server, come on this awesome conference and be patient J.

Easy Deployment of the Latest NAV 2015 Version

Today, Microsoft has published new article about easy deployment of the latest version of Microsoft Dynamics NAV on their blog. It is important to know that Microsoft always publishes the latest cumulative update (currently it is NAV 2015 with cumulative update 7). You can use this image to test the newest NAV 2015 version or to use as efficiency demo environment on Microsoft Azure.

I have also wrote about this image in my older posts and I can remind you about them:

I will prepare few more articles about this image, very soon.

Multitenancy on NAV2015 Image on Microsoft Azure

When we speak about NAV on Azure, we expect Multitenancy as main strength. This is because, we expect an easy repeatability. Now, I will explain how to achieve this goal using NAV 2015 image deployed on Microsoft Azure.

We have excellent tolls, but we also have some rules. First, if you already run “O365 Integration pack” and “ClickOnce Deployment pack” scripts, unfortunately you cannot use this tools. You will get message similar as on following picture:

Multi0

You need to have a clean image deployment with running only “Initialize the VM pack” (must run it). Then, you need to run install.ps1 file from C:\DEMO\Multitenancy folder. You can find it, when you click on Enable Repeatability from NAV on Azure Welcome Screen. You can run this PowerShell file using PowerShell ISE.

When you open this script, you have to replace “vmadmin” in path with your user name on all places you can find. You can see one of the examples on following picture:

Multi0-1

You could also rename tenant ID, if you want it. It has name “Default”, by default.

After that, you can save and run your script. When script is finished, you will get URLs file with your new links with tenants.

Multi1

Now, you can use these new links to run your NAV 2015 with tenant. If you want to add new tenant or remove existed, you can do it running Multitenancy Demo Admin Shell from your VM desktop. You can also use it tool to add users to tenant or remove existed from tenant.

Multi2