RS SharePoint Integration

I do not see the SSRS Shared Service in SharePoint CA after installing SSRS "Denali" CTP SharePoint mode

Prash Shirolkar - MSFT — Fri, 01 Jul 2011 00:51:00 GMT

After successfully installing the latest SSRS "Denali" CTP SharePoint mode Service and SSRS "Denali" Add-in for SharePoint 2010, if you do not see "SQL Server Reporting Services" in the Service or Service Application list:

SharePoint 2010 Central Admin -> "Application Management" -> "Manage Services on Server" OR
SharePoint 2010 Central Admin -> "Application Management" -> "Manages Service Applications" -> Click on "New" menu

Then it is likely the SSRS Shared Service did not get registered with SharePoint correctly at the time of installation. This state is also expected behavior if SSRS SharePoint mode was installed before the SharePoint installation.

Work Around

To register and start the SSRS SharPoint Service, complete the following:

On the computer that runs SharePoint 2010 Central Administration:

Open a PowerShell command prompt with administrator privileges. Right click the icon and click, "Run As Administrator". Run the following cmdlets from the shell:

Add-PSSnapin Microsoft.SharePoint.PowerShell
Install-SPRSService
Install-SPRSServiceProxy
Get-SPServiceInstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance

Verify the SQL Server Reporting Services Service Instance shows status as "Started" on the SharePoint 2010 Central Admin -> "Application Management" -> "Manage Services on Server" page.

HTH

Performance of SSRS in SharePoint mode reports in full-page view in SharePoint 2010.

Prash Shirolkar - MSFT — Sat, 11 Jun 2011 02:19:00 GMT

Using SSRS in SharePoint mode version 2008 R2 or earlier full-page report rendering is slower than its corresponding Native mode. This is largely due to SSRS in SharePoint mode comprises Native mode functionality and additional calls to the SharePoint object model APIs for SharePoint integration specific operations. Additionally, for some reports with short Native mode rendering times especially those less than 500ms or 1s can be found to be 2-3 times slower in SharePoint mode when compared to a typical Native mode SSRS install. This can also be inferred / approximated from the "First Page Report Performance" graph in the Reporting Services Performance in SharePoint Integrated Mode in SQL Server 2008 R2.

In the SQL Server Denali CTP3 of SSRS Reporting Services for SharePoint 2010 we have improved our integration with SharePoint 2010 which truly improves performance. This entailed changes and optimizations for the end-to-end full-page report viewing / rendering scenario starting with the SSRS Report Viewer SharePoint web part’s behavior such as in its toolbar, followed by communication between the web part and the back end server, and the interaction between SSRS components and SharePoint itself. As a result of this, in SharePoint mode full-page report rendering is either at par if not very close at par (differ by fractions of a second) with Native mode.

Hence, how do you get this performance improvement?

For maximum benefit of this performance improvement use the CTP3 (or later) SSRS Denali CTP Add-in for SharePoint 2010 with the SSRS Denali CTP3 (or later) report server.
For SSRS 2008 or SSRS 2008 R2 report server in SharePoint mode scenarios, the recommendation is to upgrade to the SSRS Denali CTP3 (or later) Add-in for SharePoint 2010 from the SSRS 2008 R2 Add-in for SharePoint 2010. SSRS Denali CTP3 (or later) Add-in for SharePoint 2010 supports full backward compatibility with SSRS 2008 and SSRS 2008 R2 report server in SharePoint mode.

Visit the SQL Server Code name Denali CTP3 site and to download. Send feedback via http://connect.microsoft.com as well.

Migrating SSRS 2008 R2 SharePoint mode from one SharePoint Farm to another

Prash Shirolkar - MSFT — Sat, 11 Jun 2011 00:49:00 GMT

In general, master copies of SSRS Content types items like Reports (.rdl), data sources (.rsds), semantic models (.smdl) etc. are stored in the SharePoint content DB and cached on-demand by SSRS in the RS catalog. Additionally, report / data source metadata like subscriptions, schedules, snapshots, stored credentials etc. are exclusively stored in the RS catalog. Having said that, all these reporting items stored or cached within the RS catalog are associated / linked with where they are stored in SharePoint. These associations generally comprise the SharePoint site GUID, relative paths wrt to the SharePoint root site, etc. Hence, in general a large portion of data stored in the Report Server catalog DB in SharePoint mode is relative to or dependent on SharePoint content/ sites. As a result, simply migrating the backed up reporting services database into another SharePoint farm is not going to work in every case.

SSRS migration (with backup and restore) needs to be step-by-step with SharePoint configuration / content DB migration. Hence the best practice / supported means:

When the entire SharePoint farm with its content DBs as well is migrated to a new SharePoint Farm then you should consider migrating the SSRS catalog DBs as well via steps identified at SSRS migration (with backup and restore).
When only SSRS DBs are being migrated from one SharePoint farm to a completely different farm without also migrating all the SharePoint content DBs, then RS catalog DB migration is not the recommended nor supported means. The right means in this case is migrate the SSRS data using tools like rs.exe utility in SSRS 2008 R2.

Configuring Kerberos Authentication for SSRS 2008 R2 with SharePoint 2010.

Prash Shirolkar - MSFT — Thu, 15 Jul 2010 19:20:27 GMT

A new whitepaper is being released today on "Configuring Kerberos Authentication for Microsoft SharePoint 2010 Products". Scenario #4 comprises specifics on setting this up with SQL Reporting Services entailing - dependencies, checklist, step-by-step instructions etc. Hope you find this whitepaper and Scenario #4 helpful. Looking forward to your feeedback on this.

Happy Kerberos configuration in RS SharePoint integration mode!

thanx,
Prash

Steps to consider when Upgrading from SharePoint 2007 to 2010 with Reporting Services in SharePoint mode

Prash Shirolkar - MSFT — Wed, 26 May 2010 20:36:00 GMT

Had multiple folks ask this question and there does not seem to be targeted docs as yet in this regard, hence decided to blog on this. Hope you find it helpful.

If you need to in-place Upgrade to SharePoint 2010 then here are the recommended sequence of steps to take with
Starting state: SharePoint 2007, SQL Server 2008 Add-in and SQL Server 2008 Report Server
1. Run SSRS 2008 SP1 CU8 (or higher) installer on all SSRS in SharePoint mode machines, details and download of SP1 CU8 @ http://support.microsoft.com/kb/981052
2. Run the SharePoint 2010 pre-requisite installer on all SharePoint 2007 WFEs. This should install SSRS 2008 R2 Add-in for SharePoint 2010 which should perform an in-place upgrade from the previous Add-in,
3. Run SharePoint 2010 setup on all SharePoint 2007 WFEs and Report Server machine(s).

Ending state: SharePoint 2010, SSRS 2008 R2 Add-in, SSRS 2008 Sp1 + CU#8 Report Server

If you need to in-place Upgrade to SharePoint 2010 and SSRS 2008 R2 Report Server then here are the recommended sequence of steps to take with
Starting state(s): SharePoint 2007, SQL Server 2008 Add-in and SQL Server 2008 Report Server
1. Run SSRS 2008 R2 setup on existing SSRS Report Server instances. This should perform an in-place upgrade of the existing report server instance to SSRS 2008 R2.
2. Run the SharePoint 2010 pre-requisite installer on all SharePoint 2007 WFEs. This should install SSRS 2008 R2 Add-in for SharePoint 2010 which should perform an in-place upgrade from the previous Add-in,
3. Run SharePoint 2010 setup on all SharePoint 2007 WFEs and Report Server machine(s).

Ending state: SharePoint 2010, SSRS 2008 R2 Add-in, SSRS 2008 R2 Report Server

For SQL Server 2005 SP2 / SP3 report server in SharePoint mode versions, step 1 (from above scenarios) comprises upgrading to SSRS 2008 SP1 + CU8 OR SSRS 2008 R2 followed by steps 2 and 3( from above scenarios) when upgrading to SharePoint 2010.

Integrating SSRS 2008 R2 RTM with SharePoint 2007

Prash Shirolkar - MSFT — Wed, 05 May 2010 18:04:00 GMT

The SSRS 2008 R2 Report Server in SharePoint mode allows integrating with SharePoint 2007:

Supported configuration: SSRS 2008 R2 is supported on SharePoint 2007 with the SSRS 2008 RS Add-in for SharePoint version SP2 onwards. This can now be downloaded from : http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35c3a13f-4b5e-4d4a-86e4-07ee307b9638&displaylang=en. Additionally, details on SP2 can be found @ http://blogs.technet.com/b/dataplatforminsider/archive/2010/09/29/sql-server-2008-sp2-is-available-for-download-today.aspx
(outdated information: The timeline for SP2 is no earlier than Sept. 2010, having said that you can consider trying out the functionality / this configuration using the latest SSRS 2008 SP2 CTP version of this Add-in available @ http://www.microsoft.com/downloads/details.aspx?FamilyID=65606fdd-093f-4c70-91f6-dc1f24520e8f&displaylang=en )
Features available: In this configuration features available include Alternate Access Mapping, SharePoint List Reporting extension in connected mode, Report Builder 3.0 with Report Parts, ATOM Renderer, RS.EXE enabled to script against SharePoint mode, etc.
Features not available: Key features not avilable include Out-of-the-box (OOTB) Local mode reporting, AJAX ReportViewer, ULS logging, etc.

For details on features supported by SSRS 2008 R2 Report Server with SharePoint 2007 refer to http://msdn.microsoft.com/en-us/library/bb326290(v=SQL.105).aspx

HTH,
Prash

Integrating SSRS 2008 R2 RTM with SharePoint 2010 RTM

Prash Shirolkar - MSFT — Mon, 26 Apr 2010 18:16:00 GMT

The SSRS 2008 R2 release in SharePoint mode allows two forms of reporting:

Out-of-the-box (OOTB) Local mode reporting: In this case, SSRS 2008 R2 introduces the ability to render reports without an integrated Report server. Details on local mode reporting with SharePoint integration can be found @ http://msdn.microsoft.com/en-us/library/ff487969(v=SQL.105).aspx. From an install prespective you only need to install SSRS 2008 R2 RTM Add-in for SharePoint 2010 on SharePoint 2010 RTM Web-front-end(s) to have the ability to render uploaded / canned reports (.rdl files) for:
1. SharePoint Lists reports: available in SharePoint 2010 Foundation Editions or higher.
2. Access reports: available in SharePoint 2010 Editions that Access Services is supported in.
Point to note: You need to turn on ASP.Net Session state as well, by opening the SharePoint Management Shell and entering the command - Enable-SPSessionStateService. Next, the command will ask for a DatabaseName value that you can provide say "MySessionDB". Finally, perform an IIS reset.
Connected mode Reporting: This form of reporting is allowed when you have an SSRS Report Server integrated into the SharePoint farm as well to enable full end-to-end reporting that existed in prior versions and is now available in SharePoint 2010 with the SSRS R2 RTM Add-in for SharePoint 2010. Details on configuring connected mode @ http://msdn.microsoft.com/en-us/library/bb326213(v=SQL.105).aspx. There are 2 report server major versions that can be used in this form of reporting for SharePoint 2010:
1. SSRS 2008 R2 RTM report server: In this case, with SSRS 2008 R2 RTM Add-in for SharePoint 2010 and SharePoint 2010 refer to the what's new in SSRS R2 functionality for information on what all is supported @ http://msdn.microsoft.com/en-us/library/ee210710(v=SQL.105).aspx
2. SSRS 2008 Report Server: A patch is needed for SSRS 2008 Report Server SP1 CU8 (planned for released in May, 2010 @ http://support.microsoft.com/kb/981702/en-us) to enable its support with SharePoint 2010 and SSRS R2 RTM Add-in for SharePoint 2010. Additionally, in this configuration existing SSRS 2008 in SharePoint mode functionality that SharePoint 2010 supports via backward compatiblity with SharePoint 2007 is available / supported . New SSRS 2008 R2 in SharePoint mode functionality like Alternate Access mapping, Access Reporting, SharePoint List reporting, etc. OR new SharePoint 2010 functionality like Claims etc. is not supported in this configuration.

thanx,
Prash

Error installing rsSharePoint.msi on Windows 2008

Prash Shirolkar - MSFT — Tue, 01 Sep 2009 19:36:00 GMT

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:

Open a command prompt with “Run as Administrator…”
Run rsSharePoint.msi SKIPCA=1.
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.
Run rsCustomAction.exe /i

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

HTH

Prash

Integrating SSRS with SharePoint 2010 Beta 1 / Beta 2

Prash Shirolkar - MSFT — Thu, 30 Jul 2009 05:04:00 GMT

Warning: Recommended version of Report Server for use with SharePoint 2010 Beta1 is SSRS 2008 R2 CTP2 / CTP3 only. The only version of SSRS Add-in for SharePoint with SharePoint 2010 Beta 2 is SSRS 2008 R2 November CTP Add-in. Using SSRS 2008 with Beta product - MOSS Beta 1 or Beta 2 is expected to work, however it is not a supported scenario esp. in production environments and has not been extensively tested at the time of publishing this blog. Hence, please proceed with utmost caution by backing up any previous data, etc. before trying out the steps below:

Enabling SSRS 2008 report server to load SharePoint 2010 Beta1 (Ignore this step for SharePoint 2010 Beta 2, because it is expected to support ASP .Net assembly binding redirect out-of-the box): Use ASP.Net assembly binding redirect to ensure an existing SSRS 2008 can load SharePoint 14 assemblies, details @ http://msdn.microsoft.com/en-us/library/2fc472t2(VS.80).aspx. Here is the entry to add under <System.data> element tags in %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config
<runtime>
     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
               <assemblyIdentity xmlns="urn:schemas-microsoft-com:asm.v1" name="Microsoft.SharePoint" publicKeyToken="71e9bce111e9429c" culture="neutral" />
               <bindingRedirect xmlns="urn:schemas-microsoft-com:asm.v1" oldVersion="12.0.0.0" newVersion="14.0.0.0" />
          </dependentAssembly>
     </assemblyBinding>
</runtime>
Integrating SSRS Add-in with SharePoint 2010 Beta2: SSRS 208 R2 November CTP ships an SSRS 2008 R2 November CTP Add-in for SharePoint 2010 @ http://www.microsoft.com/downloads/details.aspx?FamilyID=16bb10f9-3acc-4551-bacc-bdd266da1d45&displaylang=en. This the only SSRS Add-in supported with SharePoint 2010 Beta2 and can be installed prior to installing SharePoint 2010 Beta 2. It also supportsinstalling after SharePoint 2010 is installed. Having said that, the recommended means to

Installing SSRS 2008 R2 Nov. CTP Add-in before installing SharePoint 2010 Beta 2 WFEs

Install rsSharePoint.msi (ships starting with SSRS 2008 R2 November CTP)
Install SharePoint 2010 Beta 2
Run SharePoint 2010 Beta 2 configuration wizard
After this will activate the feature in the Central Admin site, however not in the SharePoint 2010 content sites because no Report Server has been integrated into SharePoint 2010. In this state (called as Local mode) SSRS supports out-of-the-box rendering only of 2 types of reports - Access and SharePoint List reports.

After successfull installation, configuring an integrated SSRS instance with SharePoint 2010 Beta2 entails:

Goto the "Reporting Services Integration" web page in the "Application Management" in Central Administration,
Provide the Report Server URL, Authentication Type and credentails and Press Apply.

For additional instances of Reportings Services when you ahve configured SSRS in Scale-out configuration use the "Add an SSRS instance to the Integration" web page.

Integrating SSRS Add-in that ships in MOSS 2010 Beta1: (Note: SSRS Add-in is not supported with WSS 2010 Beta1.) Just like in prior versions of the SSRS Add-in for SharePoint you need to belong to the SharePoint Farm Administrator group to perform the following steps and step 1 also requires local admin credentials for the SSRS machine.

Provision SSRS 2008 to access MOSS 2010 Beta1:

Browse to "SharePoint Central Administration" -> "General Application Settings" -> "Add a Report Server to the integration" pages,
Provide the machine name, instance name and press "OK", and
Provide credentials in the credentials dialog box and press "OK".

Update Report Server URL and Authentication mode by running the powershell code below:
echo "Loading Microsoft.SharePoint.Administration..."
[reflection.assembly]::LoadWithPartialName(“Microsoft.SharePoint.Administration”)
$services = [Microsoft.SharePoint.Administration.SPFarm]::Local.Services
foreach ($service in $services) {
         if ([string]::Compare($service.Name, "ReportingService", $True) -eq 0) {
            ##### Set Report Server Web Service URL
            $service.RSServerUrl = "http://<RS_Server_Name>:<RS_Server_port>/<RS_Web_Service_VDir>";
            ##### Set Authentication mode to "Windows" or "Trusted"
            $service.AuthenticationType ="Windows";
            $service.Update();
            echo $service;
        }
}
Activate the RS feature in all of MOSS 2010 Beta 1's content sites (Ignore for with SharePoint 2010 Beta2 and SSRS 2008 R2 November CTP Add-in for SharePoint 2010):

Copy the attached RSIntegrationResults.aspx page into the %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS\ReportServer folder. ***
Browse to "SharePoint Central Administration" -> "General Application Settings" -> "Reporting Services Integration" page, and
Press OK,
*** Note: This is a bug, wherein RSIntegrationResults.aspx page was not included amongst the SSRS Add-in for SharePoint files in MOSS 2010 Beta1. Hence, if you press OK without copying this page you will notice a generic SharePoint error page being shown on successful completion of activating the RS feature.

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

Prash Shirolkar - MSFT — Wed, 21 Jan 2009 20:32:00 GMT

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.

When a report is rendered in full-page view in SharePoint, the URL is displayed in the following format: http://<SharePoint_site>/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/<SharePoint_Document_Library>/<Report_Name>.rdl.
In SSRS 2008, you specify a report parameter name and value pair by explicitly specifying the prefix "rp:". Here is an example to add-on a parameter with name "Month" that accepts a string value: http://<SharePoint_site>/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/<SharePoint_Document_Library>/<Report_Name>.rdl&rp:Month=January
You can also specify a fixed set of ReportViewer parameters to alter full-page rendering experience. These ReportViewer parameters need to be explicitly prefixed by "rv:". Here is an example of rendering the report with the parameters area collapsed: http://<SharePoint_site>/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/<SharePoint_Document_Library>/<Report_Name>.rdl&rv:ParamMode=Collapsed&rp:Month=January

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

SQL Server Reporting Services 2008 R2

In the Report Viewer that ships with the SSRS 2008 R2 Add-in for SharePoint the following new Report Viewer parameters are added:

ReportViewer Parameter

Description

Values

rv:DockToolBar

Controls whether the ReportViewer web part’s toolbar is docked to the top or bottom.

Top, Bottom.

Default: Top

rv:ToolBarItemsDisplayMode

Controls turning of or on specific parts of the ReportViewer web part’s toolbar. This is an enumeration field eg. For no Actions menu rv:ToolBarItemsDisplayMode= 63 (or 0x3F); For all of Actions menu only rv:ToolBarItemsDisplayMode= 960 (or 0x3C0)

Back= 1, (0x1)

Find= 2, (0x2)

Page Navigation=4, (0x4)

Refresh= 8, (0x8)

Zoom= 16, (0x10)

AtomFeed= 32, (0x20)

Actions Menu Print= 64, (0x40)

Actions Menu Export= 128, (0x80)

Actions Menu ReportBuilder= 256,(0x100)

Actions Menu Subscribe = 512, (0x200)

Default: -1

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

Prash Shirolkar - MSFT — Tue, 21 Oct 2008 20:54:00 GMT

A] Forms Authentication

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.
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>
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.
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
*Note: These steps also apply to other authentication schemes used with SharePoint that result in a User Credentials dialog box shown to users at login time.*

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.
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.
*Additionally, if the user is using an OS that supports UAC then ensure you invoke the browser with "Run As Administrator".*

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

Prash Shirolkar - MSFT — Sat, 02 Aug 2008 03:52:00 GMT

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.

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
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.
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 is available with SSRS 2008 R2 SharePoint mode.
Is there support for Reporting against SharePoint lists?
SSRS does not natively ships a SharePoint Lists data extension as yet in SSRS 2008 R2. For prior versions of SSRS, 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.
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.
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. Note: in Trusted Account mode you cannot use “Windows Integrated” data source credentials (with the exception of SharePoint List extension in SSRS 2008 R2) and you will need to use “Stored Credentials” instead.
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
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.
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.
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?
- Use WSS 2.0 Report Explorer and Report Viewer web parts. These are supported in WSS 3.0 as well.
- Make sure you are Comparing Levels of Integration Across Versions of Reporting Services and SharePoint Technologies
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
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.
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.
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