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: support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
+22-23Lines changed: 22 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,39 +7,38 @@ ms.service: azure-monitor
7
7
ms.custom: Configure and Manage Log analytics tables
8
8
---
9
9
10
-
# Troubleshoot Custom Table Creation Errors in Azure
10
+
# Troubleshoot custom table creation errors in Azure
11
11
12
-
When attempting to create a custom table in Azure, users may encounter an error message indicating that properties of undefined cannot be read. This issue can arise due to temporary glitches or misconfigurations. Understanding the root cause and following the appropriate troubleshooting steps can help resolve this problem efficiently.
12
+
Users might receiev an error message that indicates that properties of undefined cannot be read when they try to create a custom table in Microsoft Azure. This issue can occur because of temporary glitches or misconfigurations. This article helps you determine the root cause of the errors and troubleshoot this issue efficiently.
13
13
14
-
## Step-by-Step Instructions to Resolve Custom Table Creation Errors
14
+
## Common issues and solutions
15
15
16
-
1.**Verify JSON File Validity**
17
-
- Ensure that the JSON file used for table creation is correctly formatted and contains all necessary fields.
18
-
- Use tools like *JSONLint* to validate the JSON structure.
16
+
-**Temporary Glitches**: Often, errors are temporary. You might be able to resolve the issue by trying the process again after a short time.
17
+
-**Configuration Errors**: Make sure that all configurations and permissions are correctly set in Azure.
19
18
20
-
2.**Check Azure Logs**
21
-
- Navigate to **Azure Monitor** and access the **Logs** section.
22
-
- Review the ARM logs for any error messages related to the custom table creation process.
19
+
### Instructions to resolve custom table creation errors
23
20
24
-
3.**Reattempt Table Creation**
25
-
- Retry the table creation process using the Azure portal or Azure CLI.
26
-
- If the error persists, consider using a different browser or clearing the browser cache.
21
+
1. Verify JSON file validity:
22
+
1. Make sure that the JSON file that's used for table creation is correctly formatted and contains all the required fields.
23
+
1. Use tools such as *JSONLint* to validate the JSON structure.
27
24
28
-
4.**Collect Diagnostic Information**
29
-
- Gather HAR files and console logs to identify any frontend issues.
30
-
- Use the Azure portal to capture network activity during the table creation attempt.
25
+
2. Check the Azure logs:
26
+
1. Navigate to **Azure Monitor**, and access the **Logs** section.
27
+
1. Review the ARM logs for any error messages that are related to the custom table creation process.
31
28
32
-
5.**Consult Azure Documentation**
33
-
- Refer to the [Azure Custom Tables Documentation](https://learn.microsoft.com/azure/monitoring-and-diagnostics/monitoring-custom-tables) for detailed guidance on creating custom tables.
29
+
3. Try again to create tables:
30
+
1. Run the table creation process again by using the Azure portal or Azure CLI.
31
+
1. If the error persists, consider using a different browser or clearing the browser cache.
34
32
35
-
### Common Issues and Solutions
33
+
4. Collect diagnostic information:
34
+
1. Gather HAR files and console logs to identify any front-end issues.
35
+
1. Use the Azure portal to capture network activity during the table creation process.
36
36
37
-
-**Temporary Glitches**: Often, errors may be temporary. Reattempting the process after a short interval can resolve the issue.
38
-
-**Configuration Errors**: Ensure all configurations and permissions are correctly set in Azure.
37
+
5. Consult Azure documentation: For detailed guidance to create custom tables, see [Azure Custom Tables Documentation](https://learn.microsoft.com/azure/monitoring-and-diagnostics/monitoring-custom-tables).
0 commit comments