After 4hrs searching the web for an answer why I couldn’t find the three report content types were not showing up after installing the Reporting server Add-in for SharePoint 2013 and finally found a way to bring them back.
I noticed a change on how you install the RS SharePoint add-in for SharePoint 2013. Its now a component in SQL Server 2012 rather than a SharePoint prerequisite via the installer and my experience having to use the SQL Server 2012 installation wizard to add/remove this component was a slow and painful and didn’t fix this issue.
So i found a quicker and better way to bring them back!
Note: When you install RS SharePoint Add-in feature to your Web Front end servers using the SQL Server 2012 and Service Pack 1 media you wont see any errors about the content types not installing correctly.
Symptoms:
No Report Builder Model, Report Builder Report or Report Data Source content types listed when you Add Content Types to your document library and the Report Server Integration Feature is Activated
You at attempt to deactivate and re-active the “Report Server Integration Feature” (E8389EC7-70FD-4179-A1C4-6FCB434) for your site collection feature via PowerShell or the GUI.
Enable-SPFeature -Identity E8389EC7-70FD-4179-A1C4-6FCB434
2D7A0 -Url http://sharepoint/
Error:
Enable-SPFeature : The Feature is not a Farm Level Feature and is not found in
a Site level defined by the Url http://sharepoint
Server Topology:
- SQL Server 2012 with Service Pack 1 (hosts SharePoint databases)
- SharePoint 2013 Application Server (Hosts Reporting services service application)
- SharePoint 2013 Web Front end Server (hosts the all content websites)
Resolution:
1. So what is extracted the file rsSharePoint.msi from the SQL Server 2012 Service Pack 1 x64 binaries.
- Name: rssharepoint.msi
- Author: Microsoft Corporation
- Revision Number: {D99F505C-205A-4063-B08B-1769D140AA42}
2. Copy the rssharepoint.msi to your local drive and extract the msi package.
Msiexec.exe /i rsSharePoint.msi SKIPCA=1
- Open a command prompt with administrator permissions and run a files only installation as described in the previous section.
- Find the rsCustomAction.exe file on the file system. This file is copied to your computer by the Setup program. The file will be located in the %Temp% directory. To get the path information for this file, Type the following from the command prompt:
- CD %temp%.The file should be located in: \Users\<your name>\AppData\Local\Temp
- Type the following command. This configuration step will take several minutes to finish. The W3SVC service will be restarted during this process. Several Status messages will be displayed as the program copies files, registers components, and runs the SharePoint Product Configuration Wizard.
-
rsCustomAction.exe /i
SharePoint Products Configuration Wizard version 15.0.4420. 1017.Copyright (C) Microsoft Corporation 2012. All rights reserved.
2012-12-20 16:25:58: copyappbincontents command completed successfully.
2012-12-20 16:26:19: Adding ReportServer feature to farm.
2012-12-20 16:26:20: Installed ReportServer feature.
2012-12-20 16:26:40: Adding ReportServer feature to farm.
2012-12-20 16:26:40: Installed ReportServer feature.
2012-12-20 16:27:00: Adding ReportServerStapling feature to farm.
2012-12-20 16:27:00: Installed ReportServerStapling feature.
2012-12-20 16:27:20: Adding ReportServerStapling feature to farm.
2012-12-20 16:27:20: Installed ReportServerStapling feature.
2012-12-20 16:27:40: Adding ReportServerItemSync feature to farm.
2012-12-20 16:27:40: Installed ReportServerItemSync feature.
2012-12-20 16:28:00: Adding ReportServerItemSync feature to farm.
2012-12-20 16:28:00: Installed ReportServerItemSync feature.
2012-12-20 16:28:20: Adding ReportServerCentralAdmin feature to farm.
2012-12-20 16:28:23: Installed ReportServerCentralAdmin feature.
2012-12-20 16:28:43: Adding ReportServerCentralAdmin feature to farm.
2012-12-20 16:28:43: Installed ReportServerCentralAdmin feature.
This process can take up to about 5-10mins, so be patient.
IISRESET and you should see the content types have reappeared.
SharePoint 
Great stuff, from all the blog posts out there, this actually is the only one that makes sense and helped me solve this nasty problem! Thanks a lot!
I get
SSRSCustomActionError: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\psconfig.exe return error code: -1
Any ideas?
Do you get the same result when running psconfig.exe in Administrator mode in SharePoint PowerShell Window?
Chris.
Yes
Begin all troubleshooting efforts with installs and upgrades by looking at the logged output which can normally be found wherever your ULS directory is defined.
Good. this is also documented in the files only installation of the TechNet topic “Install or Uninstall the Reporting Services Add-in for SharePoint” http://technet.microsoft.com/en-us/library/aa905871.aspx
Great guide – I had to run rsCustomAction -u, and then iisreset before running the install to get this to work, but it did so afterwards just fine.
Thanks!
Great stuff, from all the blog posts I saw,
this actually is the only one that makes sense and helped me solve this nasty problem! Thanks a lot!
Thx!
THANK YOU!!! I have spent 3 days and only your article helped me!!!
After more than a week kicking my head on the table and telling myself, I should have chosen a different career, I finally find this. This has been the one that helped me.
THANK YOU!!! This has been a big problem for us. I went as far as to delete the whole web application, content database and IIS Web Site and couldn’t get Reporting services to activate on just this one Web Application. I also had to Uninstall and reinstall using the -u and then -i switches. This might be caused from adding a new IIS Web site\Web Application after deploying reporting services. I don’t have the time to try and reproduce this. Sorry.
get-spfeature -identity reportserver # if compatability is 14 this might be the problem/it should be 15
install-spfeature -path reportserver -compatibilitylevel 15
deactivate feature in site then
$site = get-spsite “http://”
Enable-SPFeature -Identity ReportServer -Url $site.url
Thank you sir you really solved my problem