KBA-01119: Can Business Portal and Reporting Services be installed on the same IIS Server?


Can I install Business Portal and SQL Server Reporting Services (SSRS) on the same IIS server?


Yes—just not in the same website.  Microsoft‘s suggestion is that since both web applications run in the default website, you should run them on separate IIS servers.  But you can move SSRS to another website on the same IIS server and run both systems.
Microsoft SQL Server 2005 makes it easy to pick a website other than the default website when you are installing SSRS.  Microsoft SQL Server 2000 does install into the default, but you can save the two Report Service virtual directories to file and then move them to a different website. Just be sure to edit the two config files to match the new virtual directories.

Here’s the info on the Business Portal/Report Server conflict:

In ../inetpub/wwwroot/web.config:
If you comment out the following line, Reporting Services runs, but Business Portal does NOT:
(Note: line is shown with comment marks below)

<!– <add name=‘EnterpriseInitializationModule‘
Microsoft.BusinessFramework‘ />–>

If you remove the comment markers, Business Portal will run, but Reporting Services will NOT and gives the following error:

Microsoft.BusinessFramework.Security.EnterpriseInitializationModule,Microsoft.BusinessFramework cannot be found.

Additional Comments:

Spitfire does not require that you install it in the default website. In fact, we recommend that you create a web site for sfPMS and then create a virtual directory for our Spitfire web application. Therefore, Spitfire can reside on the same IIS Server as Business Portal. Remember that Spitfire reports are SQL Reporting Services reports and therefore, Spitfire requires SQL Reporting Services.  Spitfire will connect to SQL Reporting Services if Reporting Services is installed on a different IIS Server, just as long as Spitfire can connect to that IIS Server.

KBA-01119; Last updated: October 13, 2016 at 11:40 am;