When you install standalone SQL Server (apply for standalone and also standalone for AlwaysOn Availability Groups) you can select Install and configure Reporting Services and installer does simple configuration of the Reporting Services that is suitable for most of the applications.

There is a reason why the default choice for Reporting Services during installation of the SQL Server on the node of the Failover Cluster (AlwaysOn Failover Cluster Instances) is Install only and not Install and configure. Even when you select Install and configure the installer is not able to configure the Reporting Service. You have to do that manually after installation.

Default choice during installation of the SQL Server AlwaysOn Failover Cluster Instances

  • Default choice Install only.
  • You cannot use Install and configure (you can but the Reporting Services will not be confiured).

Validate configuration

  • Check Report Server website: http://<Server name>:<Port>/ReportServer_<Instance>
    • http://contsqlfcic0n0:80/ReportServer_SCSMD0
    • Reporting Services are not running.
        • http://contsqlfcic0n0:80/ReportServer_SCSMD0
    • Wrong or incomplete configuration
        • http://contsqlfcic0n0:80/ReportServer_SCSMD0
    • Proper configuration
        • http://contsqlfcic0n0:80/ReportServer_SCSMD0
  • Check Report Manager website. http://<Server name>:<Port>/Reports_<Instance>
    • http://contsqlfcic0n0:80/Reports_SCSMD0
    • Reporting Services are not running.
        • http://contsqlfcic0n0:80/ReportServer_SCSMD0
    • Wrong or incomplete configuration
        • http://contsqlfcic0n0:80/ReportServer_SCSMD0
    • Proper configuration
        • http://contsqlfcic0n0:80/ReportServer_SCSMD0

Configure Reporting Services

  • Run Reporting Services Configuration Manager
  • Connect to instance with Reporting Services feature.
      • CONTSQLFCIC0N0\SCSMD0
  • Service Account
    • Check that service account was set.
  • Web Service URL
    • Click to Apply.
  • Report Manager URL
    • Click to Apply.
  • Database
    • You can check that databases do not exist.
        • contsqlfcic0sd0.ad.contoso.com\SCSMD0
    • Change Database
    • Create a new report server database.
    • Select SQL cluster (not the SQL node).
        • contsqlfcic0sd0.ad.contoso.com\SCSMD0
    • You can leave the default name.
        • ReportServer
    • Select Service Credentials.
    • Finish
    • You can check that the DB was created.
« Previous Next »

Part of the series

  1. Building guest (virtual) Failover Cluster on Hyper-V host with Windows Server 2012 R2 - Part 1 - Create virtual machines
  2. Building guest (virtual) Failover Cluster on Hyper-V host with Windows Server 2012 R2 - Part 2 - Install and configure cluster
  3. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 1 - Design
  4. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 2 - Distributed Transaction Coordinator (MSDTC)
  5. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 3 - Configure storage and mount points
  6. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 4 - Install first node
  7. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 5 - Install second node
  8. Building Microsoft SQL Server AlwaysOn Failover Cluster Instances - Part 6 - Install another instance