Microsoft KB Archive/867872

= You receive a 1603 error message or a 25619 error message when you try to install SQL Server 2000 Reporting Services =

Article ID: 867872

Article Last Modified on 12/28/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Reporting Services

-



SYMPTOMS
When you try to install Microsoft SQL Server 2000 Reporting Services, you may receive one of the following error messages:

Error message 1

Microsoft SQL Server 2000 Reporting Services Setup

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25619.

Error message 2

Setup Error

An error has occured during setup. An error has occured while performing the following setup action. Please select help for more information about this error. You may be able to skip this action by selecting ignore, or retry the action by selecting retry. Selecting cancel will end the installation of SQL Server.

Configuring Microsoft SQL Server

Error Code: 1603

Note In the second error message, the word &quot;occured&quot; is a misspelling for the word &quot;occurred.&quot;



CAUSE
The SQL Server 2000 Reporting Services installation Setup program uses the IWAM_ account to configure Microsoft Internet Information Services (IIS). A problem may occur if one or more of the following conditions are true.

Note  is a placeholder for the name of your computer.
 * The IWAM_ account is disabled.
 * The password for the IWAM_ account that is stored in the following three locations is not synchronized:
 * The Internet Information Server (IIS) metabase
 * The User Manager for Domains tool in Microsoft Windows NT or the Local Users and Groups tool in Microsoft Windows 2000
 * Microsoft Transaction Server in Windows NT or Component Services in Microsoft Windows 2000



WORKAROUND
To work around this problem, explicitly install SQL Server 2000 Reporting Services without creating the virtual directories, and then manually create the virtual directories. To do this, follow these steps:  Install SQL Server 2000 Reporting Services without creating the virtual directories by using the RSDONOTCREATEVIRTUALDIRECTORIES command-line argument for the Setup.exe file. To do this, follow these steps:  Copy all the Setup files of SQL Server 2000 Reporting Services to a local folder. Make sure that the folder is located on the same drive as SQL Server.  At the command prompt, change the folder path accordingly to the folder that contains the Setup.exe file of the SQL Server 2000 Reporting Services Setup program, and then run the following command. setup.exe /iPath\Setup\Rsrun.msi RSDONOTCREATEVIRTUALDIRECTORIES=True Notes   represents the path of the folder to which you copy the Setup files. For example, if you copy the Setup files to the Enterprise folder under the C drive, you run the following command. setup.exe /iC:\Enterprise\Setup\Rsrun.msi RSDONOTCREATEVIRTUALDIRECTORIES=True  There is no space between /i and .

For more information about how to install SQL Server 2000 Reporting Services from the command line, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/aa179337(SQL.80).aspx

 Follow the installation steps for SQL Server 2000 Reporting Services that you see on the screen.

Because you installed SQL Server 2000 Reporting Services without creating the virtual directories, you receive a warning message that resembles the following toward the end of the SQL Server 2000 Reporting Services installation:

Setup could not initialize the report server. You must manually initialize the report server before using it for the first time. For more information, see the Reporting Services setup documentation.

</li></ol> </li> Use Internet Services Manager and create the following virtual directories:  Reports</li> ReportServer</li></ul>

To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type inetmgr, and then click OK.

In Microsoft Windows Server 2003, the Internet Information Services (IIS) Manager window opens. In Microsoft Windows 2000 or in Microsoft Windows XP, the Internet Information Services window opens.</li> In the left pane, right-click Default Web Site, point to New, and then click Virtual Directory.</li> In the Virtual Directory Creation Wizard dialog box, click Next.</li> On the Virtual Directory Alias page, type Reports in the Alias box to create the Reports virtual directory or type ReportServer to create the ReportServer virtual directory, and then click Next.</li> On the Web Site Content Directory page, click Browse.</li> If you are creating the Reports virtual directory, locate the  \Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager folder.

If you are creating the ReportServer virtual directory, locate the  \Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer folder.</li> Click Next.</li> On the Access Permissions page, click Next.</li> In the Virtual Directory Creation Wizard dialog box, click Finish.</li></ol>

For more information about how to create a virtual directory in Internet Information Services, click the following article number to view the article in the Microsoft Knowledge Base:

172138 How to create a virtual directory in Internet Information Services (IIS)

</li> Set the properties of the Reports virtual directory. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> In the Internet Information Services or in the Internet Information Services (IIS) Manager window, in the left pane, right-click Reports, and then click Properties.</li> <li>In the Reports Properties dialog box, click the Directory Security tab.</li> <li>In the Anonymous access and authentication control list, click Edit.</li> <li>In the Authentication Methods dialog box, clear the Anonymous access check box, and then click OK.</li> <li>In the Reports Properties dialog box, click the Virtual Directory tab.</li> <li>In the Application name box, type Report Server Interface .</li> <li>In the Execute Permissions drop-down list, select Scripts and Executables.</li> <li>Click the Documents tab.</li> <li>Select an item in the Enable Default Document list, and then click Remove. Similarly, you must remove all the items in the list.</li> <li>Click Add.</li> <li>In the Add Default Document dialog box, type Home.aspx in the Default Document Name box, and then click OK.</li> <li>If you are using Microsoft Internet Information Services (IIS) 5.0, you do not have to follow this step. If you are using Microsoft Internet Information Services (IIS) 6.0, follow these steps: <ol> <li>Click the HTTP Headers tab, and then click Add under Custom HTTP headers. The Add/Edit Custom HTTP Header dialog box appears.</li> <li>In the Custom header name box, type MicrosoftOfficeWebServer .</li> <li>In the Custom header value box, type 5.0_Pub .</li> <li>Click OK.</li></ol> </li> <li>In the Reports Properties dialog box, click OK.</li></ol> </li> <li>Set the properties of the ReportServer virtual directory. To do this, follow these steps:

For Microsoft Internet Information Services (IIS) 5.0 <ol style="list-style-type: lower-alpha;"> <li>In the Internet Information Services or the Internet Information Services (IIS) Manager window, in the left pane, right-click ReportServer, and then click Properties.</li> <li>In the ReportServer Properties dialog box, click the Directory Security tab.</li> <li>In the Anonymous access and authentication control list, click Edit.</li> <li>In the Authentication Methods dialog box, clear the Anonymous access check box, and then click OK.</li> <li>In the Reports Properties dialog box, click the Virtual Directory tab.</li> <li>In the Application name box, type Report Server .</li> <li>In the Execute Permissions drop-down list, select None.</li> <li>Click Configuration.</li> <li>In the Application Configuration dialog box, select an item in the Application Mappings list on the App Mappings tab, and then click Remove.</li> <li>Click Yes in the Application/Script Mappings warning message to remove the item from the list.</li> <li>Repeat step h and step i until you remove all the items in the list.</li> <li>Click Add.</li> <li>In the Add/Edit Application Mapping dialog box, click Browse, and then locate the Aspnet_isapi.dll file in the Microsoft .NET Framework 1.1 installation path.

Note By default, the .NET Framework 1.1 installation path is %windir%\Microsoft.NET\Framework\v1.1.4322.</li> <li>In the Extension box, type an asterisk ( * ).</li> <li>In the Verbs list, click All Verbs.</li> <li>Select the Script engine check box, and then click OK.</li> <li>In the Application Configuration dialog box, click OK.</li> <li>In the ReportServer Properties dialog box, click OK.</li></ol>

For Microsoft Internet Information Services (IIS) 6.0 <ol style="list-style-type: lower-alpha;"> <li>In Internet Information Services or in the Internet Information Services (IIS) Manager window, right-click ReportServer in the left pane, and then click Properties.</li> <li>In the ReportServer Properties dialog box, click the Directory Security tab.</li> <li>In the Anonymous access and authentication control list, click Edit.</li> <li>In the Authentication Methods dialog box, clear the Enable Anonymous access check box, and then click OK.</li> <li>In the Reports Properties dialog box, click the Virtual Directory tab.</li> <li>In the Application name box, type Report Server .</li> <li>In the Execute Permissions drop-down list, click None.</li> <li>Click Configuration.</li> <li>In the Application Configuration dialog box, click an item in the Application extensions list on the Mappings tab, and then click Remove.</li> <li>When you receive the following warning message, click Yes to remove the item from the list.

Remove the selected script mapping(s)?

</li> <li>Repeat step h and step i until you remove all the items in the list.</li> <li>Click Insert.</li> <li>In the Add/Edit Application Extensions Mapping dialog box, click Browse, and then locate the Aspnet_isapi.dll file in the .NET Framework 1.1 installation path.

Note By default, the .NET Framework 1.1 installation path is %windir%\Microsoft.NET\Framework\v1.1.4322.</li> <li>Click to clear the Verify that file exists check box, and then click OK.</li> <li>In the Application Configuration dialog box, click OK.</li> <li>Click the HTTP Headers tab, and then click Add under Custom HTTP headers.

The Add/Edit Custom HTTP Header dialog box appears.</li> <li>In the Custom header name box, type MicrosoftOfficeWebServer .</li> <li>In the Custom header value box, type 5.0_Pub .</li> <li>Click OK.</li> <li>In the ReportServer Properties dialog box, click OK.</li></ol> </li></ol>

<div class="moreinformation_section">

Steps to reproduce the 25619 error
<ol> <li>Click Start, point to Programs, point to Administrative Tools, and then click Computer Management. The Computer Management window opens.</li> <li>In the Computer Management window, in the left pane, locate the Users folder, and then click Users.</li> <li>In the Computer Management window, in the right pane, locate the IWAM_ account.</li> <li>Change the password of the IWAM_ account. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Right-click IWAM_ , and then click Set Password.</li> <li>In the Set Password dialog box, type a password in the New password box, and then click OK.</li> <li>In the Confirm password box, type the same password, and then click OK.</li> <li>In the Local Users and Groups message dialog box, click OK.</li></ol> </li> <li>Install SQL Server 2000 Reporting Services.</li></ol>

You receive the 25619 error that is mentioned in the &quot;Symptoms&quot; section.

<div class="references_section">