Article ID: 920803 - View products that this article applies to.
Consider the following scenario:
When you examine the SQLSetupNumber_ServerName_Core(local).log file, you notice an error message that resembles the following:
Microsoft SQL Server 2005 Setup
The setup has encountered an unexpected error while setting reporting service and share point exclusion path.
The error is: Fatal error during installation.
Doing Action: Do_RSSetSharePointExclusionPath PerfTime Start: Do_RSSetSharePointExclusionPath : Thu May 25 09:08:17 2006 <Func Name='Do_RSSetSharePointExclusionPath'> The application pool /s already exists. Error Code: 0x80077374 (29556) Windows Error Text: Source File Name: sqlca\sqliisca.cpp Compiler Timestamp: Mon Aug 29 01:18:41 2005 Function Name: Do_RSSetSharePointExclusionPath Source Line Number: 840
Error Code: 29556
MSI (s) (80!A4) [09:08:42:332]: Product: Microsoft SQL Server 2005 Reporting Services -- Error 29528. The setup has encountered an unexpected error while Setting reporting service and share point exclusion path. The error is: Fatal error during installation.
The setup has encountered an unexpected error while Setting reporting service and share point exclusion path. The error is: Fatal error during installation.
<Failure Type='Fatal' Error='29556'>
This problem occurs when the IP address for the Microsoft Internet Information Services (IIS) Default Web Site setting is not set to All Unassigned. If the SQL Server 2005 Reporting Services setup process cannot detect the Default Web Site setting, a new Web site is created. When SQL Server tries to configure the new Web site, the setup process fails, and an error message is generated. If you change the port of the default web site, the Report Server setup cannot install the default configuration.
To resolve this problem, click the Install but do not configure the server option in the setup process. Then, configure the Reporting Services using Reporting Services Configuration Tool after the installation is complete.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 920803 - Last Review: October 13, 2008 - Revision: 2.0