Azure Virtual Machine – Boot diagnostics – Failed to get contents of blob

Update: Turns out that the Boot diagnostics failure that I’ve been getting below has got nothing to do with my Azure Virtual machine being stuck in the “Starting” state. If you arrived on this post because you have the same issue of a VM being stuck in “Starting” state, follow this post instead. Otherwise, keep reading if you want to find more about the Boot diagnostics failure.

Whenever I go to the Boot Diagnostics of a Virtual Machine, I keep getting the following error:

Failed to get contents of the log ‘{some-link-here}‘ of virtual machine ‘{some-subscription-details-here}’: ‘message: Failed to complete the RPC call for ‘getExtendedInfoBlob’ stack: ###_RPC_Exception_### From RPC: Microsoft_Azure_Compute -> Microsoft_Azure_Storage (getExtendedInfoBlob) (Callstack capturing is not enabled. Use ?trace=diagnostics to enable it.) ‘ Error message: ‘message: Failed to complete the RPC call for ‘getExtendedInfoBlob’ stack: ###_RPC_Exception_### From RPC: Microsoft_Azure_Compute -> Microsoft_Azure_Storage (getExtendedInfoBlob) (Callstack capturing is not enabled. Use ?trace=diagnostics to enable it.) ‘

I’ve not been able to find a solution online and have no idea why this started occurring. What fixed this issue for me is to replace the storage account set for the Boot Diagnostics as the current account seems to have some problems. Below are the steps:

  1. Navigate to the resource group (same subscription) where your Virtual machine belongs to
  2. Click on +Add > Storage account
  3. Give it a name and fill up the rest of the details. Here’s what I had:
    • Deployment model: Resource manager
    • Account kind: Storage (general purpose v1)
    • Performance: Standard
    • Replication: Locally-redundant storage
    • Secure transfer required: Disabled
    • Virtual networks: Disabled
  4. Click create once you’re happy with the configuration
  5. Once it’s created, navigate to your Virtual Machine
  6. Under Support+Troubleshooting, click Boot diagnostics
  7. Click Settings
  8. On the *Storage account, select the new account you just created
  9. Click “Save”

After following the above steps, I checked the Boot diagnostics right away but still got the same error.

Be patient because after a few minutes, it finally worked đŸ™‚

 

Submit your review
1
2
3
4
5
Submit
     
Cancel

Create your own review

Average rating:  
 1 reviews
Great tip !!

Thanks for the great tip around the re-deploy....I ran into the same issue for one of my VMs.I did a stop on it just before I found your blog post......I ended up getting an error for the re-deploy (since my VM was de-allocated) so started it back up and it was all fixed !!I hope you dont mind me referencing this post for a blog article I plan to write about this issue....