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!
Helper VHey 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!
Community ChampionBillyT_350 , that is awesome! This reminds me of an exact situation several years ago during a network rebuild, while I was also building out an IT OPS Dashboard that combined telemetry from the Cisco Gear and PRTG SNMP Sensor Data, detected DNS for four of the sites I managed in New England, and four in the Midwest as totally messed up beginning at COB on a Friday until early Sunday. That report saved a great deal of pain, and it was love for Power BI from then on.