You must use a URL to the SharePoint server when you deploy a Report Server or Report Model project from Business Intelligence Development Studio to the report server.

To find the name of the server to use, open a browser and locate the SharePoint library where you want to publish a report. The server name appears immediately after the protocol prefix, for example, http://servername.

Using the Reporting Services URL proxy endpoint is not supported. A proxy endpoint includes a port number, for example, http://servername:8080/reportserver.

When you deploy a report or report data source, you must use a URL to a SharePoint site and subsite, if there is one. In the URL, the site name appears immediately after the server name., for example, http://servername/site or http://servername/site/subsite.

On a Microsoft Office SharePoint Server 2007 Web application, the site and subsite frequently correspond to the tabs on the main site. To find the site name or subsite name, click Home, and then All Site Content. Scroll to the bottom and look for Sites and Workspaces. The list of sites appears in this section.

When you deploy a report or related item to a SharePoint library, you must use a URL to the SharePoint library. The URL to use for a library differs depending on the version of SharePoint you are using.

On Microsoft Windows SharePoint Services 3.0, the library appears after the server name, for example, http://servername/Shared Documents.

On Office SharePoint Server 2007, the library appears after the site and subsite. For example, http://servername/site/Documents.

To find the path information for a new SharePoint library or for an unfamiliar site, open a browser and locate the SharePoint library where you want to publish your reports. If the library is empty, upload any file. Right-click the file and select Properties to open the Properties window. The address of the file contains the URL values that you need for a publish operation.

Items that are stored in a SharePoint library are always addressed through a fully qualified URL that starts with the Web application (http://server) as the root node, and concludes with the name of the file that you are referencing.

File names in the URL must include a file name extension.

You cannot use relative URLs for dependent items in reports that you publish to a SharePoint site. For example, you cannot use a relative URL to reference a shared data source, report model, or subreport. You must always specify the fully qualified URL to a SharePoint library for each item. There is no way to predict where a dependent file might be located as there is no predefined hierarchy to the sites that you can use to parse a URL format.

When you publish or upload a report that contains dependent items, you must set the references to the dependent items after the report is published. References that worked correctly in Preview mode in Report Designer are not guaranteed to work after the report is published. For more information, see Publishing from an Authoring Tool to a SharePoint Library in this topic.

A report definition can include an image file that is stored as an external file. You can reference that file in the report definition by setting a fully qualified URL to the image file. It can be stored on a SharePoint site or on a remote computer.

Regardless of the report server mode, references to an external image file in a report must be a fully qualified URL. Also, referencing an external image file typically requires that you configure the unattended report processing account.

If you are creating or constructing a URL to an item that is located on a SharePoint site, know that the words Personal and Sites are both reserved names under the default site.

When you publish a shared data source from a report authoring tool, you set the project property TargetDataSourceFolder. The target data source folder must be a URL to a SharePoint library. Unlike in Reporting Services native mode, you cannot specify a relative folder; relative paths are not valid. If a folder in the Document Library path does not exist, one will be created.

When you publish a shared data source (.rds) file to a SharePoint site, this changes the data source file to an .rsds file name extension. The .rsds file cannot be saved locally from a SharePoint site and imported into an existing Reporting Services project. Shared data sources with file name extensions .rds and .rsds are not interchangeable.

Shared Data Sources from Report Designer

Shared Data Sources from Model Designer

File names in a URL for report items must include a file name extension. The file name extension determines the file type. When you publish report items from a report authoring tool, the file name extension is included automatically. If you upload a report item to a SharePoint library, you must include a file name extension.

If you do not specify a file name extension for items that you upload to a SharePoint site, the rsInvalidDataSourceReference error will occur. File names may not include characters that are not recognized as valid file name characters by SharePoint applications. Do not include the following characters: # % & * : < > ? / { | }.

If your report definition includes references to subreports, the fully qualified URL for the subreport must be specified. You cannot specify a relative folder; relative paths are not valid.

For reports that have been created by using Report Builder, the report definition includes references to the report model and the model data source that was used to build the report. These are specified in the report definition file. If you add this report to a Report Server project in Report Designer to make changes, and then publish it to a SharePoint library, you must open the report on the SharePoint library and rebind the data source reference. You only must rebind the data source when you first publish the report. The report server cannot determine from the report definition whether the data source is an .rsds file or an .smdl file. For more information, see How to: Bind a Report or Model to a Shared Data Source.