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-arc/resource-bridge/troubleshoot-resource-bridge.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,7 +247,7 @@ To install Azure Arc resource bridge on an Azure Stack HCI cluster, `az arcappli
247
247
248
248
## Azure Arc-enabled VMware VCenter issues
249
249
250
-
### errorCode: CreateConfigKvaCustomerError, errorResponse: error getting the vsphere sdk client
250
+
### errorResponse: error getting the vsphere sdk client
251
251
252
252
For errors with errorCode `CreateConfigKvaCustomerError` and errorResponse `error getting the vsphere sdk client`, these errors occur when your deployment machine is trying to establish a TCP connection to your vCenter address but encounters a problem. You receive this errorCode and errorResponse if your vCenter address is incorrect (403 or 404 error) or if there's a network/proxy/firewall configuration blocking it (connection attempt failed). If you enter your vCenter address as a hostname and receive the error `no such host`, then your deployment machine isn't able to resolve the vCenter hostname via the client DNS. You may receive an error if the deployment machine is able to resolve the vCenter hostname but the deployment machine can't reach the IP address it received from DNS. You may receive an error if the endpoint returned by DNS isn't your vCenter address, or if the traffic was intercepted by proxy. Finally, you may get an error if your deployment machine is able to communicate with your vCenter address, but the username or password is incorrect.
253
253
@@ -302,6 +302,15 @@ To resolve this issue, manually delete the existing template. Then run [`az arca
302
302
303
303
When deploying Arc resource bridge on VMware, you specify the folder in which the template and VM are created. The selected folder must be a VM and template folder type. Other types of folder, such as storage folders, network folders, or host and cluster folders, can't be used for the resource bridge deployment.
304
304
305
+
### Cannot retrieve resource
306
+
307
+
When Arc resource bridge is deployed, you specify where the appliance VM will be deployed. The appliance VM can't be moved from that location path. If you want to change the path, you need to delete and redeploy the Arc resource bridge. When upgrading Arc resource bridge, if you moved the appliance VM, you may hit an error similar to:
You can either move the appliance VM back to its original location and ensure RBAC credentials are updated for the location change or delete and redeploy the Arc resource bridge.
313
+
305
314
### Insufficient permissions
306
315
307
316
When deploying the resource bridge on VMware vCenter, you might get an error saying that you have insufficient permission. To resolve this issue, make sure that the user account being used to deploy the resource bridge has all of the following privileges in VMware vCenter and then try again.
@@ -408,6 +417,6 @@ When deploying the resource bridge on VMware vCenter, you might get an error say
408
417
If you don't see your problem here or you can't resolve your issue, try one of the following channels for support:
409
418
410
419
- Get answers from Azure experts through [Microsoft Q&A](/answers/topics/azure-arc.html).
411
-
- Connect with [@AzureSupport](https://x.com/azuresupport), the official Microsoft Azure account for improving customer experience. Azure Support connects the Azure community to answers, support, and experts.
420
+
- Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience. Azure Support connects the Azure community to answers, support, and experts.
412
421
-[Open an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md).
0 commit comments