Sitecore vanilla installation on Azure PaaS created blank azure resources

We are installing Sitecore 9.2 on Azure PaaS using the Sitecore ARM templates. We have placed the WDP packages, XP folder and other parameter JSONs on Azure blob storage.

The installation completed successfully and it created all the Azure resources like App service, DBs etc but all those resources are blank. We are not seeing any Sitecore OOTB files under the App services and even the databases do not have any tables etc.

Also in the Azure portal we opened the resource group and clicked the “Deployments” option under Settings on the left side of the page and the deployments status was “Succeeded”.

While scanning the logs we saw the exceptions below in the logs:

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"InvalidTemplate","message":"Deployment template validation failed: 'The value for the template parameter 'setCompatibilityLevelMsDeployPackageUrl' at line '383' and column '47' is not provided. Please see https://aka.ms/resource-manager-parameter-files for usage details.'."}]}

The error above indicates that the setCompatibilityLevelMsDeployPackageUrl parameter is missing. Upon checking your azuredeploy.json we noticed that it was missing.

Please see the quickstart azuredeploy.json for the topology you are deploying(version 9.2 topologies can be found here: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates/tree/master/Sitecore%209.2.0) and you can ctrl+f search for “setCompatibilityLevelMsDeployPackageUrl” to see this parameter in the azuredeploy.json.

This change seems to be introduced in December of 2019, please note the commit here fixing this compatibility issue for all versions: https://github.com/Sitecore/Sitecore-Azure-Quickstart-Templates/commit/b37ae9e57bce566de6b8ef127722ebad17c76521

If you face similar issue please validate your azuredeploy.json and add setCompatibilityLevelMsDeployPackageUrl if it is missing.

Hope this helps!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Website Powered by WordPress.com.

Up ↑

%d bloggers like this: