Sitecore Azure Web App deployment issues

  • Description

    New Sitecore XP deployments to Azure Web Apps may fail due to the change of the Azure SQL default compatibility level.

    Azure SQL Database default compatibility level for the newly created databases has been changed to 140. Databases created prior to this change are not affected and are maintaining their current compatibility level. More information about the change can be found here.

    The article will be updated when new circumstances revealed to reflect the current state of the issue.

  • Current Status

    Sitecore is working closely with Microsoft to find a solution. For any additional questions, please open a ticket on the Sitecore Support Portal.

  • Issue Indication

    The following error appears during the deployment process:

    The resource operation completed with terminal provisioning state 
    .............................................................................................................................
    AppGallery Deploy Failed: 'Microsoft.Web.Deployment.DeploymentDetailedClientServerException: 
    Could not deploy package. Unable to connect to master or target server '<databaseName>'. 
    You must have a user with the same password in master or target server '<databaseName>'.
    .............................................................................................................................
    Microsoft.SqlServer.Dac.DacServicesException: Could not deploy package.
    Microsoft.Data.Tools.Schema.Sql.Deployment.DeploymentFailedException: 
    Unable to connect to master or target server '<databaseName>'. 
    You must have a user with the same password in master or target server '<databaseName>'.

  • Use regions that are not affected by the problem. The default compatibility level is equal to 130 in the following regions:

    • Japan West
    • West US
    • North Europe
    • South Central US
    • South East Asia
    • Australia East
  • Deploy via Sitecore Azure Toolkit following the steps below:

    1. Initiate a deployment.
      Note: the deployment will fail, but resources are created.
    2. Connect to each database via Microsoft SQL Server Management Studio and change the compatibility level from 140 to 130. Use the following query to update the compatibility level:
      ALTER DATABASE <database name> SET COMPATIBILITY_LEVEL = 130
    3. Re-run the deployment with the same parameters.

    Sitecore Corp. would like to give credit to Mark Vallins for the discovery of this workaround.

Applies to:

Azure Toolkit 1+, Managed Cloud 1+

September 19, 2017
October 03, 2017

Keywords: 

  • Azure