Publishing Reporting Services reports to MOSS



(Many, many thanks to Heidi Steen of the super-duper UE team at Microsoft for providing the material below. Hell, she even created screen shots!)


Now that lots of folks are happily playing around with SSRS/MOSS integration, it’s important to understand exactly how you publish the things to MOSS via Business Intelligence Studio. You still use the same dialogs you’re used to, but plug different values into them. Here are some nice, step-by-step instructions:


1.  In SQL Server Business Intelligence Development Studio,


    open an existing or new Report Server project.


 


2.  From the Project menu, click Properties. The <project>


    Property Pages dialog box opens.


 


3.  Choose the Configuration you use to publish to a SharePoint site.


    For example, Active(Debug) or Production.


 


4.  In the Deployment section, for the optional TargetDataSourceFolder,


    type a fully qualified URL to a library or library folder. For example,


    http://server01/mycustomreportingsite/Shared Documents.


 


    If left blank, this defaults to the TargetReportFolder value.


 


5.  For TargetReportFolder, type a fully qualified URL to a


    library or library folder. For example,


    http://server01/mycustomreportingsite/Shared Documents.


 


6.  For TargetServerURL, type a URL to a SharePoint


    top-level site or sub-site. If you do not specify


    a site, the default top-level site is used. For


    example, http://servername, http://servername/site


    or http://servername/site/subsite.


 


7.  Click OK.


 


8.  In Solution Explorer, right-click on the report


    you want to publish, and click Deploy. The report


    is published to the location specified in


    TargetReportFolder. Deployment errors appear in the Output window.


 


NOTE: In order to upload data sources and reports to MOSS, the user in question must have “Contribute” or “Full Control” permissions.


Below, I’ve attached some screenshots which demonstrate publishing to a library in a custom and default MOSS site (again, thanks to Heidi!)


 


[ImageAttachment]

PubToMoss.jpg

Comments (9)

  1. Anonymous says:

    With the release of Microsoft Office SharePoint System, you can have MOSS take over your SSRS report

  2. Anonymous says:

    This blog is very useful! I have no idea on how to deploy this to sharepoint. I have been looking for some manual on how to do it for almost 3 hours! Thanks a lot for posting it!!!

  3. Anonymous says:

    Hi,

    Thanks for this article, but usually, in reality we need to deply SSRS reports to a production or Support sites which are not on the same domain as the development servers or m/c’s. Any examples or best practises on deploying using a package or batch file would be greatly appreciated.

  4. Mahesh, in these cases you’ll use the ReportServer2006 SOAP endpoint to publish directly to the locations you are interested in. The methods in question (CreateReport()) are fully documented in books online. Hope this helps!

  5. Anonymous says:

    This blog is useful!!.

    I have faced lot of issues while deploying SSRS to MOSS for an FBA(using LDAP authentication)enabled web site in MOSS.Has anyone done this before.Any help would be appreciated.

  6. Anonymous says:

    New to sharept/ssrs — I am able to get rpts

    going by uploading rdls with internal data src

    and using rptviewers referencing same.  Having issues with rdls with external/shared data sources.  If I upload an rds and mark it as a universal data source I get "data source deleted".  If I deploy from BIDS the rds goes up ok but the rdls don’t — I’m getting timeouts plus Error 3 The operation you are attempting on item "http://wbellamy-vs1/Reports&quot; is not allowed for this item type. d:wbellamy-vs1-shipping90108a-make data connection filesearchforuseracct_sharepttest-currentsearchforuseracct_reportuseracctsearchShowUserAcct_SelectedFields.rdl 0 0

  7. Anonymous says:

    New to sharept/ssrs — I am able to get rpts

    going by uploading rdls with internal data src

    and using rptviewers referencing same.  Having issues with rdls with external/shared data sources.  If I upload an rds and mark it as a universal data source I get "data source deleted".  If I deploy from BIDS the rds goes up ok but the rdls don’t — I’m getting timeouts plus Error 3 The operation you are attempting on item "http://wbellamy-vs1/Reports&quot; is not allowed for this item type. d:wbellamy-vs1-shipping90108a-make data connection filesearchforuseracct_sharepttest-currentsearchforuseracct_reportuseracctsearchShowUserAcct_SelectedFields.rdl 0 0

  8. Anonymous says:

    Error msg on above:

    The report server cannot process the report. The data source connection information has been deleted. (rsInvalidDataSourceReference)

    Should an RDL be a UNIVERSAL or OFFICE data source?