Installing SQL Server Reporting Services (SSRS) 2012 integrated mode with SharePoint 2013

Reporting services 2012 integrated with SharePoint 2013

In this post I’m going to describe installing SSRS 2012 integrated mode with SharePoint 2013. As some guys are pretty new to SSRS 2012 or SharePoint or even SSRS integrated with SharePoint, I am explaining the situation from scratch.

Requirements:

Note: Reporting services will not install on standard or express editions

  • Windows Server 2008 or later

Note: You can download Windows Server days trial from here: Windows Server Free Trial | Microsoft

Note: SharePoint 2013 is available only in 64-bit version, so you need a 64-bit operating system.

Getting started:

Follow the instruction below to start installing Reporting Services 2012 integrated with SharePoint 2013:

  1. Install SQL Server Enterprise edition:

a. Select Database engine services

b. Management tools – Basic

c. Management tools – Complete

clip_image002

  1. After SQL Server 2012 installation completed its time to start installing SharePoint Server 2013 Preview

a. Run SharePoint 2013 software prerequisites. Please note, if running software prerequisites failed, just right click on “setup.exe” in installation media and select “Run as administrator” and click “Install software prerequisites” again.

clip_image004

clip_image006

b. For some reason (that it is not clear for me!) you may have to restart your machine again after installation of prerequisites completed. This will happen especially when you try to install SharePoint on Windows Server 2012.

c. After restarting run setup again and click “Install SharePoint Server” and complete installation process.

d. Open SharePoint product configuration wizard and select “Create a new server farm”.

clip_image008

e. Set the database server, use installed SQL Server database server installed before (wait for setup to complete)

clip_image010

f. Specify Farm security settings

clip_image012

g. Configure SharePoint Central Administration Web Applicationclip_image013

It is better to specify a port number here otherwise it may have some conflicts with IIS default website (port 80).

h. Completing the SharePoint products configuration wizard clip_image015

i. Configuration Successful

clip_image017

SharePoint is now installed and ready to use.

3. Install SSRS 2012 in SharePoint integration mode:

Select “Reporting Services – SharePoint” and “Reporting Services Add-in for SharePoint Products” from features-> Shared Features

clip_image019

  1. Install SQLServer2012SP1-KB2674319-x64-ENU and Microsoft SP1 for Power Pivot (from here: http://www.microsoft.com/en-us/download/details.aspx?id=35577), otherwise the commands in the next steps in SharePoint Server 2013 Shell will fail

  2. Open SharePoint Server 2013 Shell in run as administrator mode and run the following commands:

Install-SPRSService (will install SharePoint Reporting Services)

Install-SPRSServiceProxy (will install service proxy)

get-spserviceinstance -all |where {$_.TypeName -like “SQL Server Reporting*”} | Start-SPServiceInstance (will start the service)

We can also start the service from SharePoint central Administration rather than running the third PowerShell command. The following steps are also useful to verify that the service is running.

  • Open SharePoint Central Administration
  • Click “Manage Services on Server” in the “System Settings” group
  • Find “SQL Server Reporting Services Service” and click Start in the Action column. The status of the Reporting Services service will change from “Stopped” to “Started”.
  • If the Reporting Services service is not in the list, use PowerShell to install the service
  • Verify that the service is started in “SharePoint Central Administration” –> “Application Management” –> “Service Applications” –> “Manage Services on Server” and now look for the “SQL Server Reporting Services Service” to see if it is now configured and is running.

clip_image021

  • Create a new “SQL Server Reporting Services Application” in “SharePoint Central Administration” –> “Application Management” –> “Service Applications” –> “Manage Service Applications” and create a new “SQL Server Reporting Services Application”.

clip_image022

  • Specify a name for the application, create a new application pool, and specify the database server name. Down below you will also need to select the web application to associate this application with and I used the “Windows Authentication” for the database authentication.

Now we should see “Reports Library” in our site. If not, we need to make sure if “Enterprise Features” in “Site Collection” level is activated as well as site level.

To do so:

  • Select Site Settings-> Site Actions-> Manage site features-> SharePoint Server Enterprise Site features

clip_image024

  • To activate it in site level we need to activate the “SharePoint Server Enterprise Site Features” in “Site Collection” level. To do so select Site Settings-> Site Collection Administration-> Site collection features-> SharePoint Server Enterprise Site Collection features

clip_image026

  • Now go to Site Contents-> add an App clip_image028-> Report Library clip_image030
  • OK. It’s done now.[1]

[1]Reference: http://denglishbi.wordpress.com/2011/07/22/configuring-sql-server-denali-reporting-services-sharepoint-2010-integration/

2 thoughts on “Installing SQL Server Reporting Services (SSRS) 2012 integrated mode with SharePoint 2013

  1. Under requirements, you made a Note: “Reporting services will not install on standard or express editions”. Is this sharepoint requirement to have SQL Enterprise/Business Intelligence edition ?

    1. Hi Kumar,

      Welcome to BIInsight.com.
      Thanks for bringing this very old post from 2013 to my attention.
      It’s good to remember the old days though.
      Look, if I recall correctly, SSRS Integrated with SharePoint was only available in Enterprise/Standard editions of SQL Server 2012.

      Hopefully that helps.
      Cheers.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.