Partager via

Today! (Cleaning up Reporting Services SharePoint Add-In Setup Problems)

  • Article

Some people have had problems during installation of the new Reporting Services Add-in for Microsoft SharePoint. If the add-in setup fails while to add the Reporting Services feature to the sites, some of your SharePoint sites will no longer work.  You can tell if the custom action failed by looking for a file named RS_SP_#.log in your %temp% directory.  If you have a log file there and your install failed, you will need to manually clean up your web.config files to get SharePoint up and running again.

First, you will need to locate the SharePoint virtual directories on your server.  Typically these are located at c:\inetpub\wwwroot\wss\VirtualDirectories. This folder contains several folders with names which are numbers representing the ports used by your SharePoint sites.  In each folder you will need to remove the following entries from the web.config file:

      <SafeControl Assembly="Microsoft.ReportingServices.SharePoint.UI.WebParts, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.ReportingServices.SharePoint.UI.WebParts" TypeName="*" />
      <SafeControl Assembly="Microsoft.ReportingServices.SharePoint.UI.ServerPages, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.ReportingServices.SharePoint.UI" TypeName="*" />
      <add verb="*" path="Reserved.ReportViewerWebPart.axd" type="Microsoft.ReportingServices.SharePoint.UI.WebParts.WebPartHttpHandler, Microsoft.ReportingServices.SharePoint.UI.WebParts, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
      <add verb="*" path="_vti_bin/ReportServer" type="Microsoft.ReportingServices.SharePoint.Soap.RSProxyHttpHandler, RSSharePointSoapProxy, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />

and

  <location path="_vti_bin/ReportServiceAuthentication.asmx">
    <system.web>
      <authorization>
        <allow users="*" />
      </authorization>
    </system.web>
  </location>

Once you remove these lines, save the file.  You must do this for every web.config file under the above directory.

To get around the issue, you need to add the user who is running setup as one of the Site Collection administrators before you run the setup. You can do this though the Site Adminstration page.

This is a known issue with our CTP2 setup and has been addressed in CTP3.

Comments

  • Anonymous
    December 06, 2006
    Is this THE Brian Welcker?If so, 'Howdy friend.'It's been a long time.
  • Anonymous
    December 10, 2006
    hii want to show the subreport's page header in the report. how can i do that?thanks.sorry, i do not konw your e-mail address, so wirte down here....
  • Anonymous
    December 11, 2006
    I have struggled with this issue for days!!!!!  Adding the user to the site collection admins did not help.  In the log, the last error is:  SSRSCustomActionError: Attempted to perform an unauthorized operation.-Very frustrated
  • Anonymous
    December 11, 2006
    OK....I got past that issue.....and I was so close.  The only thing not working is the content type for the Report Model will no import.  I've tried repairing the install, and still no luck.
  • Anonymous
    December 13, 2006
    I can't get throught he install of SharePointRS.msi. It says that SharePoint is not installed, which it is. There are no logs or explanations that I can find. Where do I go to get detailed installation instructions? Is there a newgroup or forum that might help?
  • Anonymous
    January 29, 2007
    The comment has been removed
  • Anonymous
    February 03, 2007
    After installing the SPS/MOSS &amp; SSRS integration add-in, I surfed to the Application Management page
  • Anonymous
    March 21, 2007
    Brian,I can deploy and run report in sharepoint server, but I can not find any report management actions such as Edit in Report Builder, Manage Subscriptions, Manage Data Sources, Manage Parameters and Manage Processing Options, etc. Could you please tell me why and how to fix?Thank you very much.Yanwen
  • Anonymous
    June 05, 2007
    The comment has been removed
  • Anonymous
    July 04, 2007
    trevor ct,go to Application Managment -> Site collection administrators, select the administration web application, and verify that your user is ther administrator of the site. Also check in the site that the user has full control (Site Actions -> Site Settings -> People and Groups).
  • Anonymous
    July 04, 2007
    trevor ct,I after that reinstall the Add-In.That resolves the problem.
  • Anonymous
    February 08, 2009
    I had the same problem today (so probably not with CTP2, whatever that is) and found several pages on how to resolve it, including this one.  The one that worked is here: http://www.venkat.org/2007/06/reporting-services-add-in-reportserver.html
  • Anonymous
    March 25, 2009
    I've been running into major problems with this latest attempt to install the RS Add-in (which I have done successfully on several other farms).  This error, which rolls back the installation, reads:"Unable to process .Cab file or Help Collection directory.  Cannot perform action."Anyone ever seen this one?  There doesn't seem to be much on the 'net referring to it.Thanks!Keith
  • Anonymous
    December 16, 2009
    The comment has been removed