Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Power BI workspace not found when name contains URI reserved chars

See original GitHub issue

Describe the problem

Copied from https://github.com/sql-bi/Bravo/issues/494#issuecomment-1277016034

Error 10: A connection problem arises between the server and Bravo.
The specified Power BI workspace is not found.

Technical Details:
RootActivityId: 75f75078-9984-42f6-a6b0-4e16014a7433
Trace Id: 00-10a82270feac38b0b634054e0475f894-9106091162b6ddf0-00
Version: 0.9.6 (0.9.8291.23631)

Got this when trying to connect to a workspace dataset that has a \ within the workspace name. Slash at end is ok, but within no chocolates. Prob a low user case but WS names are free text really!!?? I guess your not using the workspace id to pass request thru? (Let me know if want to raise as sep issue?)

Cheers

Chris

Bravo version

n/a

Tabular model

Power BI Dataset

Power BI

n/a

Steps to reproduce the behavior

Create (or rename) a PBI workspace with a \ within the workspace name
Publish a report in the dataset
Run bravo and connect to the dataset

Additional context

No response

Screenshots

No response

Anything else ?

No response

Issue Analytics

State:
Created a year ago
Comments:10

Top GitHub Comments

1reaction

Chris-Burgess-ACTGOVcommented, Oct 18, 2022

Attempting to reproduce on another machine. Have stable release installed. Updating to DEV release. Logged in to Windows with normal account. Open cmd ‘run as administrator’. Enter admin creds. Run msi from cmd. Install/overwrite works. Now at the Launch Bravo for PowerBI. (Still in the elevated ‘bubble’) Successful Launch. Attempt to log into PowerBI.com (have to tick ‘Authenticate in Browser’ before this will log in. [Sidebar: Should that be ticked OOB or is smaller use case MFA?] All features work (including formatting of DAX [note no 9090 custom proxy setting required.]

Close App Open App (no longer launched withing A bubble). Successful. Cannot reproduce the Issue. Note have to add 909 and switch to custom proxy for formatting to work on this run. Note the successful testing was on a W10 machine of slighly diff spec Note second machine is: Edition Windows 10 Enterprise Version 21H2 Installed on ‎22/‎04/‎2022 OS build 19044.2006 Experience Windows Feature Experience Pack 120.2212.4180.0

While machines that experienced errors on Edition Windows 10 Enterprise Version 20H2 Installed on ‎21/‎03/‎2022 OS build 19042.2006 Experience Windows Feature Experience Pack 120.2212.4180.0

Task Manager. All running under standard account (but remember cannot reproduce, If try to overwrite on ‘error’ machine get the ‘remove’ only option (Change/Repair greyed out) so cant review unless remove, install, stable, try upgrading to dev - launch ticked)

Summary Cannot reproduce the UnauthorizedAccessException issue on the 21H2 build machine. I will attempt the same on the 20H2 (error) machine in the next 24 hours.

1reaction

Chris-Burgess-ACTGOVcommented, Oct 17, 2022

Now back to the Issue 500!!

@albertospelta Appears the fix rolled out in the DEV build 0.9.6-internal-20221013.1-main-1822e834e3394ad4111722d1dad5490d7a9b57d6 (0.9.8321.14222) has addressed the embedding of ‘reserved characters’ in the Workspace name (not tested $ or % or other randoms)