Forum Discussion
Trouble loading the settings for automatic page refresh
Hi,
I am getting this message on a report in the service. The dataset and report is in a premium per user workspace and the user has direct read access to the report. I have tried enabling build access in case that was the issue but it doesn't seem to make a difference.
Activity ID: 1af61ea9-3082-4e0e-a22b-a26273273316
Request ID: ba951af0-f141-331b-b277-95b807a32f6e
Correlation ID: e0052dec-adb1-a9ce-8ba7-9b88b479a160
Status code: 401
Time: Tue May 09 2023 11:13:25 GMT+0100 (British Summer Time)
Service version: 13.0.20626.62
Client version: 2305.1.13619-train
Cluster URI: https://wabi-uk-south-redirect.analysis.windows.net/
Thanks
Hi, robshpratt
The error message you are seeing indicates that the user does not have the necessary permissions to access the report. This could be due to a number of reasons, such as:
- The user does not have access to the dataset that the report is based on.
- The user does not have access to the workspace that the report is published to.
- The user does not have the necessary permissions to view the report.
To troubleshoot this issue, you can try the following steps:
- Check that the user has been granted access to the dataset that the report is based on. You can do this by going to the "Access" tab in the dataset settings and ensuring that the user has been added with the appropriate permissions.
- Check that the user has been granted access to the workspace that the report is published to. You can do this by going to the workspace settings and ensuring that the user has been added with the appropriate permissions.
- Check that the user has the necessary permissions to view the report. You can do this by going to the report settings and ensuring that the user has been added with the appropriate permissions.
If the user has the necessary permissions and is still unable to access the report, you may need to check the logs in the Power BI service to see if there are any errors or issues that are preventing the user from accessing the report.
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
3 Replies
Hi, robshpratt
The error message you are seeing indicates that the user does not have the necessary permissions to access the report. This could be due to a number of reasons, such as:
- The user does not have access to the dataset that the report is based on.
- The user does not have access to the workspace that the report is published to.
- The user does not have the necessary permissions to view the report.
To troubleshoot this issue, you can try the following steps:
- Check that the user has been granted access to the dataset that the report is based on. You can do this by going to the "Access" tab in the dataset settings and ensuring that the user has been added with the appropriate permissions.
- Check that the user has been granted access to the workspace that the report is published to. You can do this by going to the workspace settings and ensuring that the user has been added with the appropriate permissions.
- Check that the user has the necessary permissions to view the report. You can do this by going to the report settings and ensuring that the user has been added with the appropriate permissions.
If the user has the necessary permissions and is still unable to access the report, you may need to check the logs in the Power BI service to see if there are any errors or issues that are preventing the user from accessing the report.
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I have a composite model and getting the same error since I moved the report to another workspace, separated from the source datasets and removed unncessesary tables. Cleared all permission cache and reconnected to the sources.
Any ideas how to fix it?Did this get resolved? I had the same issue. I gave the account admin access to the workspace, and added it to every single senmatic model. The error still poped up.
