Microsoft KB Archive/934163

= How to upgrade SQL Server 2005 Reporting Services on a Windows Vista-based computer =

Article ID: 934163

Article Last Modified on 6/22/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Reporting Services

-



INTRODUCTION
This article discusses requirements and steps for upgrading Microsoft SQL Server 2005 Reporting Services on a Windows Vista-based computer.



MORE INFORMATION
If you upgrade Microsoft Windows XP to Windows Vista on a computer that has SQL Server 2005 Reporting Services installed, you can continue to use Reporting Services after the operating system upgrade is complete. However, these two operating systems are different. You must perform the following actions before you can use Reporting Services.
 * When you upgrade Windows XP to Windows Vista, Microsoft ASP.NET and the World Wide Web Publishing service are turned off. Even if ASP.NET and the World Wide Web Publishing service are started before the upgrade, ASP.NET and the World Wide Web Publishing service become unavailable during the upgrade process. You must reset these services after the upgrade.
 * Microsoft Internet Information Services (IIS) 7.0 uses application pools. New application pools are created when you upgrade a Windows XP-based computer that has IIS and Web applications installed. Because Reporting Services runs as a legacy application in IIS 7.0, the new application pool settings will not be valid for Reporting Services. You must modify the settings after upgrade is complete.
 * Administrator permissions are not automatically available to local administrators if you use the User Account Control (UAC) feature of Windows Vista. If you previously accessed and previously managed a report server by using the built-in permissions that are granted to local administrators, you must now create explicit role assignments for the account.

Prerequisites
 You must have SQL Server 2005 Service Pack 2 (SP2) installed to run SQL Server 2005 on Windows Vista. For more information about how to obtain the latest service pack for SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Note Upgrade steps will vary slightly depending on whether you install SQL Server 2005 SP2 before or after you upgrade the operating system. SQL Server 2005 Express Edition with Advanced Services Service Pack 2 (SP2) has specific upgrade requirements. You must configure the existing SQL Server 2005 Reporting Services installation before you install SQL Server 2005 Express Edition with Advanced Services SP2. Otherwise, you cannot install SQL Server 2005 Express Edition with Advanced Services SP2.

Upgrade a computer that has Reporting Services installed to Windows Vista
To upgrade a computer that has Reporting Services installed to Windows Vista, follow these steps.

Note These steps assume that you have a Windows XP Service Pack 2 (SP2)-based computer. Additionally, an instance of Reporting Services is installed and configured correctly.  Install SQL Server 2005 SP2 on the instance of Reporting Services. Back up the encryption keys and the report server database. To back up the keys, use the Reporting Services Configuration tool. To back up the database, use SQL Server Management Studio. Upgrade Windows XP SP2 to Windows Vista. Log on to Windows Vista, enable ASP.NET, and then start IIS. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, and then click Control Panel.</li> Click Programs</li> Under Programs and Features, click Turn Windows features on or off.</li> In the User Account Control dialog box, click Continue.</li> In the Windows Features dialog box, expand Internet Information Services, expand World Wide Web Services, expand Application Development Features, click to select the ASP.NET check box, and then click OK.</li> In Control Panel, click System and Maintenance.</li> Click Administrative Tools.</li> Double-click Services.</li> In the User Account Control dialog box, click Continue.</li> Right-click World Wide Web Publishing, and then click Properties.</li> In the Startup Type list, click Automatic.</li> Click Apply, click Start, and then click OK.</li></ol> </li> Verify that the Reporting Services service and the Database Engine service are started. If these services are stopped, you must start them now.</li> Create a new application pool for Report Server and Report Manager. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Start the Reporting Services Configuration tool. To do this, click Start, point to All Programs, point to SQL Server 2005, point to Configuration Tools, and then click Reporting Services Configuration.</li> In the User Account Control dialog box, click Continue.</li> <li>In the Instance Selection dialog box, type the computer name, select the instance of Reporting Services, and then click Connect.</li> <li>Click Web Service Identity.</li> <li>Notice the value of the ASP.NET Service Account. If the value is IWAM_, you will experience a problem when you click Apply on this page. If the ASP.NET Service Account is set to NetworkService, you can apply changes without experiencing the problem.</li> <li>Click New to create a new application pool for Report Server.

Note We recommend that you create a new application pool. However, you can select an predefined application pool if the following conditions are true: <ul> <li>In Internet Information Services Manager, the Managed Pipeline Mode setting of Application Pools is Classic.</li> <li>The ASP.NET Service Account is not IWAM_ .</li></ul>

To use a predefined application pool, click Classic .NET AppPool in the Report Server list. If you use a predefined application, go to step 6j.</li> <li>In the Application Pool Name box, type ReportServer .</li> <li>Specify an account for this application pool. If you are using a built-in account, click NetworkService in the Build-in Account list. Otherwise, specify a domain user account that has the fewest permissions.</li> <li>Click OK.</li> <li>Select the same application pool for Report Manager as the application pool for Report Server.</li> <li>Click Apply.</li> <li>Click Refresh. When the page is updated, verify that the application pool that you created is selected for both Report Server and Report Manager.

If you receive an error message when you click Apply, select the application pool for Report Server and for Report Manager, and then click Apply again. This should resolve the issue. In some cases, you may experience a problem setting the application pool for Report Manager after you successfully set the application pool for Report Server.

Note In some cases, the Apply button is disabled after you select an application pool for Report Manager. If this behavior occurs, update the page, and then reselect the application pool for Report Server. Even if the application pool for Report Server is selected correctly, select the application pool for Report Server again. This action enables the Apply button.

If the Apply button is still disabled, the application pool that you selected might be invalid. In the application pool settings in Internet Information Services Manager, verify that the Managed Pipeline Mode setting of Application Pools is Classic. You must also verify that the NetworkService account, the built-in account, or the domain user account is set for the ASP.NET Service Account.</li></ol> </li> <li>If you want to open Report Server or Report Manager in Windows Internet Explorer on the local computer, add the Report Server URL and the Report Manager URL to the Trusted Sites list. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Start Internet Explorer.</li> <li>On the Tools menu, click Internet Options.</li> <li>Click Security.</li> <li>Click Trusted Sites.</li> <li>Click Sites.</li> <li>Under Add this Web site to the zone, type http://. If you do not use HTTPS for the default site, click to clear the Require server certification (https:) for all sites in this zone check box.</li> <li>Click Add.</li> <li>Repeat step 7f and step 7g to add the http://localhost URL, and then click Close.

These steps enable you to start Internet Explorer and open either the localhost or the network computer name of the server for both the Report Server application and the Report Manager application.</li></ol> </li> <li>Create role assignments that explicitly grant you access together with full permissions. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Start Internet Explorer together with the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator.</li> <li>Open Report Manager. By default, the Report Manager URL is http:// /reports.

If you use SQL Server Express with Advanced Services SP2, the Report Manager URL is http:// /reports$sqlexpress. If you use a named instance of Reporting Services, the Report Manager URL is http:// /reports$ </li> <li>In the Home dialog box, click Properties.</li> <li>Click New Role Assignment.</li> <li>Type a Windows user account name by using the following format:

\

</li> <li>Click to select the Content Manager check box.</li> <li>Click OK.</li> <li>In the Home dialog box, click Site Settings.</li> <li>Click Configure site-wide security.</li> <li>Click New Role Assignment.</li> <li>Type a Windows user account by using the following format:

\

</li> <li>Click System Administrator.</li> <li>Click OK.</li> <li>Close Report Manager.</li></ol> </li> <li>Use Internet Explorer without the Run as administrator option to reopen Report Manager.</li></ol>

If you administer a report server on Windows Vista, explicit role assignments must be defined on the report server. In Windows XP, members of the local Administrator group automatically have full permissions on a report server. Members of the local Administrator group are equal to the System Administrator role and the Content Manager role. In Windows Vista, the built-in Administrator security principle no longer has automatic access to report server content. If you previously accessed a report server through the built-in Administrator security principle, you must now explicitly assign a Windows user account to specific roles.

Upgrade tips if you install SQL Server 2005 SP2 after you upgrade the operating system
If you upgrade the operating system to Windows Vista before you apply SQL Server 2005 SP2 to the instance of Reporting Services, you must install SQL Server 2005 SP2 on the report server before you run SQL Server 2005 SP2 in Windows Vista. To do this, follow these steps.

Note These steps assume that you have a Windows XP SP2-based computer. On this computer, an instance of Reporting Services is installed and is configured correctly. <ol> <li>Upgrade to Windows Vista.</li> <li>Enable ASP.NET, and start the World Wide Web Publishing service. For more information, see the &quot;Upgrade a computer that has Reporting Services installed to Windows Vista&quot; section.</li> <li>Install SQL Server 2005 SP2 on the instance of Reporting Services.</li> <li>If you do not restart the computer after you install SQL Server 2005 SP2, or if you install SQL Server Express Edition with Advanced Services SP2, you must reset IIS. To reset IIS, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Click Start, point to All Programs, and then click Accessories.</li> <li>Right-click Command Prompt, and then click Run as Administrator.</li> <li>In the User Account Control dialog box, click Continue.</li> <li>Type IISRESET, and then press ENTER.</li> <li>If you stopped the SQL Server service during the upgrade process, restart the SQL Server service.</li> <li>Configure application pools, create role assignments, and add the Web site to the Trusted Sites list. For more information, see the &quot;Upgrade a computer that has Reporting Services installed to Windows Vista&quot; section.</li></ol> </li></ol>

Consideration 1
If Reporting Services is not configured, you receive many upgrade blocker error messages when you try to upgrade to SQL Server Express Edition with Advanced Services SP2. For example, you receive one of the following upgrade blocker error messages:

Error message 1

The Reporting Services “ReportManager” virtual directory was not found under the default Web site.

Error message 2

The Reporting Services “ReportManager” virtual directory is not configured for Windows integrated authentication.

Error message 3

The Reporting Services “ReportManager” virtual directory is configured to use nondefault application mappings.

To work around this problem, uninstall SQL Server Express Edition with Advanced Services SP2. Then, install a new instance of SQL Server Express Edition with Advanced Services SP2.

Symptoms
Consider the following scenario. You install SQL Server Express Edition with Advanced Services SP1. During the installation, you select the Database Services component and the Reporting Services component. After the installation, you try to install SQL Server Express Edition with Advanced Services SP2. In this scenario, the Database Services component is upgraded successfully. However, the Reporting Services component cannot be upgraded.

This problem occurs if one of the following conditions is true:
 * You do not install the Report Manager component when you install SQL Server Express Edition with Advanced Services SP1.
 * When you install SQL Server Express Edition with Advanced Services SP1, you specify the Install but do not configure the server option on the Report Server Installation Options page. Additionally, you do not manually configure Reporting Services before you install SQL Server Express Edition with Advanced Services SP2.

Workaround
To work around this problem, fully configure Reporting Services. Then, install SQL Server Express Edition with Advanced Services SP2.

For more information, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkID=63922

Use SQL Server Business Intelligence Development Studio in Windows Vista
If you use Business Intelligence Development Studio in Windows Vista, you will experience compatibility issues with the vsprvs development environment.

If you want to open an existing project or an existing solution, or if you want to publish items from Report Designer or from Model Designer to a report server in Windows Vista, you must use elevated permissions to open SQL Server Business Intelligence Development Studio. To do this, follow these steps:
 * 1) Click Start, click All Programs, and then click SQL Server 2005.
 * 2) Right-click SQL Server Business Intelligence Development Studio.
 * 3) Click Run as administrator.
 * 4) Click Continue.
 * 5) Click Run Program.

You can now deploy reports and other items to the report server. If you do not have sufficient permissions, you receive error messages. For example, you experience the following issues:
 * You receive &quot;Access denied&quot; error messages when you try to open an existing project.
 * You receive logon failure error messages when you configure a data source connection to a shared data source.
 * When you use the Report Server Wizard to create a report, you receive a login failure error message when the wizard tries to connect to the external data source that provides data to the report.

To create logins for users who administer databases on the server, you must run SQL Server Management Studio by using the Run as administrator option. Otherwise, you cannot create or modify SQL Server logins or SQL Server database permissions.

<div class="references_section">