Skip to content

Commit 47f80ba

Browse files
Update Troubleshoot doc - 9
1 parent 1604eae commit 47f80ba

1 file changed

Lines changed: 4 additions & 18 deletions

File tree

docs/TroubleShootingSteps.md

Lines changed: 4 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -101,24 +101,10 @@ Use these as quick reference guides to unblock your deployments.
101101

102102
### Resource State & Provisioning
103103

104-
<details>
105-
<summary><b>AccountProvisioningStateInvalid</b></summary>
106-
107-
- The AccountProvisioningStateInvalid error occurs when you try to use resources while they are still in the Accepted provisioning state.
108-
- This means the deployment has not yet fully completed.
109-
- To avoid this error, wait until the provisioning state changes to Succeeded.
110-
- Only use the resources once the deployment is fully completed.
111-
</details>
112-
113-
<details><summary><b>BadRequest - DatabaseAccount is in a failed provisioning state because the previous attempt to create it was not successful</b></summary>
114-
115-
- This error occurs when a user attempts to redeploy a resource that previously failed to provision.
116-
117-
- To resolve the issue, delete the failed deployment first, then start a new deployment.
118-
119-
- For guidance on deleting a resource from a Resource Group, refer to the following link: [Delete an Azure Cosmos DB account](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/manage-with-powershell#delete-account:~:text=%3A%24enableMultiMaster-,Delete%20an%20Azure%20Cosmos%20DB%20account,-This%20command%20deletes)
120-
121-
</details>
104+
| Issue/Error Code | Description | Steps to Resolve |
105+
|-----------------|-------------|------------------|
106+
| **AccountProvisioningStateInvalid** | | - The AccountProvisioningStateInvalid error occurs when you try to use resources while they are still in the Accepted provisioning state<br>- This means the deployment has not yet fully completed<br>- To avoid this error, wait until the provisioning state changes to Succeeded<br>- Only use the resources once the deployment is fully completed |
107+
| **BadRequest - DatabaseAccount is in a failed provisioning state because the previous attempt to create it was not successful** | | - This error occurs when a user attempts to redeploy a resource that previously failed to provision<br>- To resolve the issue, delete the failed deployment first, then start a new deployment<br>- For guidance on deleting a resource from a Resource Group, refer to the following link: [Delete an Azure Cosmos DB account](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/manage-with-powershell#delete-account:~:text=%3A%24enableMultiMaster-,Delete%20an%20Azure%20Cosmos%20DB%20account,-This%20command%20deletes) |
122108

123109
---------------------------------
124110

0 commit comments

Comments
 (0)