Forum Discussion
Error in visuals from outside - Couldn't retrieve the data for this visual
- 1 year ago
Hi MarieKAA ,
Thanks for taking the time to test those changes and for describing your findings so clearly.
Based on what you’ve shared, it does seem like the issue isn't due to report size or complexity. Visuals loading only after changing or removing a filter, or switching pages and coming back, suggests the report server may be slow or having trouble handling requests from outside your network. This could involve how slicer interactions are queued or processed, especially when multiple requests hit the server in quick succession.
Please check whether a proxy, gateway, or firewall in your network setup is affecting the behavior when you’re accessing the report remotely. These can sometimes cause request delays or even partially block content, leading to the kind of pattern you’re seeing.
You can also try opening the report in a browser, press F12 to open developer tools, and check the Network tab. This can show if any requests are slow or failing when you use filters, which might help explain the issue.
Please feel free to share any findings.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.Thank you.
We finally managed to fix the issue, but I don't have the full overview of the solution. The IT group responded that they "changed the http compliance from 500 to 1000 on the WAF"... And apperantly that fixed it, since now the reports are running without errors. However we found out that the install of the report server was not correct - it was installed on the c-drive, and apparantly it has to be on a D Data and L: Log drive... Hopefully fixing this as well will help us avoid future isssues.
I will mark a reply about firewall as the accepted solution.
- v-veshwara-msft1 year ago
Community Support
Thank you so much for sharing this update! It’s great to hear the issue has been resolved.
It’s helpful to know that adjusting the HTTP compliance setting on the WAF and addressing the Report Server installation paths were key to resolving the problem. I hope fixing the installation paths to the appropriate drives also helps prevent future issues.
Thank you again for taking the time to share these details - it’ll definitely help others facing similar challenges.