Forum Discussion

quenart's avatar
quenart
Regular Visitor
7 years ago

Create scheduled refresh plan. An internal error occurred on the report server database.

Hello,   I am trying to troubleshoot a PowerBI report server issue for my clients.   : An error occurred within the report server database. This may be due to a connection failure, timeout or lo...
error
High availability
PowerBI Report Server
Schedule Refresh
saykasku's avatar
saykasku
Icon for Resolver I rankResolver I
7 years ago

Hi,

Check this permissions:

 

And this premissions:

GRANT SELECT ON [dbo].[syslogins] TO RSExecRole

In scalable solution RS have problem with modify TempFiles or creating Jobs (schedulers).
It's working for me.

d_gosbell's avatar
d_gosbell
Icon for Super User rankSuper User
7 years ago

If you are running PBIRS behind a load balancer make sure you have followed all the configuration steps in the following article https://docs.microsoft.com/en-us/sql/reporting-services/report-server/configure-a-report-server-on-a-network-load-balancing-cluster?view=sql-server-2017

 

Pay special attention to the BackConnectionHostName registry setting (including re-booting if you need to set this property). PBIRS is made up of a set of 4-5 services and if you don't have this set properly a single request from a client can jump back and forth between the nodes in your cluster and this can cause all sorts of weird errors.

 

And note the following article outlines the manual steps required when failing over in an Availability Group

https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/reporting-services-with-always-on-availability-groups-sql-server?view=sql-server-2017#bkmk_steps_to_complete_failover

 

Steps to complete disaster recovery of Report Server Databases

The following steps need to be completed after a Always On availability groups failover to a secondary replica:

  1. Stop the instance of the SQL Agent service that was being used by the primary database engine hosting the Reporting Services databases.

  2. Start SQL Agent service on the computer that is the new primary replica.

  3. Stop the Report Server service.

    If the report server is in native mode, stop the report server Windows server using Reporting Services configuration manager.

    If the report server is configured for SharePoint mode, stop the Reporting Services shared service in SharePoint Central Administration.

  4. Start the report server service or Reporting Services SharePoint service.

  5. Verify that reports can run against the new primary replica.