Forum Discussion
Helper VPBI Dataflows have stopped communicating with Desktop
Hey folks, so it's been about a month. We did a ton of testing with MSFT (mostly "did you try ctrl + alt +del?" stuff), but ultimately by chance our network people got involed, because this also impacted various Azure products, and we found out that it was actually an issue with DNS routing. Someone had added some DNS routing, which our network guy is still investigating. But basically the problem was these new DNS settings were redirecting connections to wabicancencdsa.blob.core.windows.net and other locations either circularly, or to nowhere. Consequentially, PBI desktop could not access the Dataflows, which apparently are stored there.
Additionally, we discovered that this was also preventing the Dataflows in the Service from updating, and so even reports in the Service were missing data, which caused a number of issues.
So, mystery solved. Thanks for all of your help!
Super UserBillyT_350 just a double check, can you create a dataflow in the service and try to connect to the original dataflow? Also, can you make sure nothing is changed on permission? Also, can you make sure re-authenticate dataflow in the Power BI desktop under data source? There are a lot of possibilities as that why it is not working.
Helper Vparry2k Yes, I am able to successfully create a dataflow or dataset in the Service which hits these dataflows:
I am the administrator, so none of the settings, permissions, etc. should have been changed. So far, all of the dataflows and their linked reports in the service have been able to refresh without reporting an error.
- foodd
Community Champion
Oooh, that's awesome! I am reminded of the words of the Solaris Administrator I mentored under long ago who had two standing rules. Never say never, and **bleep** happens.
