Skip to main content
Embedsy logo
vb_leaf

Troubleshooting an Azure Marketplace installation

When you install Embedsy from Azure Marketplace, Azure deploys it into your own subscription as a managed application. The installation form checks for the most common problems before you select Create. If a deployment still fails, this page explains how to find out why and how to install again.

Installing with the Embedsy installer instead? See Troubleshooting the Embedsy Portal installation.

Before you select Create

The form checks your subscription while you fill it in:

  • A red message says your subscription can't create Azure SQL servers in the region. Under Database region, select Choose a different region and pick a region close to the app region. The app stays in the region you chose; only the database moves.
  • A name is already taken. The App Service, SQL server and storage account names must be unique across all of Azure. Enter a different name.

If the deployment fails

Don't use Redeploy. It opens a generic Azure form instead of the Embedsy one, so you can't change the region, and some of the values you entered may not carry over.

  1. Find the error. In the Azure portal, open the resource group you installed into, then Deployments, and open the failed deployment. The error details say which resource failed and why. The most common errors are listed below.
  2. Delete the failed Embedsy application. Open it under Managed applications and select Delete. This also removes the resources that were created before the failure, so nothing is left behind.
  3. Install again from Azure Marketplace, with the change that fixes the error.

Common errors

SQL server creation is not allowed in this region

The error mentions RegionDoesNotAllowProvisioning, "Provisioning is restricted in this region" or "Your subscription does not have access to create a server in the selected region". Azure limits which subscriptions can create SQL servers in some regions. Install again and, under Database region, choose a different region. If you need the database in that exact region, ask Microsoft to enable it: in the Azure portal, create a support request of the type Service and subscription limits (quotas), with quota type SQL Database and Region access. See Resolve capacity errors with Azure SQL Database.

A name is not available

Someone else created a resource with the same name between filling in the form and the deployment. Install again with a different App Service, SQL server or storage account name.

Not enough App Service quota

The error mentions App Service quota, for example "Operation cannot be completed without additional quota". Some subscriptions, such as trial or sponsored ones, have no quota for the Basic App Service plan Embedsy uses. Request more quota for App Service in that region through a Service and subscription limits (quotas) support request, or install again in a different region.

Still stuck?

Contact us with the error message, the region you chose and roughly when the deployment ran, and we'll help you finish the installation.

Was this article helpful?