RS SharePoint Integration

  • Error installing rsSharePoint.msi on Windows 2008

    When installing the rsSharePoint.msi on Windows 2008 you need to ensure you run it with "Run As Administrator".

    Having said that, in multi-machine scenarios you may run into an error along the lines “Insufficient SQL database permissions for user ‘SYSTEM’ in database Sharepoint_AdminContent_<guid>….". The root cause, is on Windows 2008 or higher version OS's rsSharePoint.msi run its custom action (rscustomaction.exe) to install and active the RS feature in SharePoint as SYSTEM, which is known to fail in multi-machine scenarios.

    Here is the means to workaround this issue:

    1. Open a command prompt with “Run as Administrator…”
    2. Run rsSharePoint.msi SKIPCA=1.
    3. Locate rsCustomAction.exe file on the file system. This file is copied to your computer by rsSharePoint.msi and is generally located in the %Temp% directory.
    4. Run rsCustomAction.exe /i

    We are currently working on fixing this issue in rsSharePoint.msi within the SSRS 2008 R2 timeline.

     

    HTH

    Prash

    Posted Tuesday, September 01, 2009 5:36 PM by Prash Shirolkar | 0 Comments

  • Passing URL report parameters to Reports in SharePoint Document Library in SSRS 2008

    Passing URL report parameters directly to a report in a SharePoint Document Library is enabled in the SQL Server Reporting Services 2008 Integration with SharePoint Add-in.

    Why? Key intent is to allow specifying non-default report parameter values when rendering of a report in full-page view in SharePoint.  

    How do you use this feature? Simply add-on the URL report parameters onto the URL displayed in SharePoint when viewing a report in full page view. 

    Examples: Here are examples using the Adventureworks sample reports assumed to be stored in SharePoint document library: http://<SharePoint_site>/Reports/ReportsLibrary

    ·         Render the AdventureWorks "Employee Sales Summary" report for 'Syed Abbas' for 'January' / '2004' with ReportViewer Toolbar showing pagination only: http://<SharePoint_site>/Reports/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/Reports/ReportsLibrary/Employee%20Sales%20Summary.rdl&rv:ToolBar=Navigation&rp:EmpID=288&rp:ReportMonth=1&rp:ReportYear=2004

    ·         Render the AdventureWorks 'Product Catalog' report with the Document Map Area collapsed and no Header Area: http://<SharePoint_site>/Reports/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/Reports/ReportsLibrary/Product%20Catalog.rdl&rv:HeaderArea=None&rv:DocMapMode=Collapsed

    ReportViewer parameters for controlling full-page report rendering

    ReportViewer Parameter

    Description

    Values

    rv:HeaderArea

    Control how the ReportViewer web part’s header is displayed in full-page view.

    Full, None.

    Default: Full

    rv:ToolBar

    Control how the ReportViewer web part’s toolbar is displayed in full-page view.

    Full, Navigation, None.

    Default: Full

    rv:ParamMode

    Control how the ReportViewer web part’s header is displayed in full-page view.

    Full, Collapsed, Hidden.

    Default: Full

    rv:AsyncRender

    Control whether the report is rendered asynchronously or synchronously.

    true, false.
    Default: true

    rv:DocMapAreaWidth

    Control the display width in pixels of the ReportViewer web part’s Document Map area.

    Non-negative integer

    rv:DocMapMode

    Control the display of the Document Map area of a report.

    Displayed, Collapsed, Hidden.
    Default: Dislayed

     
    Posted Wednesday, January 21, 2009 5:32 PM by Prash Shirolkar | 1 Comments

  • Enabling ReportBuilder for launching from a SharePoint Doc. lib when using Forms or Basic Authentication

    A] Forms Authentication

    1. If using SQL 2005 SP2 make sure you have installed the sharepointrs.msi that includes the following fix http://support.microsoft.com/kb/939942/ else move onto step2.
    2. Add the following entries to the Web.config file for the SharePoint web application you want to enable launching of Report Builder:
      <location path="_vti_bin/ReportBuilder/ReportBuilder.application">
        <system.web>
          <authorization>
            <allow users="*" />
          </authorization>
        </system.web>
      </location>
      <location path="_vti_bin/ReportBuilder/ReportBuilder.exe.manifest">
        <system.web>
          <authorization>
            <allow users="*" />
          </authorization>
        </system.web>
      </location>
      <location path="_vti_bin/ReportBuilder/ReportBuilder.chm.deploy">
        <system.web>
          <authorization>
            <allow users="*" />
          </authorization>
        </system.web>
      </location>
      <location path="_vti_bin/ReportBuilder/ReportBuilder.exe.deploy">
        <system.web>
          <authorization>
            <allow users="*" />
          </authorization>
        </system.web>
      </location> 
    3. For non-English sites ensure you add the appropriate appropriate LCID and Culture entries as well to the Web.config file. For example enabling for launching in Japanese in addition to English (in Step 2) add the following:
      <location path="_vti_bin/ReportBuilder/1041/ReportBuilder.chm.deploy">
        <system.web>
          <authorization>
            <allow users="*" />
          </authorization>
        </system.web>
      </location>
      <location path="_vti_bin/ReportBuilder/ja/ReportBuilder.resources.dll">
        <system.web>
          <authorization>
            <allow users="*" />
          </authorization>
        </system.web>
      </location>
      For details on LCIDs and Cultures supported by the Reporting Services Add-in for SharePoint refer to "Supported Languages" section @ http://technet.microsoft.com/en-us/library/aa905871(SQL.90).aspx or the install folder under %programfiles%\Common Files\Microsoft Shared\web server extensions\12\ISAPI\ReportBuilder.
    4. Enable anonymous access on the ReportBuilder folder via IIS manager. For more information, see "How to Enable Anonymous Access on the ReportBuilder Folder" section @ http://msdn.microsoft.com/en-us/library/ms365173(SQL.90).aspx

    A known error you can run into if not setup correctly is "Cannot Start Application. Cannot continue. The application is improperly formatted. Contact the vendor for assistance."

    B] Basic Authentication

    1. If using SQL 2005 SP2 make sure you have installed the sharepointrs.msi that includes fix #50001712 from http://support.microsoft.com/kb/941450 else move onto step2.
    2. If users encounter an HTTP 401 or 400 when launching ReportBuilder then you need to ensure users select the "Remember Password" checkbox when you are provided the user credentials dialog at login time. The root cause is that the login / authentication via the user credential dialog box results in SharePoint creating a WSS_KeepSessionAuthenticated cookie to ensure this user remains authenticated for the duration of their session. ReportBuilder is launched usingClick-once, which is not aware of nor supports using this WSS_KeepSessionAuthenticated cookie resulting in the error from SharePoint during launch of ReportBuilder.
    Posted Tuesday, October 21, 2008 6:54 PM by Prash Shirolkar | 0 Comments

  • Better late than never - A PG site for SSRS integration with SharePoint

    I am aware and painfully so that a PG blog / site dedicated to SSRS integration with SharePoint has been long overdue. Hence, for my initial post I have compiled a short list of some unanswered questions I have seen from blogs / newgroups etc. on this subject. Feel free to send me your issues / thoughts on RS integration with SharePoint and I will try as best to answer / address them and post new blogs as and when required. I hope you find this helpful.

    1. Is it possible to integrate SQL Server Reporting Services with WSS3 not MOSS ? Additionally, Is it possible to run Sharepoint Services and SQL Reporting Service on Windows 2003 X64?
      Yes it supports both WSS 3.0 and MOSS 2007. Additionally it is supported on x86 and x64. For details refer to Requirements for Running Reporting Services in SharePoint Integrated Mode
    2. Does RS integrate with a SharePoint WFE using Forms or Basic Authentication?
      Yes, it does. Make sure you install Forms auth hotfix 939942 and the Basic auth hotfix 50001712 for the RS 2005 SP2 Add-in for SharePoint.
    3. Does Reporting Services support Alternate Access Mappings (AAM)? If not, then what are the alternatives?
      Reporting services only supports access via the default zone in AAM. You will get an error along the lines  "The specified path refers to a SharePoint zone that is not supported" if you try to access a report from a non-efault zone. You can consider a workaround wherein multiple “Internal URLs” (Internet, intranet, etc.) for the same web application use a single “Public URL for Zone” all in the AAM default zone. Full AAM support is being considered for the next version post-SSRS 2008.
    4. Is there support for Reporting against SharePoint lists?
      SSRS does not natively ship a SharePoint Lists data extension as yet. Here are option that may want to consider:
      • Using the out-of-the XML data extension to read and wrtie to a SharePoint via the GetListItems and SetListItems methods of the SharePoint List web service. I have attached a TicTacToe.rdl report that I demo'd @ TechEd / TechReady. This report reads from and writes to a SharePoint list by the name oif TicTacToe.  
      • Other third-party solutions like Enesys RS data extension
      • Develop a custom solution such as this blog from Teun Duynstee.
    5. How do I fix the "User cannot be found" error?
      This is a bug in wherein if the author /creator / publisher of a report is deleted from the site in which the report resides. Possible workarounds can be found in "User Cannot be found" RS Forum thread. We are working on releasing a hotfix #50003017 with the upcoming SQL 2005 SP2 CU to fix this issue.
    6. Which authentication modes should I use - Windows Integrated or trusted account?
      Only use Windows Integrated for Kerberos enabled environments and in single-box deployment scenarios. For the rest use Trusted Account mode. In the scenario wherein you are having trouble setting-up Kerberos you should consider using Trusted account mode to at least setup and verify RS integration with SharePoint works. Once you have fixed your Kerberos issues then you can choose to switch to using Windows integrated.
    7. How do I fix the error message "The report server cannot access settings in the Sharepoint configuration database.  Most likely, the Windows Sharepoint Services object model is not installed..."?
      This is generally noticed in a multi-machine scenario when SharePoint WFE and RS are on separate machines. Make sure you install the minimum SharePoint install on the SSRS machine. For details refer to How to: Configure SharePoint Integration on Multiple Servers
    8. Is Reporting Services Integration with SharePoint supported on SQL Server Express SKUs?
      No it is only supported on Standard and higher SQL SKUs. There are no plans to include it is Express SKUs. For the details refer to the SSRS feature matrix.
    9. I am trying to get this working on a domain controller and the "grant database access" step always fails with "A new member could not be added to a local group because the member has the wrong account type"?
      Make sure your Report Server services accounts are domain accounts on a DC, else you will get this error when try to to add them to the local WSS_WPG group.
    10. I have a MOSS 2007 site set up on "localhost" and RS 05 is running in native mode.How can I view the reports in sharepoint webparts on the site?
    11. How to publish to SharePoint document library via Report Designer? 
      Make sure you have SQL 2005 SP2 BIDS when deploying to SSRS 2005 SP2 and the following project properties set to absolute paths:
      TargetDataSourceFolder http://<SharePoint_site>/<SharePoint_Doclib>
      TargetReportFolder http://<SharePoint_site>/<SharePoint_Doclib>
      TargetServerURL: http://<SharePoint_site>
      If you have issues deploying to a SharePoint site that uses Forms Authentication mode then consider posting directly to the Report Server by changing TargetServerURL to:
      TargetServerURL: http://<server_name>:<port>/<ReportServer_VDIR>
      For details refer to How to: Publish a Report to a SharePoint Library from Report Designer 
    12. What do I do when I get "User does not have permission to add feature to site collection" when installing the RS Add-in for SharePoint msi?
      Locate the installation log created by the RS Add-in msi in the Temp folder - <Drive>:\Documents and Settings\<user_name>\Local Settings\Temp\RS_SP_<number>.log file. Next you should be able to locate log entries along the lines:  

      Activating feature to root site collection: <sharepoint_site_collection>
      ******* User does not have permission to add feature to site collection: <sharepoint_site_collection>

      This means that the RS integration feature was installed however the feature may not be activated for the <sharepoint_site_collection>, because the user who ran the msi wasn't a site collection admin. In order to view the RS integration feature in the site you need the site colection administrator to activate the Report Server feature. 
    13. When I try to access a report thru the MOSS Site I get an internal catalog exception near GetSystemPropertiesAction() but it works just fine when I access it directly from the report server URL?
      This is may happen when there are multiple Central Administration sites in a SharePoint Farm. Verify this by checking whether you see multiple URLs for “Central Administration” Alternate Access Mappings Collection under Central Administration -> Operations -> Alternate Access Mappings. If this is the case, then browse to the Report Server URL directly and determine the http://<server_name>/ in the SharePoint sites listed. Ensure the URL containing this <server_Name> is first in the list of URLs for the "Central Administration" group under Central Administration -> Operations -> Alternate Access Mappings. This issue has been fixed in SSRS 2008 RC0.
    14. What are some newer whitepapers related with RS integration?
      SQL Server 2005 Integration with Microsoft SharePoint Products and Technologies
      Troubleshooting Integration with SQL Server 2005 and Microsoft SharePoint Technologies
    Posted Saturday, August 02, 2008 1:52 AM by Prash Shirolkar | 4 Comments

    Attachment(s): TicTacToe.rdl

This Blog

Syndication

Tags

No tags have been created or used yet.

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker