Friday, June 26, 2009

Configuring Report Services in SQL Server 2005

1 System Requirements

1. Windows Server 2003 / Windows 2000 Server/ Windows vista / Windows XP/ Windows Server 2008
2. IIS 5.0 or later is required for Microsoft SQL Server 2005 Reporting Services (SSRS) installations.
3. ASP.NET 2.0 is required for Reporting Services. When installing Reporting Services, SQL Server Setup will enable ASP.NET if it is not already enabled.
4. SQL server 2005 with SP1(In case you need to reinstall reporting services its advised to reinstall full SQL server rather then just reporting services).
5. SQL Server Setup requires Microsoft Windows Installer 3.1 or later and Microsoft Data Access Components (MDAC) 2.8 SP1 or later. You can download MDAC 2.8 SP1 from this Microsoft Web site.

For detailed requirements see: Hardware and Software Requirements for Installing SQL Server 2005 -

2 Install the SQL server reporting services

3 Post Installation Configuration

On the report server computer, follow these steps after setup is finished to complete the deployment:

1. Open port 80 in Microsoft Windows Firewall to enable incoming requests over port 80. If you installed Reporting Services on Microsoft Windows XP with Service Pack 2 or Windows Server 2003 with Service Pack, HTTP requests over port 80 are blocked by default. To open port 80, do the following:
1. Click Start, point to Control Panel, click Windows Firewall, click Exceptions, and then click Add Port.
2. In Name, type Web Server (TCP 80).
3. In Port number, type 80.
4. For the protocol, select TCP.
5. Click OK.
2. Modify Windows Firewall settings to enable remote administration.

a. Log on as a local administrator to the computer for which you want to enable remote administration.b. Open a command line window, and then run the following command: netsh.exe firewall set service type=REMOTEADMIN mode=ENABLE scope=ALL c. Verify that remote administration is enabled. You can run the following command to show the status: netsh.exe firewall show state

3. Add InetInfo.exe to the Windows Firewall Exception List
1. Click Start, point to Control Panel, and click Windows Firewall.
2. Click Exceptions.
3. Click Add Program.
4. Click Browse.
5. Select %windir%\system32\inetsrv\inetinfo.exe
6. Click Change Scope to set the scope.
7. Click OK.
8. Reboot the computer.
4. Enable remote connections to the SQL Server instance that hosts the report server database
1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and click SQL Server Surface Area Configuration Tool.
2. Click Surface Area Configuration for Services and Connections.
3. Open the folder for the SQL Server instance that hosts the report server databases.
4. Click Remote Connections.
5. Click Local and Remote Connections.
6. Click Using both TCP/IP and named pipes.
7. Click OK, and then restart the service.
5. Run the Reporting Services Configuration tool, connect to the report server instance you just installed, and review the status indicator for each setting to verify that it is configured. Make sure that it’s all green ticks.

6. Assign write permissions to the temporary ASP.NET folder to reporting service account (\reportingsvc).

4 Verify Reporting Services Installation
4.1 Verify that the report server is installed and running

1. Run the Reporting Services Configuration tool, connect to the report server instance you just installed, and review the status indicator for each setting to verify that it is configured.
2. Open the Services window and verify that the Report Server Windows service is running. To view the status of the Report Server Windows service, click Start, point to Control Panel, double-click Administrative Tools, and then double-click Services. When the list of services appears, scroll to Report Server (MSSQLSERVER). The status should be Started.
3. On the instance of SQL Server that is hosting the report server database, verify that the SQL Server Agent service is running. SQL Server Agent must be running before users define subscriptions and other scheduled operations. Use the SQL Server Surface Area Configuration tool to enable SQL Server Agent.
4. In a browser window, type http://localhost/reportserver (http:///ReportServer).The URL will be different if you installed the report server as a named instance. You can also go and try running report server directly through IIS.
5. Run reports to test report server operations. For this step, you can install and publish the sample reports if you do not have any reports available. For more information, see AdventureWorks Report Samples in SQL Server Books Online.

4.2 Verify that Report Manager is installed and running

1. In a browser window, type http://localhost/reports (http:///Reports) this is the virtual directory for Report Manager.

You can also go and try browsing report manager directly through IIS.

2. Use Report Manager to create a new folder or upload a file to test whether definitions are passed back to the report server database. If these operations are successful, the connection is functional.



Anonymous said...

Hey really nice website, I noticed your website when doing study on some methods to develop my web log. I was simply inquiring which spam software system you use for comments as I get tons on my site.

Anonymous said...

I would like to thank you for the efforts you have made in writing this post. This has been an inspiration for me. I’ve passed this on to a friend of mine.


Anonymous said...

I wasn’t aware of some of the info that you wrote about so I want to just say thank you. scholarships

unlimited microsoft points

Anonymous said...

I enjoyed reading this blog post! Keep up the great work.


newegg promo code

Anonymous said...

how are you?

Definitely gonna recommend this post to a few friends

Anonymous said...


This post was interesting, how long did it take you to write?