You receive a 1603 error message or a 25619 error message when you try to install SQL Server 2000 Reporting Services (867872)
The information in this article applies to:
- Microsoft SQL Server 2000 Reporting Services
SYMPTOMSWhen yo u 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 "occured" is a misspelling
for the word "occurred." CAUSEThe SQL Server 2000 Reporting Services installation Setup
program uses the IWAM_ Computername account to
configure Microsoft Internet Information Services (IIS). A problem may occur if
one or more of the following conditions are true. Note Computername is a placeholder for the
name of your computer. - The IWAM_Computername account is
disabled.
- The password for the
IWAM_Computername 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.
WORKAROUNDTo 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:
- 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 /i "Setup\Rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=True Notes- This command may also require the use of the full path in the .msi path, for example, "D:\<fullpath>\setup\Rsrun.msi"
- Make sure that you use the fully qualified path for Setup.exe and
Rsrun.msi when you run this command.
For more information about installing SQL Server 2000
Reporting Services from the command line, visit the following Microsoft Web
site: - 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 is similar to 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.
- Use Internet Services Manager and create the following
virtual directories:To do this, follow these steps:
- 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. - In the left pane, right-click Default Web
Site, point to New, and then click Virtual
Directory.
- In the Virtual Directory Creation
Wizard dialog box, click Next.
- 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.
- On the Web Site Content Directory
page, click Browse.
- If you are creating the Reports virtual directory,
locate the Installation drive\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager folder.
If you are creating the ReportServer virtual
directory, locate the Installation
drive\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer folder. - Click Next.
- On the Access Permissions page, click
Next.
- In the Virtual Directory Creation
Wizard dialog box, click Finish.
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)
- Set the properties of the Reports virtual directory. To do
this, follow these steps:
- 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.
- In the Reports Properties dialog box,
click the Directory Security tab.
- In the Anonymous access and authentication
control list, click Edit.
- In the Authentication Methods dialog
box, clear the Anonymous access check box, and then click
OK.
- In the Reports Properties dialog box,
click the Virtual Directory tab.
- In the Application name box, type
Report Server Interface.
- In the Execute Permissions drop-down
list, select Scripts and Executables.
- Click the Documents tab.
- Select an item in the Enable Default
Document list, and then click Remove. Similarly, you
must remove all the items in the list.
- Click Add.
- In the Add Default Document dialog
box, type Home.aspx in the Default Document
Name box, and then click OK.
- 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:
- Click the HTTP Headers tab, and
then click Add under Custom HTTP headers. The
Add/Edit Custom HTTP Header dialog box appears.
- In the Custom header name box,
type MicrosoftOfficeWebServer.
- In the Custom header value box,
type 5.0_Pub.
- Click OK.
- In the Reports Properties dialog box,
click OK.
- Set the properties of the ReportServer virtual directory.
To do this, follow these steps:
For
Microsoft Internet Information Services (IIS) 5.0- In the Internet Information Services or the
Internet Information Services (IIS) Manager window, in the
left pane, right-click ReportServer, and then click
Properties.
- In the ReportServer Properties dialog
box, click the Directory Security tab.
- In the Anonymous access and authentication
control list, click Edit.
- In the Authentication Methods dialog
box, clear the Anonymous access check box, and then click
OK.
- In the Reports Properties dialog box,
click the Virtual Directory tab.
- In the Application name box, type
Report Server.
- In the Execute Permissions drop-down
list, select None.
- Click Configuration.
- In the Application Configuration
dialog box, select an item in the Application Mappings list on the App
Mappings tab, and then click Remove.
- Click Yes in the
Application/Script Mappings warning message to remove the item
from the list.
- Repeat step h and step i until you remove all the items
in the list.
- Click Add.
- 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. - In the
Extension box, type an asterisk ( *).
- In the Verbs list, click All
Verbs.
- Select the Script engine check box,
and then click OK.
- In the Application Configuration
dialog box, click OK.
- In the ReportServer Properties dialog
box, click OK.
For
Microsoft Internet Information Services (IIS) 6.0- In Internet Information Services or in the
Internet Information Services (IIS) Manager window, right-click ReportServer in the
left pane, and then click
Properties.
- In the ReportServer Properties dialog
box, click the Directory Security tab.
- In the Anonymous access and authentication
control list, click Edit.
- In the Authentication Methods dialog
box, clear the Anonymous access check box, and then click
OK.
- In the Reports Properties dialog box,
click the Virtual Directory tab.
- In the Application name box, type
Report Server.
- In the Execute Permissions drop-down
list, click None.
- Click Configuration.
- In the Application Configuration
dialog box, click an item in the Application extensions list
on the Mappings tab, and then click Remove.
- When you receive the following warning message, click
Yes to remove the item from the list.Remove the selected script mapping(s)?
- Repeat step h and step i until you remove all the items
in the list.
- Click Add.
- 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. - In the Verbs group box, click
All verbs.
- Select the Script engine check box,
and then click OK.
- In the Application Configuration
dialog box, click OK.
- Click the HTTP Headers tab, and then
click Add under Custom HTTP headers.
The
Add/Edit Custom HTTP Header dialog box appears. - In the Custom header name box, type
MicrosoftOfficeWebServer.
- In the Custom header value box, type
5.0_Pub.
- Click OK.
- In the ReportServer Properties dialog
box, click OK.
REFERENCESFor more information about how to troubleshoot a Reporting
Services installation, visit the following Microsoft Developer Network (MSDN)
Web sites:
Modification Type: | Major | Last Reviewed: | 8/24/2005 |
---|
Keywords: | kbPackage kberrmsg kbsetup kbtshoot kbprb KB867872 kbAudDeveloper |
---|
|
|
©2004 Microsoft Corporation. All rights reserved.
|
|