Troubleshoot Manufacturing data solutions (preview)
Important
Some or all of this functionality is available as part of a preview release. The content and the functionality are subject to change.
This troubleshooting guide is designed to help you identify and resolve common issues that can arise during and after the deployment of Manufacturing data solutions service.
Debug failed deployment
You can check if your deployment succeeded or not by looking at status of the resource.
If the status of your Manufacturing data solutions resource is Failed
, go to Managed Resource group for that resource using the following naming convention MDS-{your-deployment-name}-MRG-{UniqueID}
. You can also refer to Resource JSON details to fetch the details of Managed Resource group.
Note
The minimum access required is the Reader
role for the specified Managed Resource group.
Go to the specified resource group, select Deployments tab from the left-hand menu, and review any deployment errors that occurred.
If you receive a BadRequest
error code, it indicates that the deployment values you sent don't match the expected values by Resource Manager. Check the inner message for more details.
Deployment can fail due to various reasons as listed in the following table:
Error Code | Meaning | Mitigation |
---|---|---|
Failed to assign role to UMI: <your-UMI> . Check if UMI has the required roles to assign roles. |
Missing permissions for the User Managed Identity used | If the User Assigned Managed Identity doesn't have the Owner role assigned at the subscription scope, the role assignments don't work and causes the deployment to fail. Also, User managed identity’s service principal need to have Owner role assigned to itself. |
DeploymentQuotaExceeded | Insufficient quotas and limits for Azure services | Azure resources have certain quotas and limits for various Azure services like Azure Data Explorer, OpenAI, etc. Make sure you have enough quota for all the resources before starting the Manufacturing data solutions deployment. |
NoRegisteredProviderFound/ SubscriptionNotRegistered/ MissingSubscriptionRegistration | Required Resource Providers aren't registered | One of the prerequisites for the deployment is that you must register the Resource Providers listed in the deployment guide. Ensure that all the resource providers are properly registered before starting the deployment. |
Only one User Assigned Managed Identity is supported | You can’t add multiple User Managed Identities in Manufacturing data solutions | For more information, see common Azure Resource Manager (ARM) deployment errors. |
Note
For any other intermittent issues, try to redeploy the solution once. If problem persists, you need to get in touch with Microsoft Support Team.