The extension encountered an unexpected error and provided no additional details.

Question

I tried to create an Azure Database for MySQL. I used the Advance Create choice. Workload type: for Development and hobby projects. Use Burstable, B1ms, no preference on the Availability Zone. MySQL authentication only. Allow my IP for firewall rules. Reviewed and created. The deployment failed after a few minutes. The dashboard shows the resource, however when I try to display the resource I get the message: The extension encountered an unexpected error and provided no additional details.

• Session ID: a04adfeef4b841af9a6ddb79a91e3757
• Resource ID:Not available
• Extension: HubsExtension
• Content: ResourceMenuBlade
• Error code: --

The screen has the 3 horizontal dots blinking but never loading. I tried to the CLI interface, and I can't find the server or the database anywhere. Yet, If I try to recreate the database it fails because the name exists. I am lost on the next steps as this point, I would like to remove the resource but don't see any way of doing it.

Answer 1

Hello Ralph Schiavone,

Thank you for posting your question in the Microsoft Q&A forum.

Creating an Azure Database for MySQL is generally a straightforward process, but as with any cloud service, issues can arise during deployment. In your case, the deployment failed, and you are encountering an error when trying to access the resource. Additionally, the resource appears to exist in the Azure portal, but you cannot view or manage it, and attempts to recreate it fail because the name is already in use. 

When you attempted to create the Azure Database for MySQL using the "Advanced Create" option, the deployment failed, but the resource still appears in the Azure portal. This could be due to a partial deployment or a failure in the backend services that manage the resource. The error message you received, "The extension encountered an unexpected error and provided no additional details," is a generic error that can occur when there is an issue with the Azure portal's interface or the underlying service.

First, you should verify the status of the deployment. Even though the deployment failed, Azure might still have some information about what went wrong.

Since the Azure portal is not providing useful information, you can use the Azure CLI to check for the existence of the resource.

• If the resource is stuck in a failed state and cannot be deleted through the portal or CLI, you can try to force delete it. This can be done by using the Azure REST API or by opening a support ticket with Microsoft Azure. In your case, the Azure Database for MySQL deployment failed, and the resource is stuck in a state where it cannot be accessed or deleted through the portal or CLI. By checking the deployment status, using the Azure CLI, and potentially force deleting the resource via the Azure REST API, you can resolve the issue. If all else fails, contacting Azure Support is a reliable way to get assistance.

Microsoft documentation you may refer on troubleshooting Azure Database for MySQL deployment issues:

https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors

https://learn.microsoft.com/en-us/azure/mysql/

Please, let me know the response helps answer your question? If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. 🙂