none
SQL 2012 SP1 Reporting Services for SharePoint (2013) - Install-SPRSService Not Available

    Question

  • So, at this point, I've blown away an otherwise functional SP2013 + SQL2012SP1 multi-server farm trying to get this to work, only to end up with the same results. Irrespective of whether I install Reporting Services before or after the SP2013 server is in a farm, SSRS does not seem to be enabled in the farm. I cannot add a new SSRS service application (the menu item does not exist); I cannot start the SSRS service on server (because it isn't here); I cannot execute the Install-SPRSService cmd in SP (yes, the SharePoint) Powershell (PS comes back with this error:

    Install-SPRSservice : The term 'Install-SPRSservice' is not recognized as the
    name of a cmdlet, function, script file, or operable program. Check the
    spelling of the name, or if a path was included, verify that the path is
    correct and try again.
    At line:1 char:1
    + Install-SPRSservice
    + ~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Install-SPRSservice:String) [],
        CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

    ).

    Quite simply, something's broken. I've followed a couple of detailed how-to's on technet and elsewhere... Right at the point when I should be able to create the SSRS service application, the wheels come off the cart. I've tried Import-Module'ing the SQLCMDLETS and SQLPS PS modules...nothing... The strange thing is that after the installation of the SSRS, if I happen to go into the General Application Settings in Central Admin, I see a new item after Content Deployment:

    $Resources:ReportServerResources,AdminReportServerGroupTitle; 

    $Resources:ReportServerResources,ManageIntegrationSettings;

    $Resources:ReportServerResources,AddTrustedAccounts;

    $Resources:ReportServerResources,SetServerDefaults; 

    When I uninstall, this goes away.

    Greatly appreciate any suggestions you can offer because this is driving me crazy, and I have tried everything I can think of to get this going...


    Tuesday, November 20, 2012 7:04 AM

Answers

  • In a land where stories aren't so much funny ha-ha as they are funny I-wish-I-could-get-those-5-days-of-my-life-back-but-never-will...

    Apparently SQL 2012 with SP1 doesn't yield an SQL 2012 server with SP1 when installed... Installing SP1 AFTER installing SQL "with SP1" resolves the issue. Hope no one else wastes their time like I have...

    • Marked as answer by artemico Sunday, November 25, 2012 6:10 AM
    Sunday, November 25, 2012 6:10 AM

All replies

  • Make sure you are running SharePoint 2010 Management Shell not PowerShell.

    Also make sure you are running SharePoint 2010 Management Shell with administrator privileges. Right click the icon and click, "Run As Administrator".

    You must have installed "Reporting Services add-in for SharePoint Products" on the server where you are executing "Install-SPService".

    You also may be interested to check this tutorial: Install Reporting Services SharePoint Mode for SharePoint 2013

    Tuesday, November 20, 2012 2:26 PM
  • Yes, I am running the SP 2013 power shell, and I'm running it as administrator...
    Tuesday, November 20, 2012 6:00 PM
  • And, yes, I've installed that from the SQL2012SP1 ISO and yes, I used the tutorial you reference as one of the guides for installing in the first place.

    Tuesday, November 20, 2012 6:01 PM
  • Having the exact same problem on multi-server farm, only I'm not using SP1 for SQL2012.  ......sigh.

    Tuesday, November 20, 2012 8:16 PM
  • So...I downloaded SQL 2012 SP1 CTP4 and ran the upgrade for the SSRS pieces on my SharePoint box, and that fixed my issue with not being able to run SPRSService etc.

    You can download CTP4 at http://www.microsoft.com/en-us/download/details.aspx?id=34700

    hope this helps.

    • Proposed as answer by rockit Tuesday, November 20, 2012 9:16 PM
    • Unproposed as answer by artemico Sunday, November 25, 2012 3:23 AM
    Tuesday, November 20, 2012 9:15 PM
  • Why would I use CTP4 of SP1 when I've got SP1...?
    Wednesday, November 21, 2012 6:41 PM
  • In a land where stories aren't so much funny ha-ha as they are funny I-wish-I-could-get-those-5-days-of-my-life-back-but-never-will...

    Apparently SQL 2012 with SP1 doesn't yield an SQL 2012 server with SP1 when installed... Installing SP1 AFTER installing SQL "with SP1" resolves the issue. Hope no one else wastes their time like I have...

    • Marked as answer by artemico Sunday, November 25, 2012 6:10 AM
    Sunday, November 25, 2012 6:10 AM
  • Installing SP1 after installing SQL 2012 will only lead to more heart ache as msiexec will totally chew up your RAM. I have been struggling with this ALL DAY. No fix yet, if you want Management Tools that is.

    MS for the WIN!!

    Tuesday, November 27, 2012 1:08 AM
  • Thank you this did the trick. Saved me 4 days.
    Monday, December 03, 2012 11:00 PM
  • That did it, but only after I reboot the server when SP1 was done installing.  So far you have saved 8 days.
    Tuesday, December 04, 2012 8:25 PM
  • This is because the ISO for SQL Server 2012 with SP1 that was released on November 8th does not install SP1.

    http://support.microsoft.com/kb/2783963?wa=wsignin1.0

    If you downloaded the ISO prior to November 27, it means you have a BAD ISO VERSION.

    The good news is that we weren't going crazy...

    • Proposed as answer by ategethoff Friday, February 01, 2013 8:24 PM
    Tuesday, December 11, 2012 1:05 AM
  • Are you sure that you do need "Reporting Services add-in for SharePoint Products"  According to the installation it says you don't need to install it on the SharePoint Application Server just the WFE.  I wonder if Microsoft made a mistake in their doc?

    http://msdn.microsoft.com/en-us/library/c1a6b683-15cf-44ae-ac60-ceee63a60aaf

    "If the server will only be used as an application server and the server will not be used as a WFE, you do not need to select Reporting Services add-in for SharePoint products"

    Does this mean if you have a 3 tier SharePoint       SQL , App and WFE that you'd install  just the "Reporting Services - SharePoint" on the Application Server and the "Reporting Services-Add-in for SharePoint Products" on the WFE server and which would mean you'd only run the "install-SPRSService" & "install-SPRSSerivceProxy" on the WFE?

    Really surprise that MS only has complete step-by-step docs on single server deployments and only incomplete notes on scale-out deployments which is probably more wildly used for most enterprises.

    Friday, January 25, 2013 10:35 PM
  • I can't believe the amount of time and heartache I've spent on trying to figure this out.

    I won't thank you guys for saving me any time, but I will thank you for saving my sanity!!!!

    Friday, February 01, 2013 8:24 PM
  • To remind you guys: Install the SQL DVD version WITH SP1! otherwise the SPRS SharePoint integration will not work. And also the PowerPivot is missing!

    I had to uninstall SQL on the WFE and install the SQL with SP1 DVD. Uninstalling gave me a failure that Reporting Services - SharePoint could not be removed due to the cmdlet uninstall SPRSServiceProxy is not recognized... Why giving me this message while installing and with the uninstall? (I was not able to solve this issue)

    My goal integrating SPRS SQL 2012 with SharePoint 2013 (SQL and WFE server).

    Mount the .iso and run the SQL 2012 SP1 installer with the SharePoint farm account. Select the SharePoint integration feature and run the install-sprsservice and sprsserviceproxy (as the administrator in the SharePoint management Shell). Start the SQL Server Reporting Services Service in CA and configure from there.

    Took me 2 1/2 days :(
    Hope this helps you saving some time like the other posts above.
    Amancio

    Monday, April 15, 2013 8:05 AM
  • This was the perfect solution for me! I was having the same issue...

    All I had to do was install everything as instructed, then ran the few lines of script.

    Thank you!

    Monday, October 28, 2013 5:40 PM