App Service Installation Error When Installing on ASDK 1805

Question

Just started to install App Service 1.2 on our ASDK 1805 servers.  All the pre-requisites are configured.  I am at the step on the installer where it is asking us to provide the SQL information.  My SQL VM is in it own vnet, the file server is in its own vnet as well.   The SQL server is SQL 2014.   

I get the following error:

A connection was successfully established with the server, but then an error occurred during the login process.  (provider:  SSL Provider, error: 0 - The client and server cannot communicate, because they do not possess a common algorithm.)

I have double checked the creds and they are good.

---

Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

Answer 1

It sounds like a possible TLS issue?  Is SQL 2014 still supported SQL version for the App Service 1.2 and Azure Stack version 1805?

---

Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

Answer 2

Just FYI, I just installed a new SQL 2016 VM for testing and it connected just fine.  Is there something that needs to be done if we need to use SQL 2014 or is that not supported anymore?

---

Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

Answer 3

Issue fixed.  Wasn't using Sp2 for SQL 2014.  

---

Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

Answer 4

Hello Kristopher,

SQL Server 2014 is compatible with 1805 & App Service 1.2.

 

A couple of questions:

Is App Services 1.2 being deployed on a ASDK or ASIS?

  

Is the SQL server Virtual network set to ‘Public’ or ‘Private’?

 

Is authentication set to ‘SQL’ or ‘Windows’?

 

Are you connecting using IP address or FQDN?

   

What ports do you have enabled in your SQL server ‘Network Security Group’?

Make sure (ports/protocals) 1433, 1434, 3389 ,80, 443 and SMB 445 are enabled.

    

Note: App Service can only be deployed into the Default Provider Subscription at this time. In a future update App Service will deploy into the new Metering Subscription introduced in Azure Stack 1804 and all existing deployments will be migrated to this new subscription also.

 

Workers are unable to reach file server when App Service is deployed in an existing virtual network and the file server is only available on the private network.

If you chose to deploy into an existing virtual network and an internal IP address to connect to your file server, you must add an outbound security rule, enabling SMB traffic between the worker subnet and the file server. To do this, go to the WorkersNsg in the Admin Portal and add an outbound security rule with the following properties:

• Source: Any
• Source port range: *
• Destination: IP Addresses
• Destination IP address range: Range of IPs for your file server
• Destination port range: 445
• Protocol: TCP
• Action: Allow
• Priority: 700
• Name: Outbound_Allow_SMB445

     

Let us know how it goes.

 

We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

If you continue experience any issues with ASDK release, feel free to contact us.

       

 Thanks, 

---

Gary Gallanes

Answer 5

Yes the minimum supported version is 

https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-app-service-before-you-get-started#prepare-the-sql-server-instance

For Azure Stack Development Kit deployments, you can use SQL Server Express 2014 SP2 or later.