SharePoint and SSRS (Reporting Services) IIS Port Conflict

I have been having trouble installing SharePoint on the same Server as SQL 2005 due to port 80 conflicts. 

If you search on "SharePoint" in SQL BOL (Books On Line) there are some good links to configure both on the same machine. 

Here is some initial reasearch I have done. 

Great doc!

 There is also a reporting services add-in for SharePoint:

It also may be possible to host SSRS reports in the context of a SharePoint PageViewer control, but I haven't gotten that far yet. 

 Here is the SQL BOL Content:

You can run a report server and Microsoft Windows SharePoint Services together on a single Microsoft Internet Information Services (IIS) 6.0 server as long as each service runs in a different application pool and you add the Reporting Services virtual directories to the Windows SharePoint Services list of exclusions.

Installation Recommendations

You can install Reporting Services and Windows SharePoint Services in any order.

For best results, install the report server instance using the installation option that copies the program files to disk and performs minimal configuration. In the SQL Server Installation Wizard, this is the Install but do not configure server option. Use the Reporting Services Configuration tool after Setup is finished to complete the report server deployment.

Windows SharePoint Services can be downloaded from the Microsoft Download site. The executable that installs the service is stsv2.exe. To install Windows SharePoint Services, choose a computer that is running Windows Server 2003 with IIS 6.0 in Worker Process Isolation Mode and ASP.NET enabled.

Configuration Steps for Side-by-Side Deployment

The following steps explain how to run Windows SharePoint Services and Reporting Services together after both products are installed. You can configure the report server for deployment before or after the following steps are complete.

  1. Run the following commands to add the Reporting Services virtual directories to the Windows SharePoint Services list of exclusions. If you installed Reporting Services using the default virtual directories, run the following at the command prompt:

    Copy Code
    STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion

    Copy Code
    STSADM.EXE -o addpath -url http://localhost/Reports -type exclusion

By default, the stsadm.exe file is located in C:\Program Files\Common Files\Microsoft Shared\Web server extensions\60\bin.



  1. Run the Reporting Services Configuration tool. If you have not yet configured the report server for operation, you must create the report server and Report Manager virtual directories, specify service accounts, and create the report server database. For more information about how to set the options in the tool, see Reporting Services Configuration F1 Help.

    If you configured the report server before installing Windows SharePoint Services, check the application pool settings for the Web service to verify they are correct:

    1. Open the Web Service Identity page.

    2. Verify that the application pool for the report server and Report Manager is set to Default Application Pool (or another application pool that you defined for the service). The application pool used by the report server must be different from the one used by SharePoint Services.

In the previous release, the documentation recommended that you enable session state. Enabling session state is no longer a requirement. However, if you do not enable session state, session state for Report Manager folder pages that get set in detail view will not be preserved. If you require session state for detail view, enable session state by setting enableSessionState to true in the SharePoint Web.config file located at C:\Inetpub\wwwroot.



See Also





Skip to main content