-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP error 403 (Forbidden) while connecting to a PBI dataset in a PRO licensed workspace #644
Comments
Hi @objecto, thanks for reporting! The inner error message indicates that the request was not authorized by the server
Would it be possible for you to test using DaxStudio and let us know if you get the same error? |
Hi @albertospelta , thanks for the quick reply. Yes it connects just fine. |
@objecto Does the error also occur with other datasets or only with this one? |
Hi Alberto.
This is the latest DAX Studio.
It is an imported dataset , it is on the same Workspace and Tenant as all the others I’ve tried through Bravo.
Let me remind you that with the production version of Bravo I get a 500 error (in Greek) that says I have no rights to the Discover method.
Let me know if you want me to give you more specifics about this.
|
@objecto Unfortunately, I cannot reproduce the problem on my side. In order to identify the cause and try to reproduce the error, it would be helpful for me to know what the properties are and the differences between this dataset and another one that you have tried successfully through Bravo. You can view dataset properties in the diagnostics panel after enabling the verbose diagnostics level. Once diagnostics are enabled you can copy dataset metadata via the "Copy Message" function. The information that would be helpful for me to know would be the information highlighted in the orange boxes for these diagnostic events:
If you prefer to share them privately, feel free to email me here [email protected]. |
Hello Alberto.
I really appreciate your time for this one.
Let me get back to you by following your instructions in order to supply you with more information.
I really love your product guys and I’m happy to help.
Depending on the log information I’ll let you know if the information will be publicly available.
|
Describe the problem
After switching to Dev branch to avoid error "No right to call Discover method" , now I get "The connection either timed out or was lost" instead. I'm accessing a dataset on a "Pro" workspace, in a tenant where I'm the admin. Didn't have this problem a while ago. Last time I used Bravo to check those datasets must have been 2-3 months back.
The complete error stack is as follows:
Bravo version
1.0.2-internal-20230412.1-main-308e7834fcee7ccec2134658206e2924322f56fd (1.0.8502.21762)
Tabular model
Power BI Dataset
Power BI
Service version:13.0.20534.70
Steps to reproduce the behavior
Additional context
No response
Screenshots
Anything else ?
No response
The text was updated successfully, but these errors were encountered: