Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hi,
I have built a Report that uses data from Azure DevOps (Analytics Views) and published it to the Report Server of my company.
I was able to configure it, refresh it several times per day and have it running for a few months until this week.
I needed to modify something in the report and when I published the new version I kept getting the error message
I have tried all options under Edit Credentials but the error message I keep receving is the one below:
Activity ID: | 11dd2d5e-3dd8-43e3-893e-74b606199b29 |
Request ID: | a05f21c2-7a42-9abd-125d-d32bb4dacdda |
Status code: | 400 |
Time: | Thu May 19 2022 09:36:32 GMT+0200 (Mitteleuropäische Sommerzeit) |
Service version: | 13.0.18218.51 |
Client version: | 2205.1.11282-train |
Cluster URI: | https://wabi-north-europe-g-primary-redirect.analysis.windows.net/ |
Can anybody help please?
Solved! Go to Solution.
Hi @DavidPorTodos,
It’s a known issue(ICM 307200975) that Power BI customers using Azure DevOps Server connector may experience issues connecting from desktop and users who already have connection established and report published might experience credentials errors when refreshing the dataset. Product group is working on the fix and will update the expected fix time when available.
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems on it, please let me know. Thanks a lot!
Best Regards,
Community Support Team _ Caiyun
Hi @DavidPorTodos,
It’s a known issue(ICM 307200975) that Power BI customers using Azure DevOps Server connector may experience issues connecting from desktop and users who already have connection established and report published might experience credentials errors when refreshing the dataset. Product group is working on the fix and will update the expected fix time when available.
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly. If I misunderstand your needs or you still have problems on it, please let me know. Thanks a lot!
Best Regards,
Community Support Team _ Caiyun
Do you know if this issue still persists? I was trying to find the known issue (ICM 307200975) to find the status, but for some reason I can't find it.