MicrosoftDocs
Error codes in the article don't match the error codes that end users see in the portal
In the portal, if deletion of an event hub fails, the Summary shown in the activity logs is:
Error code: MetadataDRCannotDeleteWhenAliasPresentConflict
Message: DR config cannot be deleted because replication is in progress. Please failover or break pairing before attempting to delete the DR Config. For more information visit https://aka.ms/eventhubsarmexceptions.
But in the article, the error code is presented as:
Error code: Conflict
In order to see the 'Conflict' error code, an end user would have to go into the JSON details of the activity log and see this:
"statusCode": "Conflict",
"statusMessage": "{\"error\":{\"code\":\"MetadataDRCannotDeleteWhenAliasPresentConflict\",\"message\":\"DR config cannot be deleted because replication is in progress. Please failover or break pairing before attempting to delete the DR Config. For more information visit https://aka.ms/eventhubsarmexceptions.\"}}",
The article should include the actual error that end users see, such as MetadataDRCannotDeleteWhenAliasPresentConflict
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 75eaba1b-1674-8027-6058-53c061560ac8
- Version Independent ID: 9fb91b8f-bde4-09a4-49ad-e67c0c44c265
- Content: Azure Event Hubs - Resource Manager exceptions - Azure Event Hubs
- Content Source: articles/event-hubs/resource-manager-exceptions.md
- Service: event-hubs
- GitHub Login: @spelluru
- Microsoft Alias: spelluru
@kwill-MSFT Thanks for your feedback! We will investigate and update as appropriate.
@spelluru This is a worthy update to make. How can we represent the additional detail under the "Conflict" error code?
@axisc - I guess we will have to add an additional column for "error codes in status message" for "Conflict" status code.
Hi @kwill-MSFT - I will track this as a DevOps work item internally and send you the link. I will work with Ashish and other product team members to update the article. Thanks very much for the feedback.
#please-close