Skip to content

Commit f7201bd

Browse files
author
Simonx Xu
authored
Merge branch 'main' into Bmoran-0225
2 parents 1fd5343 + 8553983 commit f7201bd

1,500 files changed

Lines changed: 7922 additions & 4465 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.openpublishing.redirection.json

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12763,6 +12763,122 @@
1276312763
{
1276412764
"source_path": "support/mem/configmgr/client-management/cmg-communication-error-403.md",
1276512765
"redirect_url": "/troubleshoot/mem/configmgr/client-management/cmg-communication-error"
12766+
},
12767+
{
12768+
"source_path": "support/dynamics-365/sales/attachments-not-tracked-to-dynamics-365-after-office-365-atp-is-enabled.md",
12769+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/attachments-not-tracked-to-dynamics-365-after-office-365-atp-is-enabled"
12770+
},
12771+
{
12772+
"source_path": "support/dynamics-365/sales/buttons-such-as-track-and-set-regarding-are-missing.md",
12773+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/buttons-such-as-track-and-set-regarding-are-missing"
12774+
},
12775+
{
12776+
"source_path": "support/dynamics-365/sales/cannot-connect-to-exchange-message-when-using-dynamics-365-app-for-outlook.md",
12777+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/cannot-connect-to-exchange-message-when-using-dynamics-365-app-for-outlook"
12778+
},
12779+
{
12780+
"source_path": "support/dynamics-365/sales/dynamics-365-app-for-outlook-is-missing.md",
12781+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/dynamics-365-app-for-outlook-is-missing"
12782+
},
12783+
{
12784+
"source_path": "support/dynamics-365/sales/dynamics-365-app-outlook-did-not-load.md",
12785+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/dynamics-365-app-outlook-did-not-load"
12786+
},
12787+
{
12788+
"source_path": "support/dynamics-365/sales/emails-tracked-by-dynamics-365-app-for-outlook-show-track-pending.md",
12789+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/emails-tracked-by-dynamics-365-app-for-outlook-show-track-pending"
12790+
},
12791+
{
12792+
"source_path": "support/dynamics-365/sales/error-incomingemailrejected-install-dynamics-365-app-outlook.md",
12793+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-incomingemailrejected-install-dynamics-365-app-outlook"
12794+
},
12795+
{
12796+
"source_path": "support/dynamics-365/sales/error-install-dynamics-365-app-outlook.md",
12797+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-install-dynamics-365-app-outlook"
12798+
},
12799+
{
12800+
"source_path": "support/dynamics-365/sales/error-when-accessing-crm-app-outlook.md",
12801+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-accessing-crm-app-outlook"
12802+
},
12803+
{
12804+
"source_path": "support/dynamics-365/sales/error-when-opening-365-app-outlook.md",
12805+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-opening-365-app-outlook"
12806+
},
12807+
{
12808+
"source_path": "support/dynamics-365/sales/error-when-using-365-app-outlook.md",
12809+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-using-365-app-outlook"
12810+
},
12811+
{
12812+
"source_path": "support/dynamics-365/sales/privilege-error-occurs-when-using-dynamics-365-app-for-outlook.md",
12813+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/privilege-error-occurs-when-using-dynamics-365-app-for-outlook"
12814+
},
12815+
{
12816+
"source_path": "support/dynamics-365/sales/the-view-is-not-available-error-when-opening-emails.md",
12817+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/the-view-is-not-available-error-when-opening-emails"
12818+
},
12819+
{
12820+
"source_path": "support/dynamics-365/sales/troubleshoot-item-level-server-side-synchronization-issues.md",
12821+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/troubleshoot-item-level-server-side-synchronization-issues"
12822+
},
12823+
{
12824+
"source_path": "support/dynamics-365/sales/trying-to-access-dynamics-365-app-for-outlook-from-email-do-not-recognize-error.md",
12825+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/trying-to-access-dynamics-365-app-for-outlook-from-email-do-not-recognize-error"
12826+
},
12827+
{
12828+
"source_path": "support/dynamics-365/sales/we-are-unable-to-connect-to-your-dynamics-365-app-for-outlook-error.md",
12829+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/we-are-unable-to-connect-to-your-dynamics-365-app-for-outlook-error"
12830+
},
12831+
{
12832+
"source_path": "support/dynamics-365/sales/you-do-not-have-permission-to-access-this-app-error-when-accessing-dynamics-365-app-for-outlook.md",
12833+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-permission-to-access-this-app-error-when-accessing-dynamics-365-app-for-outlook"
12834+
},
12835+
{
12836+
"source_path": "support/dynamics-365/sales/you-do-not-have-required-role-privilege.md",
12837+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-required-role-privilege"
12838+
},
12839+
{
12840+
"source_path": "support/dynamics-365/sales/you-do-not-have-the-required-role-or-privilege-to-complete-this-action-error.md",
12841+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-the-required-role-or-privilege-to-complete-this-action-error"
12842+
},
12843+
{
12844+
"source_path": "support/windows-server/performance/use-userdump-create-dump-file.md",
12845+
"redirect_url": "/sysinternals/downloads/procdump"
12846+
},
12847+
{
12848+
"source_path": "support/power-platform/dataverse/d365-app-outlook/troubleshoot-dynamics-365-app-outlook.md",
12849+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
12850+
},
12851+
{
12852+
"source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-accessing-crm-app-outlook.md",
12853+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
12854+
},
12855+
{
12856+
"source_path": "support/power-platform/dataverse/d365-app-outlook/new-forms-formatted-incorrectly.md",
12857+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
12858+
},
12859+
{
12860+
"source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-using-365-app-outlook.md",
12861+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
12862+
},
12863+
{
12864+
"source_path": "support/power-platform/dataverse/d365-app-outlook/your-device-is-currently-unsupported.md",
12865+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
12866+
},
12867+
{
12868+
"source_path": "support/power-platform/dataverse/d365-app-outlook/this-organization-has-already-been-configured-error-when-connecting.md",
12869+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
12870+
},
12871+
{
12872+
"source_path": "support/power-platform/dataverse/d365-app-outlook/you-do-not-have-permission-to-access-this-app-error-when-accessing-dynamics-365-app-for-outlook.md",
12873+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
12874+
},
12875+
{
12876+
"source_path": "support/power-platform/dataverse/d365-app-outlook/the-given-key-was-not-present-in-dictionary.md",
12877+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/the-given-key-was-not-present-in-dictionary"
12878+
},
12879+
{
12880+
"source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-installing-crm-2016-outlook.md",
12881+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/error-when-installing-crm-2016-outlook"
1276612882
}
1276712883
]
1276812884
}

support/azure/.openpublishing.redirection.azure.json

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6283,6 +6283,22 @@
62836283
{
62846284
"source_path": "azure-monitor/app-insights/availability/profiler-troubleshooting.md",
62856285
"redirect_url": "/azure/azure-monitor/profiler/profiler-troubleshooting"
6286+
},
6287+
{
6288+
"source_path": "azure-monitor/app-insights/availability/code-optimizations-troubleshooting.md",
6289+
"redirect_url": "/azure/azure-monitor/insights/code-optimizations-troubleshoot"
6290+
},
6291+
{
6292+
"source_path": "azure-monitor/app-insights/debug/snapshot-debugger-troubleshoot.md",
6293+
"redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-troubleshoot"
6294+
},
6295+
{
6296+
"source_path": "azure-kubernetes/error-codes/vhdfilenotfound.md",
6297+
"redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-vhdfilenotfound"
6298+
},
6299+
{
6300+
"source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
6301+
"redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
62866302
}
62876303
]
62886304
}

support/azure/azure-container-instances/connectivity/web-socket-is-closed-or-could-not-be-opened.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Error - Web socket is closed or could not be opened
33
description: Learn how to resolve the (Web socket is closed or could not be opened) error. This error prevents you from connecting to your container from a virtual network.
4-
ms.date: 12/28/2023
4+
ms.date: 02/24/2025
55
author: tysonfms
66
ms.author: tysonfreeman
77
editor: v-jsitser
8-
ms.reviewer: v-leedennis
8+
ms.reviewer: albarqaw, v-weizhu, v-leedennis
99
ms.service: azure-container-instances
1010
ms.custom: sap:Connectivity
1111
#Customer intent: As an Azure administrator, I want to learn how to resolve the "Web socket is closed or could not be opened" error so that I can successfully deploy an image onto a container instance.
@@ -22,10 +22,12 @@ When you try to connect to your container from the Azure portal, you receive the
2222
2323
## Cause
2424

25-
Your firewall blocks access to port 19390. This port is required to connect to Container Instances from the Azure portal when container groups are deployed in virtual networks.
25+
Your firewall or corporate proxy blocks access to port 19390. This port is required to connect to Container Instances from the Azure portal when container groups are deployed in virtual networks.
2626

2727
## Solution
2828

29-
Allow ingress to TCP port 19390 in your firewall. At a minimum, make sure that your firewall gives access to that port for all public client IP addresses that the Azure portal has to connect to.
29+
To resolve this error, allow ingress to TCP port 19390 in your firewall. At a minimum, make sure that your firewall gives access to that port for all public client IP addresses that the Azure portal has to connect to.
30+
31+
In some scenarios where the corporate proxy blocks port 19390, allow this port for corporate proxy, and then verify the traffic by using the **Network** tab in the browser developer tools.
3032

3133
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/connectivity/insufficientsubnetsize-error-advanced-networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: InsufficientSubnetSize error code
33
description: Learn how to fix an InsufficientSubnetSize error that occurs when you deploy an Azure Kubernetes Service (AKS) cluster that uses advanced networking.
4-
ms.date: 11/29/2023
4+
ms.date: 02/20/2025
55
author: jotavar
66
ms.author: jotavar
77
ms.reviewer: chiragpa, nickoman, v-leedennis

support/azure/azure-kubernetes/create-upgrade-delete/429-too-many-requests-errors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 429 Too Many Requests errors
33
description: Troubleshoot why you receive 429 Too Many Requests errors on your Kubernetes clusters.
4-
ms.date: 08/29/2023
4+
ms.date: 02/20/2025
55
ms.reviewer: chiragpa, nickoman, v-leedennis, v-weizhu
66
ms.service: azure-kubernetes-service
77
keywords:

support/azure/azure-kubernetes/create-upgrade-delete/error-code-poddrainfailure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot UpgradeFailed errors due to eviction failures caused by PDBs
33
description: Learn how to troubleshoot UpgradeFailed errors due to eviction failures caused by Pod Disruption Budgets when you try to upgrade an Azure Kubernetes Service cluster.
4-
ms.date: 12/21/2023
4+
ms.date: 02/23/2025
55
editor: v-jsitser
66
ms.reviewer: chiragpa, v-leedennis, v-weizhu
77
ms.service: azure-kubernetes-service

support/azure/azure-kubernetes/error-codes/vhdfilenotfound.md renamed to support/azure/azure-kubernetes/error-codes/vmextensionerror-vhdfilenotfound.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
---
2-
title: ERR_VHD_FILE_NOT_FOUND when creating AKS clusters
3-
description: Learn how to troubleshoot the ERR_VHD_FILE_NOT_FOUND error (65) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
2+
title: VMExtensionError_VHDFileNotFound when creating AKS clusters
3+
description: Learn how to troubleshoot the VMExtensionError_VHDFileNotFound error (65) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
44
ms.date: 10/14/2024
55
editor: v-jsitser
66
ms.reviewer: axelg, chiragpa, v-leedennis
77
ms.service: azure-kubernetes-service
8-
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (or error code OutboundConnFailVMExtensionError, error number 50 - or error code ERR_K8S_API_SERVER_CONN_FAIL, error number 51) so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
8+
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the VMExtensionError_VHDFileNotFound error code (or error code OutboundConnFailVMExtensionError, error number 50 - or error code ERR_K8S_API_SERVER_CONN_FAIL, error number 51) so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
99
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
1010
---
11-
# ERR_VHD_FILE_NOT_FOUND error code (65) when deploying an AKS cluster
11+
# VMExtensionError_VHDFileNotFound error code (65) when deploying an AKS cluster
1212

13-
This article discusses how to identify and resolve the `ERR_VHD_FILE_NOT_FOUND` error code (error code number 65) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
13+
This article discusses how to identify and resolve the `VMExtensionError_VHDFileNotFound` error code (error code number 65) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
1414

1515
## Symptoms
1616

support/azure/azure-kubernetes/toc.yml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -366,7 +366,8 @@
366366
href: error-codes/vmextensionerror-k8sapiserverconnfail.md
367367
- name: VMExtensionError_K8SAPIServerDNSLookupFail error
368368
href: error-codes/vmextensionerror-k8sapiserverdnslookupfail.md
369+
- name: VMExtensionError_VHDFileNotFound error
370+
href: error-codes/vmextensionerror-vhdfilenotfound.md
369371
- name: UnsatisfiablePDB error
370372
href: error-codes/unsatisfiablepdb-error.md
371-
- name: ERR_VHD_FILE_NOT_FOUND error
372-
href: error-codes/vhdfilenotfound.md
373+

support/azure/azure-monitor/app-insights/availability/code-optimizations-troubleshooting.md

Lines changed: 0 additions & 54 deletions
This file was deleted.

0 commit comments

Comments
 (0)