Troubleshoot Azure Resource Manager issues on an Azure Stack Edge device

APPLIES TO: Azure Stack Edge Pro - GPUAzure Stack Edge Pro 2Azure Stack Edge Pro RAzure Stack Edge Mini R                  

This article describes how to troubleshoot issues with Azure Resource Manager that may interfere with management of resources on your Azure Stack Edge device. Azure Resource Manager provides a management layer that enables you to create, update, and delete resources in your Azure account.

Azure Resource Manager configuration errors

The following errors may indicate an issue with your Azure Resource Manager configuration.

Issue / Errors	Resolution
General issues	Verify that the device is configured properly. Verify that the client is configured properly.
Add-AzureRmEnvironment: An error occurred while sending the request. At line:1 char:1 + Add-AzureRmEnvironment -Name Az3 -ARMEndpoint "https://management.dbe ...	Your device isn't reachable or isn't configured properly. Verify that the device and the client are configured correctly. For guidance, see the General issues row in this table.
Service returned error. Check InnerException for more details: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.	There was an error in the creation and installation of the certificate on your device. For more information, see Create and install certificates.
Operation returned an invalid status code 'ServiceUnavailable' Response status code does not indicate success: 503 (Service Unavailable).	This error could be the result of any of these conditions: ArmStsPool is in stopped state. Either Azure Resource Manager is down or the website for the Security Token Service is down. The Azure Resource Manager cluster resource is down. Restarting the device may fix the issue. To debug further, collect a Support package.
AADSTS50126: Invalid username or password. Trace ID: 29317da9-52fc-4ba0-9778-446ae5625e5a Correlation ID: 1b9752c4-8cbf-4304-a714-8a16527410f4 Timestamp: 2019-11-15 09:21:57Z: The remote server returned an error: (400) Bad Request. At line:1 char:1	This error could be the result of any of these conditions: For an invalid username and password, make sure that you have reset the Azure Storage Manager password from the Azure portal, and then use the correct password. For an invalid tenant ID, make sure the tenant ID is set to c0257de7-538f-415c-993a-1b87a031879d
connect-AzureRmAccount: AADSTS90056: The resource is disabled or does not exist. Check your app's code to ensure that you have specified the exact resource URL for the resource you are trying to access. Trace ID: e19bdbc9-5dc8-4a74-85c3-ac6abdfda115 Correlation ID: 75c8ef5a-830e-48b5-b039-595a96488ff9 Timestamp: 2019-11-18 07:00:51Z: The remote server returned an error: (400) Bad	The Azure Resource Manager endpoints used in the Add-AzureRmEnvironment command are incorrect. To find the Azure Resource Manager endpoints, check Device endpoints on the Device page of your device's local web UI. For PowerShell instructions, see Set Azure Resource Manager environment.
Unable to get endpoints from the cloud. Ensure you have network connection. Error detail: HTTPSConnectionPool(host='management.dbg-of4k6suvm.microsoftdatabox.com', port=30005): Max retries exceeded with url: /metadata/endpoints?api-version=2015-01-01 (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')],)",),))	This error appears mostly in a Mac or Linux environment. The error occurs because a PEM format certificate wasn't added to the Python certificate store.

Troubleshoot general issues with Azure Resource Manager

For general issues with Azure Resource Manager, make sure that your device and the client are configured properly. For end-to-end procedures, see Connect to Azure Resource Manager on your Azure Stack Edge Pro GPU device.

Verify the device is configured properly

1. From the local UI, verify that the device network is configured correctly.

2. Verify that certificates are updated for all the endpoints.

3. Get the Azure Resource Manager management and login endpoint from the Device page in local UI.

4. Verify that the device is activated and registered in Azure.

Verify the client is configured properly

1. Validate that the correct PowerShell version is installed.

2. Validate that the correct PowerShell modules are installed.

3. Validate that Azure Resource Manager and login endpoints are reachable. You can try to ping the endpoints. For example:

   ping management.28bmdw2-bb9.microsoftdatabox.com ping login.28bmdw2-bb9.microsoftdatabox.com

   If they aren't reachable, add DNS / host file entries.

4. Validate that client certificates are installed.

5. If you're using PowerShell, enable the debug preference to see detailed messages by running this PowerShell command:

   $debugpreference = "continue"

Next steps

• Troubleshoot device activation issues.
• Troubleshoot device issues.