Reporting Services Failover

I have few questions about Reporting Services:
1. can reporting server DB put on a cluster? if so is there a reference article which shows how you can target a specific location for Reporting DB and Reporting TempDB
2. for reporting server DR, should we install two servers with SSRS one at primary site and the other at DR Site pointing to local instances of the clustered DB (DW and Reporting DB are clsutered and mirrored between peimary and DR site)

I have had it confirmed by the Microsoft product team that the link provided by Venkat (which I have reposted below) still applies to SCOM 2007 R2 and SCOM 2012 so the official answer is no, it is not supported from a SCOM perspective to have the SQL
Reporting Services databases as part of a cluster.
http://blogs.technet.com/b/momteam/archive/2008/03/28/operations-manager-reporting-supported-ssrs-configurations.aspx
Like Pavel, I have deployed option 4 and know it works but just be aware that is not supported (for SCOM) to have the SQL Reporting Services databases deployed on a clustered SQL Server.
Cheers
Graham
New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
Is this still the case for SCOM 2012 R2?
Regards,
Chris

Similar Messages

  • Reporting Services as a generic service in a failover cluster group?

    There is some confusion on whether or not Microsoft will support a Reporting Services deployment on a failover cluster using scale-out, and adding the Reporting Services service as a generic service in a cluster group to achieve active-passive high
    availability.
    A deployment like this is described by Lukasz Pawlowski (Program Manager on the Reporting Services team) in this blog article
    http://blogs.msdn.com/b/lukaszp/archive/2009/10/28/high-availability-frequently-asked-questions-about-failover-clustering-and-reporting-services.aspx. There it is stated that it can be done, and what needs to be considered when doing such a deployment.
    This article (http://technet.microsoft.com/en-us/library/bb630402.aspx) on the other hand states: "Failover clustering is supported only for the report server database; you
    cannot run the Report Server service as part of a failover cluster."
    This is somewhat confusing to me. Can I expect to receive support from Microsoft for a setup like this?
    Best Regards,
    Peter Wretmo

    Hi Peter,
    Thanks for your posting.
    As Lukasz said in the
    blog, failover clustering with SSRS is possible. However, during the failover there is some time during which users will receive errors when accessing SSRS since the network names will resolve to a computer where the SSRS service is in the process of starting.
    Besides, there are several considerations and manual steps involved on your part before configuring the failover clustering with SSRS service:
    Impact on other applications that share the SQL Server. One common idea is to put SSRS in the same cluster group as SQL Server.  If SQL Server is hosting multiple application databases, other than just the SSRS databases, a failure in SSRS may cause
    a significant failover impact to the entire environment.
    SSRS fails over independently of SQL Server.
    If SSRS is running, it is going to do work on behalf of the overall deployment so it will be Active. To make SSRS Passive is to stop the SSRS service on all passive cluster nodes.
    So, SSRS is designed to achieve High Availability through the Scale-Out deployment. Though a failover clustered SSRS deployment is achievable, it is not the best option for achieving High Availability with Reporting Services.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here
    Mike Yin
    TechNet Community Support

  • SSL Cert for 2008 R2 Reporting Services that is installed on a Failover Cluster - server address mismatch?

    I utilized the idea from
    http://www.mssqltips.com/sqlservertip/2778/how-to-add-reporting-services-to-an-existing-sql-server-clustered-instance/ to install 2008 R2 Reporting Services on a new Clustered SQL instance.  In short, create the new Clustered SQL instance on Node1,
    installing Reporting Services with it.  Then on Node2, Add a Failover Cluster Node (without choosing Reporting Services); following that up with starting the SQL setup.exe with a cmd to bypass a check so that I can then install the Reporting Services
    feature on Node2.  It points out using the SQL Cluster Network name for connecting to Reporting Services.
    I verified upon failover that I could still access the Reports and ReportServer URLs.  However, when wanting to add an SSL certificate to the RS configuration, I run into the warning of "mismatched address - the security certificate presented by
    this website was issued for a different website's address", where I can continue and get to the Reports or ReportManager URLs.
    I played with different certs (internal CA created) and SANs and other things, but I still get this error with the cert.  The Reports URL, for example, is <a href="https:///Reports">https://<SQLClusterNetworkName>/Reports, and the
    cert has a CN and Friendly Name of SQLClusterNetworkName (with SAN of DNS: SQLClusterNetworkName.<domain>), but the error still happens.
    What am I missing to eliminate the mismatched address warning when using the SQLClusterNetworkName as the base of the URLs?

    I got it working by using the FQDN as the common name on the SSL cert, with FQDN in RS URLs.

  • Service Accounts for Reporting Service in SQL Server Failover Cluster setup

    I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
    There are 2 options to configure the service account for SSRS:
    Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
    Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
    http://msdn.microsoft.com/en-us/library/ms143504.aspx
    which is the recommended one? is it option 2?
    There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
    Security Note:  Always run SQL Server services by using the lowest possible user rights. Use a MSA or  virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
    of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
    directly to a service SID, where a service SID is supported.
    Thanks very much for your help!

    Hi Luo Donghua,
    In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
    simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
    Of cause, you can also use domain accounts in your clustering. 
    Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Reporting Services will not automatically use a different replica for the report server databases when a failover occurs. How to overcome this issue

    Reporting Services offers limited support for using AlwaysOn Availability Groups with report server databases. The report server databases can be configured in AG to be part of a replica; however Reporting Services will not automatically use a different
    replica for the report server databases when a failover occurs. How to overcome this issue? is there any workaround for that..
    Rahul

    Hi.
    With the AlwaysOn listener you should have a single DNS name to connect to regardless of which cluster node is active. Are you using the listener service? If not, please refer to the link below.
    http://msdn.microsoft.com/en-us/library/hh213417.aspx#AGlisteners

  • Moving the Reporting Services and Report Server DB into AlwaysON Availability Group

    I have configured the new set of SQL 2012 AlwaysOn Availability Group and need to move the SSRS and it's Report Server DB into that Availability Group.
    Can anyone give tell me the steps to do this move?
    Can I just backup the ReportServer DB into the AG server then import that DB into the SSRS running on the new AlwasyOn AG SQL?

    Hello,
    Based on your description, it seems that you want to move the Report Server database to a different server. If so, both the reportserver and reportservertempdb databases must be moved or copied together. You can move the databases by using Detaching
    and Attaching or Backup and Restore.
    What's more, you should also backup the encryption keys for the report server database you want to move and then restore to the new server.
    You can configure report server databases in Always On Availability Group to be part of a replica; however Reporting Services will not automatically use a different replica for the report server databases when a failover occurs
    Reference:
    Moving the Report Server Databases to Another Computer
    Reporting Services with AlwaysOn Availability Groups (SQL Server)
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • $100 to the person that can work with me on getting Lightswitch, Telerik Reporting, Azure reporting service working.

    I give up. I am not a professional developer however I am pretty good at coding. But I have limitations and do not understand how all the pieces fit together when it comes to WCF, LightSwitch and Telerik Reporting service.
    I have spent the better part of the past 5 evenings attempting to deploy a WCF service to my azure account to create reports for my application.  I know this should be simple but I cannot find an example that ties all the pieces together.
    I have a
    working lightswitch application deployed to Azure
    20+ working telerik reports created in a separate project (Reports have parameters that is one of the problems)
    No way to get the two to talk together.
    If you have experience and feel you can help me please respond to this post and I will set up some time for us to work together online.
    Regards a very frustrated part time developer
    Cliff
    P.S. Sorry if this is an inappropriate use of the forum but I am at my wits end!

    (I am not in the running for the 'bounty' just trying to help on the WCF RIA part...)
    When you deploy the application to Azure you should be able to hit the WCF RIA Service using:
    site/{class name}.svc/
    For example if you look at the reports I have in this example:
    LightSwitch Survey: Handling
    Complex Business Logic Using WCF RIA Services
    You can use the live application at the following link: https://survey.lightswitchhelpwebsite.com/HTMLClient (use your
    username and password from
    LightSwitchHelpWebsite.com)
    The call in Fiddler looks like this:
    /WCF_RIA_ServiceData.svc/SurveyResults?$filter=(SurveyId%20eq%202)&$top=45&$inlinecount=allpages
    This is what your reports should be calling. Can you get this far?
    Unleash the Power - Get the LightSwitch 2013 HTML Client / SharePoint 2013 book
    http://LightSwitchHelpWebsite.com

  • Reporting Services Webpart - web part does not auto render consistantly

    We are on SharePoint 2010 (integrated with Reporting Services)- on several sites we have added the Reporting Services Web Part and with a saved parameter.  The behavior of this web part is not consistent.  There are times when I open up a site
    and the web part will auto render the report.  5 minutes later I can go into the same site, and the web part does not auto render the report.  I have to do edit page, or close and re-open the web site.  Has anyone experienced this type of behavior. 
    I've looked for assistance with this issue on-line cannot find anything that specifically addresses this issue.   

    Hi Karen,
    If the parameters have default values in the report, then the report can be rendered automatically.
    For this issue, I recommend to verify the things below:
    Does this issue occur when you open the page with the web part in a new tab in the browser or go back to the previous opened tab?
    Does this issue occur in the server side or client side?
    Please add the site to trusted sites in Internet Explorer to see how it works.
    Please change another browser to see how it works.
    For narrowing down the issue scope, please test with another report and compare the results.
    Thanks,
    Victoria
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Reporting Services 2008 R2 - SharePoint Integration Mode

    Hi everyone,
    I installed Reporting Services 2008 R2 in my SharePoint(2013) server and configurated the SSRS to run in SharePoint Integrate mode. But, when I run the command Install-SPRSService in SharePoint 2013 Management Shell, I get this error: 
    Does anyone know how resolve it ? I search but I didn't get a solution :(
    Thanks in advance!
    Best Regards!

    SSRS 2008 R2 isn't supported with SharePoint 2013. You'll need a minimum of SSRS 2012 SP1. In addition, SSRS 2008 R2 doesn't include the cmdlet you're looking for because it isn't a Service Application, rather it sat external to SharePoint.
    The support matrix is at http://msdn.microsoft.com/en-us/library/gg492257.aspx.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Reporting Services not able to connect with sharepoint

    HI
    We have a Sql server instance where we are not able to install reporting services, so what we have done is we have created one more sql server instance on the same server with reporting services.
    When we configured reporting services in sharepoint integrated mode and try to connect that web service url in sharepoint we are getting an error in sharepoint central administartion  that not able to connect to the reporting services.
    Request you to throw some light on the same.
    Thanks
    Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

    Hi Geeth,
    Based on the limited information, I am not very clearly about you issue. In order to solve the problem more efficiently, I need to clarify some information. Could you post more detail information about “try to connect that web service url in sharepoint we
    are getting an error in sharepoint central administartion”? For example, the detail steps about the action, the screenshot of the action, and what error message you received. I’m not sure which step are you trying to do. And could you tell me the edition of
    your SQL Server and SharePoint? It is benefit for us to do further analysis.
    References:
    2008 R2:
    http://technet.microsoft.com/en-us/library/bb283190(v=sql.105).aspx
    http://sharepointtaskmaster.blogspot.in/2010/11/intergration-reporting-service-with.html
    http://technet.microsoft.com/en-us/library/bb326213(v=sql.105).aspx
    2012:
    http://technet.microsoft.com/en-us/library/47efa72e-1735-4387-8485-f8994fb08c8c
    http://denglishbi.wordpress.com/2011/07/22/configuring-sql-server-denali-reporting-services-sharepoint-2010-integration/
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • "Reporting services" service does not start automatically

    I have installed reporting services from SQL Express SP1 package. OS is Windows 2000 SP4. Just after installation "Reporting services" service has StartMode=Automatic and LogOnAS=LocalSystem as shown in SQL Server Configuration Manager. When system is rebooted reporting services state is Stopped and there is 2 errors in System log:
    1. Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (REPS) service to connect.
    2. The SQL Server Reporting Services (REPS) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
    If i select "start" from service's context menu then it starting normally and it's state becomes Running.
    What can i do to make reporting services starting automatically on system load?

    i  have the same problem here in one of our servers ,, it was working and suddenly it stopped i don't know why 
    when i reviewed the Event Viewer :
    Event Type: Error
    Event Source: SQL Server Report Service
    Event Category: None
    Event ID: 0
    Date: 8/22/2010
    Time: 12:05:26 PM
    User: N/A
    Computer: SERVICE-CENTER
    Description:
    Service cannot be started. Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information. ---> System.UnauthorizedAccessException:
    Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is denied.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
       at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
       at Microsoft.ReportingServices.Diagnostics.Globals.SafeOpenXmlDocumentFile(XmlDocument doc, String pathToXmlFile)
       at Microsoft.ReportingServices.Diagnostics.RSConfiguration.LoadDocument()
       at Microsoft.ReportingServices.Diagnostics.R...
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Any body can help with this ,, because i didn't find anything helpful till now !!!
    dear all 
    i installed SQL Server 2005 SP2 and it solved my problem 
    wish you all luck 

  • Reporting Services Point, remote SQL issue

    I'm trying to install Reporting Services Point on a remote SQL 2008 R2 SP2 server. I select the SQL server under Servers and Site System Roles and it lists the site database server name, database name (should this name be the same as the DB found in Reporting
    Services Configuration Manager?), folder name and reporting services server instance. I enter a new account that is a sysadmin on the SQL click verify and get:
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
    (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).
    Ping works both ways, remote connection on this SQL instance are enabled, static ports configured, a rule to allowany is set in the firewall. Should I perhaps be entering the port (this instance uses a non-standard one) in the Add Site System Roles
    Wizard?
    If I open up Reporting Services Configuration Manager, the service is started, mode is native, a domain user account is used for the service account, web service URL opens, I even created a new DB. Report Manager URL opens.
    SCCM itself uses the same remote SQL instance, so it appears connectivity works fine.
    Any assistance is appreciated.

     Thank you very much - CypherMike. 
    You helped me so much!!!
    I installed the DB on another Instance so i had to change the port # and just here i found this info that i need to use comma to define the port.
    Tnx

  • Reporting Services Point status message errors.

    My Reporting Services Point seems to work OK -all reports are available and run correctly both through the console and via the website. However, I am seeing the following warning in the SMS_SRS_REPORTING_POINT status messages every hour:
    "The SQL Reporting Services datasource on Reporting point server "Databaseserver.contoso.com" is missing or has been changed outside of Configuration Manager.  It will be rebuilt based on the RSP configuration."
    Here's what I think is causing the issue, but I don't know how to solve it.
    The reports database is on the same remote SQL server as my site database. Because these site systems were installed automatically through the SCCM installation process, they show up in the Servers and Site Systems Role without an intranet FQDN. However,
    when I add the RSP to the database server, it creates a new entry because when manually adding site systems SCCM insists on automatically adding the intranet FQDN. So I now have two separate entries for the same server:
    \\DBServer01 - component server, site database server, site system
    \\DBServer01.contoso.com - component server, reporting services point, site system
    Any thoughts on how to stop these errors?

    Yes, I know this is an old post, but I’m trying to clean them up.
    In the past when I have seen this, they will automatically clean themselves up after a few days. (aka up to a week later). Have it clean itself up yet?
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Reporting Services Point SSL after Role installed

    Scenario,
    Reporting Services (SQL 2012) installed on a remote server and not configured with SSL.  Reporting Services Point installed and functioning correctly.
    We now have enabled SSL in RS Configuration using a cname for the certificate (sccmreports.domain.com) and it is working via web browser, however when I attempt to remove the port 80 binding it breaks SCCM's ability to connect to the reporting point via
    the admin console.   Presumably, if SSL is not enabled prior to installing the RSP that SCCM only knows to connect via HTTP?
    If this is the case, outside of uninstalling and re-installing the RSP now is there a way to "tell" SCCM to use HTTPS to connect?  Maybe its a different issue altogether?
    Thanks!

    The SSRS connection info is stored in Site control file, which is in the view vSMS_SC_SiteControlXML. If you change the SSRS address manually, the info cannot be updated automatically so that you must reinstall SSRS.
    Juke Chou
    TechNet Community Support

  • Reporting Services web service complex xml type report parameters

    Hi,
    I have the following xml type parameter in my request query that I use in reporting services.
    <Parameter Name="accountDetails" Type="XML" xmlns:d4p1="thevalue" xmlns:i="thevalue">
    <DefaultValue>
    <d4p1:AccountDetailDto>
    <d4p1:AccountNumber>12345</d4p1:AccountNumber>
    <d4p1:AccountType>Sales</d4p1:AccountType>
    </d4p1:AccountDetailDto>
    </DefaultValue>
    I want to know how I can assign values to the accountDetails parameter from report parameters, I've tried to call it from the dataset parameter properties but it doesn't return any values. I created Parameters!accountDetails.Value on the dataset parameters
    properties and assigned it the following value: it only returns empty columns
    ="<AccountDetailDto><AccountNumber>"& Parameters!AccountNumber.Value &"</AccountNumber><AccountType>"& Parameters!AccountType.Value &"</AccountType></AccountDetailDto>"
    You're help will be highly appreciated as I've been trying to solve this for a while now

    Hi Alisa,
    Perhaps I should explain my problem clearly...
    This is my query request that I send to the webservice:
    <Query>
    <Method Name="GetPerAccountAssetAllocation" Namespace="http://tempuri.org/">
    <Parameters>
    <Parameter Name="accountDetails" Type="XML" xmlns:d4p1="thevalue" xmlns:i="thevalue">
    <DefaultValue>
    <d4p1:AccountDetailDto>
    <d4p1:AccountNumber>12345</d4p1:AccountNumber>
    <d4p1:AccountType>JSE</d4p1:AccountType>
    </d4p1:AccountDetailDto>
    </DefaultValue>
    </Parameter>
    </Parameters>
    </Method>
    <SoapAction>http://tempuri.org/IPortfolioManagementService/GetPerAccountAssetAllocation</SoapAction>
    <ElementPath IgnoreNamespaces="true">*</ElementPath>
    </Query>
    It works well when I run it just like this, that is without specifying any parameters in the report data dialogue window or on the dataset parameters properties, it returns the values and columns correctly.
    So my problem is, I need to find out how(xml parameter syntax, steps e.t.c)
    I can do to allow users to specify the accountDetails parameter, its quite tricky for me coz its an xml type parameter, Im not sure if I should just specify the AccountNumber and
    ReportType parameters separately:
    I've tried the following without any success:
    1. Under the dataset properties:  I tried not to specify a default value for the accountDetails parameter on the xml query, then I added a parameter called "accountDetails" under the dataset parameters properties, then under parameter
    value I added the following xml value :
    <d4p1:AccountDetailDto>
    <d4p1:AccountNumber>Parameters!AccountNumber.Value</d4p1:AccountNumber>
    <d4p1:AccountType>Parameters!AccountType.Value</d4p1:AccountType>
    </d4p1:AccountDetailDto> 
    (I also added the AccountNumber and AccountType parameters under the report data dialogue window)
    This returns empty columns, is there something I'm missing, or am I doing this incorrectly?

Maybe you are looking for