Forum Discussion
Cannot create Scheduled Refresh Plan on on-premises Power BI Report Server
- 4 years ago
That's strange, there is no specific error message, so it is difficult to determine the problem.
Try to restart the sql database service in machine.Is the RS report in the production environment from the previous test environment or is it newly uploaded?
If it still doesn’t work, I’m afraid you have to reinstall RS.
Troubleshoot scheduled refresh in Power BI Report Server - Power BI | Microsoft Docs
Best Regards,
Community Support Team _ Janey - 4 years ago
我也遇到过这个问题。
后来我查看D:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles日志,发现是权限的问题。设置能够完全控制下面这个路径的文件夹即可。
或许你也可以检查一下对这个文件夹的访问权限。
appdomainmanager!DefaultDomain!1cc0!07/02/2021-16:45:00:: e ERROR: AppDomain ReportServer error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_PBIRS_1. ---> System.UnauthorizedAccessException: 对路径“D:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\RSTempFiles\~AspAccessCheck_81fb13747360.tmp”的访问被拒绝。 - Anonymous3 years ago
Hi Team,
I am also facing the similar issue in my prod environment. However it is a painful to restart/reboot the service to get it resolved. Is there any alternate ways to handle this error.
Currently when ever i am getting this error below steps i am following which is not a candidate for production environments.
1. Clearing SQL Logs in SSMS.
2. Restarting the service and also Rebooting mechine.(Which may not required).
3.All the credentials are correct only.
Please support me to solve the Issue.
Thanks & Regards,
Phanikumar B
Hi Team,
I am also facing the similar issue in my prod environment. However it is a painful to restart/reboot the service to get it resolved. Is there any alternate ways to handle this error.
Currently when ever i am getting this error below steps i am following which is not a candidate for production environments.
1. Clearing SQL Logs in SSMS.
2. Restarting the service and also Rebooting mechine.(Which may not required).
3.All the credentials are correct only.
Please support me to solve the Issue.
Thanks & Regards,
Phanikumar B