Error messages and fixes

Most errors in Measure Killer come from a handful of causes on the Power BI or network side. Search this page for the text of your error message, or look for the closest match below. If your error is not here, send us the message and your Measure Killer logs at support@measurekiller.com.

Semantic models

DatasetExecuteQueriesError: Failed to execute the DAX query (3239575574)

You may see this as DatasetExecuteQueriesError, “Failed to execute the DAX query”, AnalysisServicesErrorCode 3239575574, or a BadRequestError next to a semantic model, while the model refreshes fine in the Power BI Service.

The model is in a Pro workspace. Pro workspaces have no XMLA endpoint, so Measure Killer reads the model through a Power BI API that has a known bug on Microsoft’s side. Microsoft enables the fix tenant by tenant.

To fix it, send us your tenant ID at support@measurekiller.com. You find it in the Power BI Service under ? → About Power BI, or in Microsoft Entra ID under Overview. We forward it to Microsoft, and the error usually goes away after about 24 hours. Then run the analysis again.

If you cannot wait, assign the Pro workspace to a capacity for a moment (an F SKU, a P SKU or a Fabric trial capacity), run the analysis, and move the workspace back to Pro afterwards.

Auto-generated models such as “Report Usage Metrics Model” and “Usage Metrics Report” also show this error. You can ignore those.

DatasetExecuteQueries_DatasetNotAllowed

The full message says that the dataset “is a model hosted in Azure Analysis Services or SQL Server Analysis Services using On-Premise Gateway, which is not allowed”.

The report uses a live connection to Analysis Services. Measure Killer cannot read that model through Power BI, and whitelisting does not change that. Analyze the Analysis Services model itself with the SSAS and AAS mode instead, see Unused objects in Analysis Services models.

UnauthorizedError: User is not authorized (401)

This shows up as UnauthorizedError, PowerBINotAuthorizedException or “User is not authorized” while Measure Killer fetches report layouts, often twice per report.

It is often temporary, so run the analysis again first. If it comes back, check your role in that workspace. With Viewer, Measure Killer can read the reports, but semantic models need Contributor or higher.

CapacityNotActiveError

The workspace sits on a Fabric capacity that is paused. Resume the capacity in the Azure portal and run the analysis again.

XMLA connection

ServerNotFoundError or workspace not found

Measure Killer cannot find the XMLA server of the workspace. There are three common causes:

• A different account in the second sign-in. Measure Killer asks you to sign in twice: once for the APIs and once more for XMLA. If you pick another account in the XMLA popup, and that account does not have the required permissions on the workspace, the server cannot be found. Run the scan again and choose the same account both times, see Run the scan.
• You are a guest user in someone else’s tenant. Set the XMLA custom domain, see Run Measure Killer as a guest user.
• The XMLA endpoint is turned off for the capacity. In the Admin portal, under the capacity’s settings, the XMLA endpoint should be set to Read Only or Read Write.

StorageInvalidData while generating the MWC token

An AdomdConnectionException with “Generating MWC token” and StorageInvalidData almost always means you are signed in as a guest user. Set the XMLA custom domain to the host tenant’s domain, see Run Measure Killer as a guest user.

Sign-in

Authentication fails right after signing in

If more than one Microsoft sign-in window opened, you may have completed the wrong one. Close Measure Killer, start it again, and sign in once. Authentication errors are also sometimes temporary, and a restart fixes them.

For Capacity Metrics you also need to be a capacity admin of at least one capacity, see Capacity metrics.

Network and license

getaddrinfo failed or Failed to resolve api.powerbi.com

Messages such as getaddrinfo failed, NameResolutionError: Failed to resolve 'api.powerbi.com', MaxRetryError or ConnectionError mean that Measure Killer cannot reach a server.

This is often temporary. Close Measure Killer, check that your internet or VPN connection is up, and start it again. If it keeps happening, your network is probably blocking the connection. Enter your proxy in Settings → API and XMLA, and ask IT to allow the domains in Network requirements.

License cannot be verified or Could not get the current time

Measure Killer checks your license and the current date online when it starts. If it cannot reach the license server or any of the date and time sources, you see that the license cannot be verified, or “Could not get the current time. All methods failed”.

Restart Measure Killer and check your connection first. If it keeps happening, the license or time servers are blocked on your network, see Network requirements. Make sure you are on the latest version of Measure Killer too.

License key has expired after a renewal

You are on a version older than 2.9.3, which does not pick up the extension. Update Measure Killer, see Renewed, but Measure Killer still says the license expired.

Startup

Measure Killer is not responding or does not open

The first start can take 20 to 30 seconds. Wait for it without clicking the loading logo, and make sure only one Measure Killer is running. See The first start can take a while.

Where to find the logs

Measure Killer saves its logs in your %APPDATA% folder, in %APPDATA%\Measure Killer. Your license key file (.json) and the other files Measure Killer keeps between sessions are in the same folder.

To open it, press Windows + R, type %APPDATA%\Measure Killer and press Enter. When you contact support, attach the log files from that folder together with the text of your error message.