Troubleshooting error messages in Azure VM

Troubleshooting step for the error message 'VM has reported a failure when processing extension' while trying to add Site24x7 Azure VM Extensions

Occasionally, when the extension is configured along with the creation of VM using the new Azure portal, the deployment can fail. To workaround this issue, try adding the extension after the deployment of the VM. 

On the other hand, you may get these messages while deploying the VM extensions to classic VMs using the new Azure portal. 
The operation failed due to an internal error. Please retry the operation after sometime. 
The resource operation completed with terminal provisioning state 'Failed'.

If you get error message like above or any other issue while adding the extension to a classic VM, kindly check the operation logs for more details. To verify the operation logs, go to Azure Classic Portal (https://manage.windowsazure.com/) and check the operation logs (under Management services). The logs can be filtered based on service. On clicking Details of the respective log, it will give the xml content of the failure. 

<SubscriptionOperation xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> 
...
    <OperationStatus>
        <ID>XXXXXXX-XXX-XXXX-XXXX-XXXXXXX</ID>
        <Status>Failed</Status>
        <HttpStatusCode>400</HttpStatusCode>
        <Error>
            <Code>BadRequest</Code>
            <Message>...</Message>
        </Error>
    </OperationStatus
...
</SubscriptionOperation>

If you require further support, please write to us at support@site24x7.com. Please send us the status part of the operational logs for troubleshooting. 

    • Related Articles

    • Troubleshooting steps for On-Premise Poller

      Prerequisites and basic details: Prerequisites for installing On-Premise Poller Necessary ports to allow access to the installed On-Premise Poller How secure is On-Premise Poller Amount of bandwidth consumed by the On-Premise Poller software Adding ...
    • Troubleshoot Error 401 (Unauthorized error) for RabbitMQ

      When installing the RabbitMQ monitoring plugins, you may encounter the following error: HTTP Error 401: Unauthorized: This error occurs when the user attempts to access the /api/overview endpoint of RabbitMQ server, which requires authentication, but ...
    • Troubleshooting tips for log collection errors

      The following is a list of possible log collection errors and the solutions to fix them: Error message Reason Solution Upload Limit Reached You might have reached the maximum upload limit configured for this log type in the current billing cycle. ...
    • Troubleshoot the Error 404 and Error 99 for RabbitMQ

      When installing the RabbitMQ plugin, you may encounter the following errors: HTTP Error 404: Not Found: This error usually occurs when Site24x7's RabbitMQ monitoring plugin attempts to access the /api/overview page of RabbitMQ, but the resource ...
    • Troubleshoot Error 404, Error 111, and "no host given" error when installing the Apache plugin

      When installing the Apache monitoring plugin, you may encounter the following errors: Error_code : URL Error no host given: The "no host given" error message typically indicates an issue with a URL or request that lacks a hostname. If you encounter ...