Odd new error: Encrypting the connection isn't supported for Data source kind: Power BI

[Tomcat3]

I've been working witht the same Power BI Dataflow for the past six months. Today a number of table transformations are failing. This happens when I attempt to merge a base table with a dimension table, basically flattening a few values. (simple lookups)

It is important to note that no security settings have been changed on my developer side, and the Admin insists no security changes were made on the Ops side. My suspicion is this is a new error in the Service, but right now I would settle for a clue. There are no data protection restrictions in place, as far as I know.

[otravers]

Looks like a bug for sure, that error message has only a single mention on the web and it's from years ago for a Web source (where the error might actually make sense).

I'm not seeing it in my dataflows that use merges, this is a good candidate for a support ticket.

[Tomcat3]

I can add some context to this problem. The cryptic reference to encryption is clearly in error, but did provide a clue. I verified credentials for every connection in my Dataflow, mostly on a hunch based on previous issues. Not enough. I was then checking earlier Dataflows and my Dimension Dataflow showed errors never previously seen. It had been stable for many months. Failed yesterday for no known reason. 

The credentials are correct, had not changed, and I could recreate the Dataflow using the originals. Clearly something got corrupted on the back-end. Not your typical expiration and not a failure due to changed passwords. The "configure connection" button on this message does not have any effect other and "...an unknown error has occurred....". No sh*t, Sherlock.

[otravers · Accepted solution]

That makes more sense, the error is coming from that source dataflow then trickled down through the merge. I agree the initial error message is cryptic, but that's par for the course with Power BI error messaging.

Please accept your own message as a solution to the thread is marked as resolved.

[Tomcat3]

I'll close this thread and re-post the source error, there's got to be a way to correct credentials. I know something is cached somewhere, since the error persists. Assume something is corrupted. So far I have been unable to initiate a reboot of Azure Cloud.