MMA Extension Is Not Provisioned Correctly and Running Troubleshooting Tool Doesn't Help

Open

#182 opened on Aug 2, 2023 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 20/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: azure, sql
Domain: cloud, databases, observability

Research direction

Start with the attached tool.log and compare it with the linked Azure VM extension and agent troubleshooting guidance. Reproduce the SQL best practices assessment failure and determine why the MMA extension is not provisioned correctly; done means the extension deploys successfully and the assessment runs without the reported error.

Written by the indexing model from the issue text.

Description

I ran SQL best practices assessment for SQL virtual machine and got this failure:

Then I went through these troubleshooting steps and everything looks fine:
https://learn.microsoft.com/en-us/azure/azure-monitor/visualize/vmext-troubleshoot?WT.mc_id=Portal-SqlAzureExtension#troubleshoot-the-azure-windows-vm-extension

Next, I followed these steps and chose "The agent extension deployment is failing" scenario:
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agent-windows-troubleshoot?WT.mc_id=Portal-SqlAzureExtension&tabs=UpdateMMA#use-the-troubleshooting-tool

And I got this log:
tool.log

Then I ran the SQL best practices assessment again but still got the same error. Can you please help me to solve this problem? Many thanks!

Dominant language: PowerShell
Stars: 1.2k
Forks: 493
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
fix(mcp): `permanently_delete_cloud_{source,destination,connection}` lack `workspace_id` param, unusable without a default workspace Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

airbytehq/PyAirbyte#1201 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026
[Bug]: aws_lb_listener silently ignores tcp_idle_timeout_seconds on TCP_UDP listeners Open

bug needs-triage service/elbv2

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

hashicorp/terraform-provider-aws#50100 · 1 comment · Opened Sep 21, 2026

More Cloud issues