Skip to content

Commit 2d5b3ba

Browse files
authored
Merge branch 'main' into Branch-CI4011
2 parents dec1255 + 76df92b commit 2d5b3ba

181 files changed

Lines changed: 3589 additions & 2355 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: 253 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12880,10 +12880,18 @@
1288012880
"source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-installing-crm-2016-outlook.md",
1288112881
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/error-when-installing-crm-2016-outlook"
1288212882
},
12883+
{
12884+
"source_path": "support/power-platform/dataverse/d365-app-outlook/something-went-wrong-during-sign-in.md",
12885+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/something-went-wrong-during-sign"
12886+
},
12887+
{
12888+
"source_path": "support/power-platform/dataverse/d365-app-outlook/you-do-not-have-required-role-privilege.md",
12889+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-the-required-role-or-privilege-to-complete-this-action-error"
12890+
},
1288312891
{
1288412892
"source_path": "support/power-platform/dataverse/d365-app-outlook/we-cannot-load-this-app.md",
1288512893
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-opening-365-app-outlook"
12886-
},
12894+
},
1288712895
{
1288812896
"source_path": "support/power-platform/dataverse/d365-app-outlook/error-incomingemailrejected-install-dynamics-365-app-outlook.md",
1288912897
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-install-dynamics-365-app-outlook"
@@ -12923,6 +12931,250 @@
1292312931
{
1292412932
"source_path": "support/windows-server/performance/toggle-terminal-services-application-server-mode.md",
1292512933
"redirect_url": "/previous-versions/troubleshoot/windows-server/toggle-terminal-services-application-server-mode"
12934+
},
12935+
{
12936+
"source_path": "support/windows-server/active-directory/cannot-join-computer-to-domain.md",
12937+
"redirect_url": "/previous-versions/troubleshoot/windows-server/cannot-join-computer-to-domain"
12938+
},
12939+
{
12940+
"source_path": "support/windows-server/active-directory/fail-to-join-computer-to-ad-domain.md",
12941+
"redirect_url": "/previous-versions/troubleshoot/windows-server/fail-to-join-computer-to-ad-domain"
12942+
},
12943+
{
12944+
"source_path": "support/power-platform/power-automate/desktop-flows/desktop-application-crashes-ui-automation.md",
12945+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/ui-automation/desktop-application-crashes-ui-automation"
12946+
},
12947+
{
12948+
"source_path": "support/power-platform/power-automate/desktop-flows/cannot-access-java-application-elements.md",
12949+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/ui-automation/cannot-access-java-application-elements"
12950+
},
12951+
{
12952+
"source_path": "support/power-platform/power-automate/desktop-flows/focus-window-action-not-working.md",
12953+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/ui-automation/focus-window-action-not-working"
12954+
},
12955+
{
12956+
"source_path": "support/power-platform/power-automate/desktop-flows/failed-get-ui-element.md",
12957+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/ui-automation/failed-get-ui-element"
12958+
},
12959+
{
12960+
"source_path": "support/power-platform/power-automate/desktop-flows/ui-automation-action-fails-errors.md",
12961+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/ui-automation/ui-automation-action-fails-errors"
12962+
},
12963+
{
12964+
"source_path": "support/power-platform/power-automate/desktop-flows/set-drop-down-list-value-fails.md",
12965+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/ui-automation/set-drop-down-list-value-fails"
12966+
},
12967+
{
12968+
"source_path": "support/power-platform/power-automate/desktop-flows/browser-automation-error-after-chromium-update.md",
12969+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/browser-automation-error-after-chromium-update"
12970+
},
12971+
{
12972+
"source_path": "support/power-platform/power-automate/desktop-flows/cannot-automate-webpage-with-iframes.md",
12973+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/cannot-automate-webpage-with-iframes"
12974+
},
12975+
{
12976+
"source_path": "support/power-platform/power-automate/desktop-flows/web-automation-action-fails-runtime.md",
12977+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/web-automation-action-fails-runtime"
12978+
},
12979+
{
12980+
"source_path": "support/power-platform/power-automate/desktop-flows/automate-save-as-open-upload-dialog-box-web-browser.md",
12981+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/automate-save-as-open-upload-dialog-box-web-browser"
12982+
},
12983+
{
12984+
"source_path": "support/power-platform/power-automate/desktop-flows/failed-to-assume-control-of-edge-chrome-firefox-error.md",
12985+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/failed-to-assume-control-of-edge-chrome-firefox-error"
12986+
},
12987+
{
12988+
"source_path": "support/power-platform/power-automate/desktop-flows/automation-browser-security-update.md",
12989+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/automation-browser-security-update"
12990+
},
12991+
{
12992+
"source_path": "support/power-platform/power-automate/desktop-flows/web-extensions-policies.md",
12993+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/browser-automation/web-extensions-policies"
12994+
},
12995+
{
12996+
"source_path": "support/dynamics-365/sales/action-not-available.md",
12997+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/action-not-available"
12998+
},
12999+
{
13000+
"source_path": "support/dynamics-365/sales/you-cannot-complete-this-action-for-this-component-error-when-importing-solution.md",
13001+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/you-cannot-complete-this-action-for-this-component-error-when-importing-solution"
13002+
},
13003+
{
13004+
"source_path": "support/dynamics-365/sales/cascading-settings-revert-value-solution.md",
13005+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/cascading-settings-revert-value-solution"
13006+
},
13007+
{
13008+
"source_path": "support/dynamics-365/sales/failed-export-business-process.md",
13009+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/failed-export-business-process"
13010+
},
13011+
{
13012+
"source_path": "support/dynamics-365/sales/element-savedquery-has-incomplete-content.md",
13013+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/element-savedquery-has-incomplete-content"
13014+
},
13015+
{
13016+
"source_path": "support/dynamics-365/sales/error-when-importing-attributemap.md",
13017+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/error-when-importing-attributemap"
13018+
},
13019+
{
13020+
"source_path": "support/dynamics-365/sales/only-import-solutions-a-package.md",
13021+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/only-import-solutions-a-package"
13022+
},
13023+
{
13024+
"source_path": "support/dynamics-365/sales/the-file-provided-was-not-uploaded-error.md",
13025+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/the-file-provided-was-not-uploaded-error"
13026+
},
13027+
{
13028+
"source_path": "support/dynamics-365/sales/the-import-of-solution-failed-error-code-8004f016.md",
13029+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/the-import-of-solution-failed-error-code-8004f016"
13030+
},
13031+
{
13032+
"source_path": "support/dynamics-365/sales/the-publisher-name-cannot-be-changed.md",
13033+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/the-publisher-name-cannot-be-changed"
13034+
},
13035+
{
13036+
"source_path": "support/dynamics-365/sales/workflow-creates-large-volume-of-system-jobs-and-logs.md",
13037+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/workflow-creates-large-volume-of-system-jobs-and-logs"
13038+
},
13039+
{
13040+
"source_path": "support/dynamics-365/sales/workflow-designer-fails-load.md",
13041+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/workflow-designer-fails-load"
13042+
},
13043+
{
13044+
"source_path": "support/dynamics-365/sales/workflow-element-has-invalid-child-element.md",
13045+
"redirect_url": "/previous-versions/troubleshoot/dynamics/crm/workflow-element-has-invalid-child-element"
13046+
},
13047+
{
13048+
"source_path": "support/dynamics-365/sales/cannot-import-the-patch-the-solution.md",
13049+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13050+
},
13051+
{
13052+
"source_path": "support/dynamics-365/sales/input-string-was-not-in-a-correct-format-error.md",
13053+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13054+
},
13055+
{
13056+
"source_path": "support/dynamics-365/sales/error-occurs-when-importing-solution.md",
13057+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13058+
},
13059+
{
13060+
"source_path": "support/dynamics-365/sales/error-occurs-when-saving-folder-level-tracking-mapping.md",
13061+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13062+
},
13063+
{
13064+
"source_path": "support/dynamics-365/sales/error-when-selecting-a-solution.md",
13065+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13066+
},
13067+
{
13068+
"source_path": "support/dynamics-365/sales/import-generic-error.md",
13069+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13070+
},
13071+
{
13072+
"source_path": "support/dynamics-365/sales/invalid-display-order-value.md",
13073+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13074+
},
13075+
{
13076+
"source_path": "support/dynamics-365/sales/invalid-file-error-parentheses-80048000.md",
13077+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13078+
},
13079+
{
13080+
"source_path": "support/dynamics-365/sales/sql-error-80044150-when-importing-solution.md",
13081+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13082+
},
13083+
{
13084+
"source_path": "support/dynamics-365/sales/sql-timeout-error-80044151-when-importing-or-exporting-dynamics-365-solution.md",
13085+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13086+
},
13087+
{
13088+
"source_path": "support/dynamics-365/sales/the-solution-package-was-365-online.md",
13089+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13090+
},
13091+
{
13092+
"source_path": "support/dynamics-365/sales/unexpected-error-when-importing-solution.md",
13093+
"redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
13094+
},
13095+
{
13096+
"source_path": "support/dynamics-365/sales/solution-installation-or-removal-failed-error-when-installing-or-removing-solution.md",
13097+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/concurrent-solution-operation-failures"
13098+
},
13099+
{
13100+
"source_path": "support/dynamics-365/sales/the-solution-is-installed-this-system.md",
13101+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/failure-converting-to-managed-solution"
13102+
},
13103+
{
13104+
"source_path": "support/dynamics-365/sales/a-user-disappears-all-eligible-users.md",
13105+
"redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/a-user-disappears-all-eligible-users"
13106+
},
13107+
{
13108+
"source_path": "support/dynamics-365/sales/the-import-file-is-too-large-upload.md",
13109+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/the-import-file-is-too-large-upload"
13110+
},
13111+
{
13112+
"source_path": "support/dynamics-365/sales/an-error-calculating-dependencies.md",
13113+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/an-error-calculating-dependencies"
13114+
},
13115+
{
13116+
"source_path": "support/dynamics-365/sales/error-code-8004f042-occurs.md",
13117+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/error-code-8004f042-occurs"
13118+
},
13119+
{
13120+
"source_path": "support/dynamics-365/sales/error-when-uninstalling-portals-solutions.md",
13121+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/error-when-uninstalling-portals-solutions"
13122+
},
13123+
{
13124+
"source_path": "support/dynamics-365/sales/error-when-you-import-delete-solution.md",
13125+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/error-when-you-import-delete-solution"
13126+
},
13127+
{
13128+
"source_path": "support/dynamics-365/sales/invalidpluginassemblycontent-error-when-importing-solution.md",
13129+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/invalidpluginassemblycontent-error-when-importing-solution"
13130+
},
13131+
{
13132+
"source_path": "support/dynamics-365/sales/my-apps-area-is-missing.md",
13133+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/my-apps-area-is-missing"
13134+
},
13135+
{
13136+
"source_path": "support/dynamics-365/sales/the-import-of-solution-failed-error-when-importing-solution.md",
13137+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/the-import-of-solution-failed-error-when-importing-solution"
13138+
},
13139+
{
13140+
"source_path": "support/dynamics-365/sales/the-solution-file-is-invalid.md",
13141+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/the-solution-file-is-invalid"
13142+
},
13143+
{
13144+
"source_path": "support/dynamics-365/sales/the-solution-is-installed-a-managed-one.md",
13145+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/the-solution-is-installed-a-managed-one"
13146+
},
13147+
{
13148+
"source_path": "support/dynamics-365/sales/this-solution-package-cannot-be-imported.md",
13149+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/this-solution-package-cannot-be-imported"
13150+
},
13151+
{
13152+
"source_path": "support/dynamics-365/sales/unable-import-dynamics-365-solution.md",
13153+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/unable-import-dynamics-365-solution"
13154+
},
13155+
{
13156+
"source_path": "support/dynamics-365/sales/cannot-uninstall-solution-error-when-deleting-solution.md",
13157+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/cannot-uninstall-solution-error-when-deleting-solution"
13158+
},
13159+
{
13160+
"source_path": "support/dynamics-365/sales/assembly-version-error-importing-dynamics-365-solution.md",
13161+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/assembly-version-error-importing-dynamics-365-solution"
13162+
},
13163+
{
13164+
"source_path": "support/dynamics-365/sales/troubleshoot-solution-import-errors-in-dynamics-365.md",
13165+
"redirect_url": "/troubleshoot/power-platform/dataverse/working-with-solutions/troubleshoot-solution-import-errors-in-dynamics-365"
13166+
},
13167+
{
13168+
"source_path": "support/windows-server/active-directory/sync-center-slow-syncing-of-offline-files.md",
13169+
"redirect_url": "/troubleshoot/windows-client/networking/sync-center-slow-syncing-of-offline-files"
13170+
},
13171+
{
13172+
"source_path": "support/windows-server/active-directory/troubleshoot-domain-controller-location-issues.md",
13173+
"redirect_url": "/troubleshoot/windows-server/windows-security/troubleshoot-domain-controller-location-issues"
13174+
},
13175+
{
13176+
"source_path": "support/windows-server/setup-upgrade-and-drivers/repair-or-in-place-upgrade.md",
13177+
"redirect_url": "/windows-server/get-started/perform-in-place-upgrade"
1292613178
}
1292713179
]
1292813180
}

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6299,6 +6299,10 @@
62996299
{
63006300
"source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
63016301
"redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
6302+
},
6303+
{
6304+
"source_path": "azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md",
6305+
"redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes"
63026306
}
63036307
]
63046308
}

support/azure/azure-kubernetes/availability-performance/node-not-ready-then-recovers.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
22
title: Node not ready but then recovers
33
description: Troubleshoot scenarios in which the status of an AKS cluster node is Node Not Ready, but then the node recovers.
4-
ms.date: 12/09/2024
5-
ms.reviewer: rissing, chiragpa, momajed, v-leedennis
4+
ms.date: 2/25/2024
5+
ms.reviewer: rissing, chiragpa, momajed, v-leedennis, novictor
66
ms.service: azure-kubernetes-service
77
#Customer intent: As an Azure Kubernetes user, I want to prevent the Node Not Ready status for nodes that later recover so that I can avoid future errors within an AKS cluster.
88
ms.custom: sap:Node/node pool availability and performance
99
---
1010
# Troubleshoot Node Not Ready failures that are followed by recoveries
1111

12-
This article provides a guide to troubleshoot and resolve "Node Not Ready" issues in Azure Kubernetes Service (AKS) clusters. When a node enters a "Not Ready" state, it can disrupt the application's functionality and cause it to stop responding. Typically, the node recovers automatically after a short period. However, to prevent recurring issues and maintain a stable environment, it's important to understand the underlying causes to be able to implement effective resolutions.
12+
This article provides a guide to troubleshoot and resolve Node Not Ready" issues in Azure Kubernetes Service (AKS) clusters. When a node enters a "NotReady" state, it can disrupt the application's functionality and cause it to stop responding. Typically, the node recovers automatically after a short period. However, to prevent recurring issues and maintain a stable environment, it's important to understand the underlying causes to be able to implement effective resolutions.
1313

1414
## Cause
1515

16-
There are several scenarios that could cause a "Not Ready" state to occur:
16+
There are several scenarios that could cause a "NotReady" state to occur:
1717

1818
- The unavailability of the API server. This causes the readiness probe to fail. This prevents the pod from being attached to the service so that traffic is no longer forwarded to the pod instance.
1919

@@ -24,7 +24,12 @@ There are several scenarios that could cause a "Not Ready" state to occur:
2424

2525
## Resolution
2626

27-
Check the API server availability by running the `kubectl get apiservices` command. Make sure that the readiness probe is correctly configured in the deployment YAML file.
27+
To resolve this issue, follow these steps:
28+
29+
1. Run `kubectl describe node <node-name>` to review detail information about the node's status. Look for any error messages or warnings that might indicate the root cause of the issue.
30+
2. Check the API server availability by running the `kubectl get apiservices` command. Make sure that the readiness probe is correctly configured in the deployment YAML file.
31+
3. Verify the node's network configuration to make sure that there are no connectivity issues.
32+
4. Check the node's resource usage, such as CPU, memory, and disk, to identify potential constraints. For more informations see [Monitor your Kubernetes cluster performance with Container insights](/azure/azure-monitor/containers/container-insights-analyze#view-performance-directly-from-a-cluster)
2833

2934
For further steps, see [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).
3035

support/azure/azure-kubernetes/connectivity/error-from-server-error-dialing-backend-dial-tcp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: 'Error from server: error dialing backend: dial tcp'
33
description: 'Troubleshoot the error dialing backend: dial tcp error that blocks you from using kubectl commands or other tools when you connect to the API server.'
4-
ms.date: 10/21/2024
5-
ms.reviewer: chiragpa, nickoman, v-leedennis, pihe
4+
ms.date: 03/05/2025
5+
ms.reviewer: chiragpa, nickoman, v-leedennis, pihe, mariusbutuc
66
ms.service: azure-kubernetes-service
77
keywords:
88
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the "Error from server: error dialing backend: dial tcp" error so that I can connect to the API server or use the `kubectl logs` command to get logs.

0 commit comments

Comments
 (0)