You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/troubleshooting/error-invalid-template.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Invalid template errors
3
3
description: Describes how to resolve invalid template errors when deploying Bicep files or Azure Resource Manager templates (ARM templates).
4
4
ms.topic: troubleshooting
5
-
ms.date: 12/20/2021
5
+
ms.date: 09/12/2022
6
6
---
7
7
8
8
# Resolve errors for invalid template
@@ -26,7 +26,7 @@ This error can result from several different types of errors. They usually invol
26
26
27
27
<aid="syntax-error"></a>
28
28
29
-
## Solution 1 - syntax error
29
+
## Solution 1: Syntax error
30
30
31
31
If you receive an error message that indicates the template failed validation, you may have a syntax problem in your template.
32
32
@@ -56,13 +56,13 @@ When you receive this type of error, review the expression's syntax. To identify
56
56
57
57
<aid="incorrect-segment-lengths"></a>
58
58
59
-
## Solution 2 - incorrect segment lengths
59
+
## Solution 2: Incorrect segment lengths
60
60
61
61
Another invalid template error occurs when the resource name isn't in the correct format. To resolve that error, see [Resolve errors for name and type mismatch](error-invalid-name-segments.md).
62
62
63
63
<aid="parameter-not-valid"></a>
64
64
65
-
## Solution 3 - parameter isn't valid
65
+
## Solution 3: Parameter isn't valid
66
66
67
67
You can specify a parameter's allowed values in a template. During deployment, if you provide a value that isn't an allowed value, you receive a message similar to the following error:
68
68
@@ -77,13 +77,13 @@ Check the template for the parameter's allowed values, and use an allowed value
77
77
78
78
<aid="too-many-resource-groups"></a>
79
79
80
-
## Solution 4 - too many target resource groups
80
+
## Solution 4: Too many target resource groups
81
81
82
82
You may see this error in earlier deployments because you were limited to five target resource groups in a single deployment. In May 2020, that limit was increased to 800 resource groups. For more information, see how to deploy to multiple resource groups for [Bicep](../bicep/deploy-to-resource-group.md#deploy-to-multiple-resource-groups) or [ARM templates](../templates/deploy-to-resource-group.md#deploy-to-multiple-resource-groups).
83
83
84
84
<aid="circular-dependency"></a>
85
85
86
-
## Solution 5 - circular dependency detected
86
+
## Solution 5: Circular dependency detected
87
87
88
88
You receive this error when resources depend on each other in a way that prevents the deployment from starting. A combination of interdependencies makes two or more resource wait for other resources that are also waiting. For example, resource1 depends on resource3, resource2 depends on resource1, and resource3 depends on resource2. You can usually solve this problem by removing unnecessary dependencies.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/troubleshooting/error-job-size-exceeded.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
2
title: Job size exceeded error
3
-
description: Describes how to troubleshoot errors when job size or template are too large for deployments using a Bicep file or Azure Resource Manager template (ARM template).
3
+
description: Describes how to troubleshoot errors for job size exceeded or if the template is too large for deployments using a Bicep file or Azure Resource Manager template (ARM template).
4
4
ms.topic: troubleshooting
5
-
ms.date: 12/20/2021
5
+
ms.date: 09/12/2022
6
6
---
7
7
8
8
# Resolve errors for job size exceeded
9
9
10
-
This article describes how to resolve the `JobSizeExceededException` and `DeploymentJobSizeExceededException` errors. The errors can occur when you deploy a Bicep file or Azure Resource Manager template (ARM template).
10
+
This article describes how to resolve the `JobSizeExceededException` and `DeploymentJobSizeExceededException` errors. The job size exceeded errors can occur when you deploy a Bicep file or Azure Resource Manager template (ARM template).
11
11
12
12
## Symptom
13
13
@@ -29,7 +29,7 @@ Other template limits are:
29
29
- 64 output values
30
30
- 24,576 characters in a template expression
31
31
32
-
## Solution 1 - use dependencies carefully
32
+
## Solution 1: Use dependencies carefully
33
33
34
34
# [Bicep](#tab/bicep)
35
35
@@ -53,7 +53,7 @@ dependsOn: [
53
53
54
54
---
55
55
56
-
## Solution 2 - simplify template
56
+
## Solution 2: Simplify template
57
57
58
58
# [Bicep](#tab/bicep)
59
59
@@ -70,7 +70,7 @@ You can set other resources as dependent on the linked template, and [get values
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/troubleshooting/error-not-found.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
title: Resource not found errors
3
3
description: Describes how to resolve errors when a resource can't be found. The error might occur when you deploy a Bicep file or Azure Resource Manager template, or when doing management tasks.
4
4
ms.topic: troubleshooting
5
-
ms.date: 11/30/2021
5
+
ms.date: 09/12/2022
6
6
ms.custom: devx-track-azurepowershell
7
7
---
8
8
9
-
# Resolve Resource Not Found errors
9
+
# Resolve errors for resource not found
10
10
11
11
This article describes the error you see when a resource can't be found during an operation. Typically, you see this error when deploying resources with a Bicep file or Azure Resource Manager template (ARM template). You also see this error when doing management tasks and Azure Resource Manager can't find the required resource. For example, if you try to add tags to a resource that doesn't exist, you receive this error.
12
12
@@ -31,7 +31,7 @@ group {resource group name} was not found.
31
31
32
32
Resource Manager needs to retrieve the properties for a resource, but can't find the resource in your subscription.
33
33
34
-
## Solution 1 - Check resource properties
34
+
## Solution 1: Check resource properties
35
35
36
36
When you receive this error while doing a management task, check the values you provided for the resource. The three values to check are:
37
37
@@ -43,7 +43,7 @@ If you're using PowerShell or Azure CLI, check that you're running commands in t
43
43
44
44
If you can't verify the properties, sign in to the [Microsoft Azure portal](https://portal.azure.com). Find the resource you're trying to use and examine the resource name, resource group, and subscription.
45
45
46
-
## Solution 2 - Set Dependencies
46
+
## Solution 2: Set dependencies
47
47
48
48
If you get this error when deploying a template, you may need to add a dependency. Resource Manager optimizes deployments by creating resources in parallel, when possible.
49
49
@@ -56,13 +56,13 @@ Use an [implicit dependency](../bicep/resource-dependencies.md#implicit-dependen
56
56
For example, the web app's `serverFarmId` property uses `servicePlan.id` to create a dependency on the App Service plan.
If one resource must be deployed after another resource, you need to use the [dependsOn](../templates/resource-dependency.md#dependson) element in your template.
76
+
If a resource must be deployed after another resource, use the [dependsOn](../templates/resource-dependency.md#dependson) element in your template.
77
77
78
78
```json
79
79
{
80
80
"type": "Microsoft.Web/sites",
81
-
"apiVersion": "2021-02-01",
81
+
"apiVersion": "2022-03-01",
82
82
"dependsOn": [
83
83
"[variables('hostingPlanName')]"
84
84
],
@@ -107,15 +107,15 @@ When you see dependency problems, you need to gain insight into the order of res
107
107
108
108
:::image type="content" source="media/error-not-found/select-deployment-events.png" alt-text="Screenshot that highlights the link to a deployment's related events.":::
109
109
110
-
1. Examine the sequence of events for each resource. Pay attention to the status of each operation and it's time stamp. For example, the following image shows three storage accounts that deployed in parallel. Notice that the three storage accounts are started at the same time.
110
+
1. Examine the sequence of events for each resource. Pay attention to the status of each operation and it's time stamp. For example, the following image shows three storage accounts that deployed in parallel. Notice that the three storage account deployments started at the same time.
111
111
112
112
:::image type="content" source="media/error-not-found/deployment-events-parallel.png" alt-text="Screenshot of activity log for resources deployed in parallel.":::
113
113
114
114
The next image shows three storage accounts that aren't deployed in parallel. The second storage account depends on the first storage account, and the third storage account depends on the second storage account. The first storage account is labeled **Started**, **Accepted**, and **Succeeded** before the next is started.
115
115
116
116
:::image type="content" source="media/error-not-found/deployment-events-sequence.png" alt-text="Screenshot of activity log for resources deployed in sequential order.":::
117
117
118
-
## Solution 3 - Get external resource
118
+
## Solution 3: Get external resource
119
119
120
120
# [Bicep](#tab/bicep)
121
121
@@ -124,12 +124,12 @@ Bicep uses the symbolic name to create an [implicit dependency](../bicep/resourc
124
124
In this example, a web app is deployed that uses an existing App Service plan from another resource group.
When deploying a template, look for expressions that use the [reference](../templates/template-functions-resource.md#reference) or [listKeys](../templates/template-functions-resource.md#listkeys) functions. The values you provide vary based on whether the resource is in the same template, resource group, and subscription. Check that you're providing the required parameter values for your scenario. If the resource is in a different resource group, provide the full resource ID. For example, to reference a storage account in another resource group, use:
219
+
When you deploy a template, look for expressions that use the [reference](../templates/template-functions-resource.md#reference) or [listKeys](../templates/template-functions-resource.md#listkeys) functions. The values you provide vary based on whether the resource is in the same template, resource group, and subscription. Check that you're providing the required parameter values for your scenario. If the resource is in a different resource group, provide the full resource ID. For example, to reference a storage account in another resource group, use:
When you delete a resource, there might be a short amount of time when the resource appears in the portal but isn't available. If you select the resource, you'll get an error that the resource is **Not found**.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/troubleshooting/error-parent-resource.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Parent resource errors
3
3
description: Describes how to resolve errors when you deploy a resource that's dependent on a parent resource in a Bicep file or Azure Resource Manager template (ARM template).
4
4
ms.topic: troubleshooting
5
-
ms.date: 12/20/2021
5
+
ms.date: 09/12/2022
6
6
---
7
7
8
8
# Resolve errors for parent resources
@@ -25,7 +25,7 @@ When one resource is a child to another resource, the parent resource must exist
@@ -50,7 +50,7 @@ If you deploy the server and the database in the same template, but don't specif
50
50
51
51
If the parent resource already exists and isn't deployed in the same template, you get the `ParentResourceNotFound` error when Resource Manager can't associate the child resource with a parent. This error might happen when the child resource isn't in the correct format. Or if the child resource is deployed to a resource group that's different than the resource group for parent resource.
52
52
53
-
## Solution 1 - deployed in same template
53
+
## Solution 1: Deployed in same template
54
54
55
55
To resolve this error when parent and child resources are deployed in the same template, use a dependency.
56
56
@@ -59,7 +59,7 @@ To resolve this error when parent and child resources are deployed in the same t
59
59
This example uses a nested child resource within the parent resource and that creates the dependency. The child gets the resource type and API version from the parent resource.
@@ -87,7 +87,7 @@ For more information about `dependsOn`, see [Define the order for deploying reso
87
87
88
88
---
89
89
90
-
## Solution 2 - deployed in different templates
90
+
## Solution 2: Deployed in different templates
91
91
92
92
To resolve this error when the parent resource was deployed in a different template, don't set a dependency. Instead, deploy the child to the same resource group and provide the name of the parent resource.
0 commit comments