September 21, 2017 at 9:39 am
Hello,
We are using SQL 2012, and SharePoint 2013 for SSRS and it is set up with always on availability. We have two instances of SQL server on the same server, we have the main SQL Server on the default instance and the ReportServer on a separate Report Server instance. Our primary server has a high CPU usage often, so I was trying to move the report server instance to the secondary server to see if that would resolve the CPU load issue.
When I failover the report server to the secondary server, I am able to run reports for 5 - 10 minutes sometimes longer, before I get the attached error, something about ReportingSserviceTempDB being read-only, but I am not seeing that database being in read-only mode.
Also when I failover the report server instance, the sql server agent and jobs are not failing over to the secondary server they still show the primary server jobs. So I am wondering if something is not set up right with the availability groups.
Any help would be appreciated.
Thanks,
Sam
September 21, 2017 at 9:50 am
Is your Reporting Services configured to point to an Availability Group listener or just an instance?
With Reporting Services and AlwaysOn Availability Groups, it's not as simple as just doing a normal failover. There are other steps you have to follow as well, including stopping and starting some services. See here: https://technet.microsoft.com/en-us/library/hh882437(v=sql.110).aspx
September 24, 2017 at 11:55 pm
The following site has some useful information:
Regards,
DBASupport
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply