Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
I am constantly getting the below error - using the same credentials that succeed with powershell access to API. We would prefer to use the PowerBI pack than roll our own.
Activity Id: | bc0c9164-cd33-4005-acbb-eef8061c3d09 |
Request Id: | 6d99a618-b42f-930a-c434-3d74b39c2f81 |
Status Code: | 400 |
Time: | Tue Nov 03 2015 09:25:47 GMT+0000 (GMT Standard Time) |
Version: | 11.0.9168.508 |
Cluster URI: | https://wabi-north-europe-redirect.analysis.windows.net |
Details: | Web.Contents failed to get contents from 'https://ea.azure.com/rest/xxxxx/usage-report' (404): Report not available |
Solved! Go to Solution.
Raised this with Premier support - it's working now, root cause as below:
The error you are experiencing is due to a delay with the completion of the monthly charges and usage calculations. The delayed calculation of charges and usage has caused monthly reporting to be unavailable until the job completes. API and Power BI require the monthly reporting to process, hence the errors. I’ve been advised by engineering that their monthly calculation batch job is almost complete. Engineering expects the issue to be resolved after system refresh tonight. Please allow until tomorrow afternoon PST for the usage calculations to update and correctly and reflect under your enrollment’s reporting. You should then have access to API.
Raised this with Premier support - it's working now, root cause as below:
The error you are experiencing is due to a delay with the completion of the monthly charges and usage calculations. The delayed calculation of charges and usage has caused monthly reporting to be unavailable until the job completes. API and Power BI require the monthly reporting to process, hence the errors. I’ve been advised by engineering that their monthly calculation batch job is almost complete. Engineering expects the issue to be resolved after system refresh tonight. Please allow until tomorrow afternoon PST for the usage calculations to update and correctly and reflect under your enrollment’s reporting. You should then have access to API.