Distributed Server Deployment with Three computers.
| Download a .doc version of this post |
Summary
02 - Recommended installation sequence (installation overview - workarounds)
3.1 - Step 1: Installation of SQL Server 2008 on SQLSERVER2008
01 - Start SQL Server 2008 installation
3.2 - Step 2: Installation of SQL Server Reporting Services 2008 on SSRS2008SPIM
01 - Start SQL Server 2008 installation
02 - Selecting Installation features
3.3 - Step 3: Installation of SharePoint 2007 on SHAREPOINT2007
01 - Create SharePoint databases and grant permissions to SPS_SETUP domain account
02 - Start SharePoint installation on SHAREPOINT2007
03 - Running SharePoint Product and Technologies Configuration Wizard
03 - Creating a Web Application on port 81 and a TestReportingServices Site Collection
3.4 - Step 4: Installation of SharePoint 2007 on SSRS2008SPIM
3.5 - Step 5: Configuration and test of the Report Server on SSRS2008SPIM
01 - Preparing SSRS_SERVICE account to configure Reporting Services
01 - Installation of SQL Server Reporting Services 2008 Add In for SharePoint on SHAREPOINT2007
02 - Configuration of reporting services in SharePoint Central Administration
3.7 - Step 7: BIDS installation, Report creation, deployment and test
- SQL Server 2008 Database Engine
- SQL Server Reporting Services 2008
- SharePoint 2007 (Windows SharePoint Services 3.0)
This tutorial is completing these previous ones:
Integrating Reporting Services 2008 with SharePoint 2007 Step 1 - SQL Server 2008 Installation
Integrating Reporting Services 2008 with SharePoint 2007 Step 2 - SharePoint Installation
Integrating Reporting Services 2008 with SharePoint 2007 Step 3 - Configuring Reporting Services for SharePoint 3.0 Integration - Part 1
Integrating Reporting Services 2008 with SharePoint 2007 Step 4 - Configuring Reporting Services for SharePoint 3.0 Integration - Part 2
Installing SQL Server 2008 samples: Adventure works (Integrating Reporting Services 2008 with SharePoint 2007 Step 5)
Integrating Reporting Services 2008 with SharePoint 2007 Step 6 - Report Creation and Deployment
that was showing how to install SQL Server Reporting Services 2008 in SharePoint integrated mode with SharePoint 2007 but on a single computer. In this tutorial, we are going to build a real Production Environment.
Of course it would be better before doing this installation to have done at least once the installation on a single machine with one service account: local administrator account.
What I have noticed performing several interventions for different clients, is that the knowledge required installing even Microsoft Office SharePoint Server 2007 in a QA, staging, or Production Environment is increasing more and more because the involved products (SharePoint, SQL Server, IIS, etc.) are becoming more and more complex. For that reason, it is difficult for people working in Infrastructure and Network Area to have the entire required acknowledgement, and very often they need the support of SharePoint developers that are used to install SharePoint on their own development environment.
However, on the opposite, SharePoint developers are not deploying very often the products on several machines using the several service accounts required by the least-privilege administration policy that is recommended when you configure a Production Environment. They are often, not either aware of the configuration key elements that are needed by SharePoint, SQL Server, IIS, etc. to work on a multiple server environment.
If you add SQL Server Reporting Services 2008 to SharePoint 2007, the number of operations to perform and choices to take, much more increases.
So there is a knowledge gap to fill...
The name of the Domain used in this tutorial is "CORPORATE".
As this tutorial is rather made for people working in Infrastructure Area, I do not show how to create a domain account in Active Directory, and I put in the prerequisites the presence in the Active Directory of the following Service Accounts in order to be able to build an environment compliant with the principle of least privilege administration (Plan for administrative and service accounts (Office SharePoint Server)):
- SQL_SERVICE
- SPS_SETUP
- SPS_FARM
- SSRS_SERVICE
- SPS_AppPoolWebApp81
Of course you have three available Servers running Windows 2003 Server OS ready for the installation. The machine names I use in this post are the followings:
- SQL2008
- SSRS2008SPIM (for SQL Server Reporting Services 2008 in SharePoint Integrated Mode)
- SHAREPOINT2007
[...]
Three-Computer Deployment
The following illustration shows components for a three-computer deployment.
.gif)
The first computer hosts an instance of a SharePoint product or technology. The second computer hosts SQL Server Reporting Services. The third computer hosts an instance of the Database Engine.
In the illustration, notice that the Database Engine does not require a local installation of a report server or an instance of a SharePoint product or technology.
To use a remote database server with a deployment of a SharePoint product or technology, choose the Advanced installation option when installing an instance of a SharePoint product or technology, or use Central Administration to modify the database server setting. To select a remote database server for Reporting Services, use the Reporting Services Configuration tool. For more information about edition and connection requirements for a report server database, see Creating a Report Server Database and How to: Create a Report Server Database for SharePoint Integrated Mode (Reporting Services Configuration) .
[...]
| Machine 1 Name: | SQL2008 |
| Operating System: | Windows 2003 Server |
| Server Role | none (no more need of IIS for SQL Server 2008) |
| Deployed products: | SQL Server 2008 (Database Engine, Full Text, Basic Management Tools, Management Tools Complete) |
| Topology: | one instance (no named) |
| Machine 2 Name: | SSRS2008SPIM (for SQL Server Reporting Services 2008 SharePoint Integrated Mode) |
| Operating System: | Windows 2003 Server |
| Server Roles: | Application Server (no more need of IIS for Report server 2008 since it has its own IIS, but we need IIS for SharePoint) |
| Deployed products: | SQL Server 2008 Reporting Services, Windows SharePoint Services 3.0 |
| Topology: | SQL
Server 2008 Reporting Services: one instance, simple (no Scale Out)
Windows SharePoint Services 3.0: Minimal Installation |
| Machine 3 Name: | SHAREPOINT2007 |
| Operating System: | Windows 2003 Server |
| Server Roles: | Application Server (we need IIS for SharePoint) |
| Deployed products: | Windows SharePoint Services 3.0 |
| Topology: | simple Farm |
| Account Name and Password: | SQL_SERVICE Passw0rd |
| Account Description: | SQL
Server prompts for this account during SQL Server Setup. This account is
used as the service account for the following SQL Server services:
|
| Domain vs. Local | Domain Account (can be a local account) |
| Permissions | no special permissions required |
| Referenced documentation: | Technet: Plan for administrative and service accounts |
| Account Name and Password: | SPS_SETUP Passw0rd |
| Account Description: | SharePoint
SetUp user Account on SHAREPOINT2007 Server SharePoint SetUp user Account on SSRS2008SPIM Server The service account that is used to run:
cf. : Configuring the Report Server Service Account |
| Domain vs. Local | Domain Account (cannot be a local account) |
| Permissions | Administrator
of SHAREPOINT2007 Administrator of SSRS2008SPIM SQL Server login on the computer running SQL Server. Member of the following SQL Server security roles:
|
| Referenced documentation: | Technet: Plan for administrative and service accounts |
| Account Name and Password: | SPS_Farm Passw0rd |
| Account Description: | SharePoint
Server Farm Account This account is also referred to as the database access account. This account is:
|
| Domain vs. Local | Domain Account (cannot be a local account) |
| Permissions | no
special permissions required Its permission for SharePoint databases will be granted automatically during installation process |
| Referenced documentation: | Technet: Plan for administrative and service accounts |
| Account Name and Password: | SSRS_SERVICE Passw0rd |
| Account Description: | SQL
Server prompts for this account during SQL Server Reporting Services 2008
Setup. This account is used as the service account for the following SQL
Server services:
|
| Domain vs. Local | Domain Account (cannot be a local account in the current topology: Distributed Server Deployment with Three computers) |
| Permissions | The SharePoint Database Access will be granted during Report Server Configuration in SharePoint Central Administration on SHAREPOINT2007 |
| Referenced documentation: | msdn: How to: Configure a Service Account for Reporting Services |
| Account Name and Password: | SPS_AppPoolWebApp81 Passw0rd |
| Account Description: |
Application pool identity |
| Domain vs. Local | Domain Account (cannot be a local account in the current topology: Distributed Server Deployment with Three computers) |
| Permissions |
No manual configuration is necessary. Use a separate domain user account for each application pool. This account should not be a member of the Administrators group on any computer in the server farm The following are automatically configured:
|
| Referenced documentation: | msdn: How to: Configure a Service Account for Reporting Services |
The installation performed in this tutorial includes the following steps:
- Step 1: Installation of SQL Server 2008 on SQLSERVER2008
- Step 2: Installation of SQL Server Reporting Services 2008 on SSRS2008SPIM
- Step 3: Installation of SharePoint 2007 on SHAREPOINT2007
- Step 4: Installation of SharePoint 2007 on SSRS2008SPIM
- Step 5: Configuration and test of the Report Server on SSRS2008SPIM
- Step 6: Installation of SQL Server Reporting Services 2008 Add In for SharePoint on SHAREPOINT2007, Configuration and Check.
- Step 7: BIDS installation, Report creation, deployment and test.
WARNING:
when you are installing SQL Server Reporting
Services 2008 in SharePoint Integrated Mode, and want to keep being compliant
with the least-privilege administration principle, this principle and its
limited permissions become a problem because both, the configuration of report
server and the installation of SQL Server Reporting Services Add in for
SharePoint fail due to the limited access of all these accounts. But with a
workaround you can install the products combination properly and restore the
permissions keeping compliant with the least privilege administration. Read
carefully the following:
[...]
Least-privilege administration requirements when using domain user accounts
Least privilege administration is a recommended security practice in which each service or user is provided with only the minimum privileges needed to accomplish the tasks they are authorized to perform. This means that each service is granted access to only the resources that are necessary to its purpose. The minimum requirements to achieve this design goal include the following:
- Separate accounts are used for different services and processes.
- No executing service or process account is running with local administrator permissions.
By using separate service accounts for each service and limiting the permissions assigned to each account, you reduce the opportunity for a malicious user or process to compromise your environment.
Least privilege administration with domain user accounts is the recommended configuration for most environments.
[...]
Regarding Windows SharePoint Services 3.0, let us examine the minimal services and processes needed and we will understand least privilege basic administration for SharePoint.
- Setting up SharePoint on each server computer: task requiring local administrator permissions
- Running the SharePoint Products and Technologies Configuration Wizard: task requiring local administrator permissions
- Executing a Psconfig command-line: task requiring local administrator permissions
- Executing an Stsadm command-line: task requiring local administrator permissions
- Running the process of application pool identity for the SharePoint Central Administration Web site: process that does not require local administrator permissions
- Running the Windows SharePoint Services Timer service: service that does not require local administrator permissions
Thus, the least privilege administration principle for SharePoint is based on two main user accounts:
- Setup Account
- Farm Account
The Farm Account appears as System Account when you are signed in with it on a SharePoint site, but is not Administrator of any SharePoint server, thus you cannot perform a Psconfig or Stsadm command using it. You cannot run the SharePoint Products and Technologies Configuration Wizard with it.
Furthermore, in SharePoint Central Administration, the Farm account cannot access to the entire administration tasks, for example, when you are connected to SharePoint Central Administration with this account, in the Tab Operations, you cannot see the following links:
- Services on Server
- Incoming e-mail settings
- Remove SharePoint from IIS Web Site
The Application Pool Identity Account is an
account used during the creation of the first Web Application. The least
privilege administration requirements for this account are:
-
Use a separate domain user account for each application pool.
-
This account should not be a member of the Administrators group on any computer in the server farm.
The Report Server Account
Adding Reporting
Services to SharePoint, there is a fourth account that must have least
privilege, it is the Report Server account, here called SSRS_SERVICE. For this
account, very simple, it has no permissions at all. However, it might be useful
to use it during installation process, you will see why...
The Installation Sequence overview with the workarounds
Now let us see how we are going to use these accounts performing an
installation of Reporting Services and Sharepoint on two different computers,
and the workaroud to install the Reporting Services Add In for SharePoint.
01 - Use the SharePoint Setup Account to install Reporting Services on
the Report Server computer (it has local administrator permissions for this
computer because it will be used to install SharePoint on this computer later).
02 - Use the SharePoint Setup Account to install SharePoint on the
SharePoint Server.
03 - Use SharePoint Setup Account to create
the Web Application but when prompted, refence the Application Pool
Identity Account
The additional operation will be to grant the dbo or
db_owner permissions for the new created content database to the SPS_SETUP
account as specified in Technet documentation previously mentioned:
After
each database has been created, change the database owner (dbo
or db_owner) to the Setup User account.
04 - Configuring Reporting Services on the Report Server.
Here again there is additional operation to perform.
Let us examine
the permissions required by the account configuring SQL Server Reporting
Services 2008.
- Local administrator of the Report Server computer
If the account you are logged on with is not local admnistrator of the computer, you cannot open Reporting Services Configuration Manager.
- high privileges on the Database Engine
During the Report Server Databases creation, the configuration process is not only creating the ReportServer and the ReportServerTemp Databases, but also configuring the Databases (rights generation, connection rights application), and the account used by the process needs high privileges on the Database Engine. For example, there is a request on msdb database :USE msdb if not exists (select * from sysusers where issqlrole = 1 and name = 'RSExecRole') BEGIN EXEC sp_addrole 'RSExecRole' END
The consequence is that you cannot configure Reporting Services with SPS_SETUP account, since it has unfortunately not enough permissions on the database engine.
You have two solutions:
You grant temporary the database engine sysadmin
permission to the Setup account
You add temporary the SQL DataBase Engine
administrator account to the administrators group of Report Server computer, and
you use this account to configure reporting Services.
05 - Workaround for Add In installation:
When you are
installing Reporting Services Add In for SharePoint on the SharePoint computer,
you have temporary to grant the database engine sysadmin permission to the Setup
account AND to add temporary the Farm account to the machine Administrators,
otherwise the Reporting Services Add In installation fail over.
Installation Trick:
In the current installation
tutorial I have taken advantage of this workaround to perform Reporting Services
Configuration with the Reporting Services Account (here called SSRS_SERVICE).
Doing that I am able to check that the Report Server Web Service works well
before installing Reporting Services Add In for SharePoint.
In order to be
allowed to do that, I had temporary to grant the database engine sysadmin
permission to the SSRS_SERVICE account and to temporary add this account to the
Report Server computer Administrators. (only computer Administrators can
configure Reporting Services)
I will remind these operations in time using the red color.
Logon to SQL2008 with a domain user account that is administrator of the computer.
Launch SQL Server 2008 installation.
Follow all steps of the previous post Integrating reporting Services 2008 with SharePoint 2007 Step 1 - SQL Server 2008 installation from step 1 to step 9.
On Step 10 - Selecting Installation features, select:
- Database Engine Services
- Full-Text Search (it is for SQL 2008 Samples: Adventure Works).
- Management Tools - Basic (SQL Server Management Studio).
- Management Tools - Complete (SQL Server Management Studio complement included those for Reporting Services).
Follow the procedure until step 12
Use the same account for all services: SQL_SERVICE.
Set the SQL Server Agent account to be started Automatically, because it will be used for Standard or Data Driven Subscriptions in Integrated mode and thus, has to be enabled and always started.
Do not forget the Collation settings otherwise you will have an exception during SharePoint deployment.
This is the Installation Complete Screen Shot.
and the screen shot of the SQL Server Management Studio open.
Do not forget to configure connections protocol with SQL Server Network Configuration Area
Logon to SSRS2008SPIM with a domain user account that is administrator of the computer.
Launch SQL Server 2008 installation.
Follow all steps of the previous post Integrating reporting Services 2008 with SharePoint 2007 Step 1 - SQL Server 2008 installation from step 1 to step 9.
On Step 10 - Selecting Installation features, select:
- Reporting Services
Follow the procedure until step 12
Use the SSRS 2008 service account: SSRS_SERVICE.
We have to select the last option because SharePoint is not installed, neither on SHAREPOINT2007 computer nor on SSRS2008SPIM one.
This is the Installation Complete Screen Shot.
The screen shot of the Reporting Services Service.
The screen shots of the welcome Pages of the Report Server Configuration Tool
Logon to SQL2008 with SQL_SERVICE domain service account.
open SQL Server management Studio.
Create databases as in the previous post: Integrating Reporting Services 2008 with SharePoint 2007 - SharePoint Installation
In Management Studio right click Login node click "New Login"
On the "Login-New" Pop Up type "CORPORATE\SPS_SETUP" as new login name.
You can check the new Login creation in SQL Server 2008 Management Studio
Right click the new login and click "Properties"
Login-properties Dialog is opening.
Double click Server Roles, and in the opening Dialog, check "SecurityAdmin" and "DbCreator".
double Click User mappings, and in the opening Dialog, locate the two SharePoint databases SharePoint_Config and SharePoint_AdminContent.
For each of these databases, grant SPS_SETUP account the following permission:
"DbOwner".
Logon to SHAREPOINT2007 with the SPS_SETUP domain user account.
Launch SHAREPOINT 2007 installation as in the previous post.
Follows the steps 4 to 9. (Until closing the first installation wizard with the check box unchecked).
Open a command prompt and type the following line:
psconfig -cmd configdb -create -server SQL2008 -database SharePoint_Config -user CORPORATE\SPS_FARM -password Passw0rd -admincontentdatabase SharePoint_AdminContent
execute the command.
You will obtain this window after performing the command.
Run the SharePoint Product and Technologies Configuration Wizard as in the previous post, but with the multiple Server Environment parameters.
You can check the parameters on the following screen shots.
At the end of the process as usual, you will obtain the displaying of the Central Administration Home page
In order to have a Site Collection with a Root Web Site that can display SQL
Server reporting services 2008 Reports, DataSources and so on in a SharePoint
2007 document library,
Perform the steps 2 to 4 of the previous
post:
For step 5 because we are in a multiple server environement and want to be compliant with the least privilege administration principle, do the following:
In
the "Create New Web Application" page, Application Pool section, select "Create
new application pool" option, type the name of your new Application Pool, select
"Cofigurable" and type the name and the password of the Application Pool
Identity domain account.
Then,
perform your Site Collection creation and check that the Site Collection is
properly created.
Now, we have to grant the dbo permission to the
SPS_SETUP account for the brand new created WSS_Content_WEBAPP81 content
database. If we do not do that, we will not be able to perform operations using
stsadm command for the new created Web Application, its Site Collections,
its Web Sites, etc., because we will get an "Access Denied"
exception.
Logon to the SQL Server computer (SQL2008).
Open the SQL
Management Studio.
Locate the login for SPS_SETUP account.
Right Click the
Login and select properties.
In the opening dialog click "User
Mapping".
Locate the WSS_Content_WebApp81 database.
Check the check box
for the database.
In "Database role member ship
for: WSS_Content_WEBAPP81" pane check the check box for
db_owner.
Click OK.
First of all start by stopping the IIS default web site in order to avoid conflicts with the web service of Report server that also uses port 80.
Launch SHAREPOINT 2007 installation as in the previous post: Integrating
Reporting Services 2008 with SharePoint 2007 - SharePoint Installation
Follows the steps 4 to 9. (Until closing the first installation
wizard with the check box unchecked).
When Setup finishes, a dialog box
prompt you to complete the configuration of your server. Be sure that the "Run
the SharePoint Products and technologies Configuration Wizard now" check box
IS selected. (It is the opposite of what we have done for installation of
SharePoint 2007 on SHAREPOINT2007 server). 
Click "Next". On the "Connect to a Server farm" dialog
select "Yes I want to connect to an existing Farm". 
Click "Next". On the "Specify Configuration Database
Settings" type "SQL2008" for the databases server name, then click "Retrieve
Database Names" button. 
The wizard retrieves not only the SharePoint Configuration
database, but also the Farm Service Account... 
...so you just have the password to type. 
Click "next" to launch configuration and wait until the
"Configuration Successful" dialog. 
As usual, when you close this Dialog, SharePoint Central
Administration Web Site Home Page Appears. 
02 - Check SharePoint installation on SSRS2008SPIM
Take advantage of this page to check that SSRS2008SPIM server has now
joined the SharePoint Farm.
Click Operation Tab, then servers in farm link.
You can see the presence of the computer as a new Server of the SharePoint Farm.
There is another thing you can notice since SSRS2008SPIM
is a Web Front End. Open IIS and Notice that a "SharePoint - 81" Web Application
in now available. Right click the Web Application node in IIS and click
"Browse". 
The testReportingServices Site Collection Root Web Site
will be served by the SSRS2008SPIM computer as it is become a new Web Front End
of a SharePoint Farm. 
(If you prefer to keep using SharePoint Setup account (SPS_SETUP) to configure report server do not forget to Logon to SQL2008 and grant the sysadmin permissions to SPS_SETUP since it has not enough permissions to configure the Report Server Databases.)
Add SSRS_SERVICE to the Administrators Group of the Report Server computer (SSRS2008SPIM). To use Report Server Configuration Manager you must be logged as an Administrator.
Logoff from SSRS2008SPIM and re-logon with SSRS-SERVICE.Logon to SQL2008 and grant temporary the sysadmin permissions to SSRS_SERVICE
Open Report Server Configuration Manager and connect to the default instance of the current server
On the left menu click database, then, on opening dialog, click change database to open the change database dialog.
Select "create a new report Server Database", then click "Next".
On database server dialog notice that the SQL 2008 Server Computer has been retrieved, and that the account is SSRS_SERVICE.
Do not forget to test database connection.
On the next dialog select SharePoint Integrated mode.
On the next dialog select windows credential and type again SSRS_SERVICE
Check the summary and launch database creation
On the left menu of the report server Configuration Manager, this time click Web Service URL
Click Apply to provisioning the Web Service.
Click the URL to check the Web service. Notice that no mention of SharePoint is visible for the moment.
Logon to SQL2008 and remove the sysadmin permissions to SSRS_SERVICE
Click again the URL to check the Web service. Notice that the connection requires now the configuration in SharePoint. But we will not be able to perform it before having installed SSRS Add In for SharePoint on SHAREPOINT2007 computer.
Remove SSRS_SERVICE from the Administrators Group of the Report Server computer (SSRS2008SPIM)
Logon to SQL2008 and grant the sysadmin permissions to SPS_SETUP
Logon to SHAREPOINT2007 and grant the Administrator permissions to SPS_FARM
Then, perform SQL Server Reporting services 2008 Add In for SharePoint 2007 installation as shown in my previous post:Integrating Reporting Services 2008 with SharePoint 2008 Step 4 - Configuring Reporting Services for SharePoint 3.0 Integration - Part 2: Operations performed in SharePoint Central Administration.
Step 1 to 8.
When it is done, go to SharePoint central Administration, Application Management Tab, and locate Reporting Services section.
Open "Manage Integration Setting" Page and type the report Server URL.
For the "Authentication Mode" Section select "Trusted Account" that is the right mode for the present configuration in multiple servers with NTLM.
For more information there is a good post of Reza Alirezaei:
SSRS 2008 integrated mode: security
Open the Grant Database Access Page, and type the Report Server Computer name.
Click OK.
In the Enter Credentials dialog box, specify the User Name and Password to connect to the report server to retrieve the service account information. Be sure to enter credentials for an account that is a member of the local Administrators group on the report server computer. In our case, SPS_SETUP has the required permissions to perform this task.
When the page is refreshed, you can open a browser window and type the url of the report Server Web Service: http://ssrs2008spim/reportserver
Notice that you are now connected to the SharePoint Sites and Libraries. Your Installation is done!
Don't forget to:
Logon to SQL2008 and remove the sysadmin permissions to SPS_SETUP
Logon to SHAREPOINT2007 and remove SPS_FARM from the Administrators group.
I have chosen to install BIDS on SSRS2008SPIM computer to be as close as possible to a real Production Environment where BIDS will not be installed on the SharePoint machine.Doing that, I will be sure to succeed in deploying report remotely using the current environment.
Logon to SSRS2008SPIM with SPS_SETUP account. Run the SQL Server installation package, and select "Add a feature to the current installation". Select Visual Studio and wait until installation process is complete.
Open BIDS.
Create a report (if needed install Adventure Works as a sample Database).
You can do my previous tutorial:
Integrating reporting Services 2008 with SharePoint 2007 Step 6 - Report Creation and Deployment
For the project properties, type the following:
- TargetDataSourceFolder: http://SHAREPOINT2007:81/shared documents
- TargetReportFolder: http://SHAREPOINT2007:81/shared documents
- TargetServerURL: http://SHAREPOINT2007:81/
Perform deployment with BIDS.
If you try to see the deployed report now, you will have a credential exception. You will be able to see the type of this exception only on the report Server machine: SSRS2008SPIM.
The error type will only be displayed on the Report Server Web Service when you are logged on to SSRS2008SPIM. And Reporting Services errors can be examined. This is the path of the Log Files of SQL Server 2008 Reporting Services:
c:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles
To solve this error logon to SHAREPOINT2007.
Go to the Shared Documents documents library of the TestReportingServices Web Site, and locate the file Report1.rdl (that has not its extension visible).
Expand the Report contextual menu and select "Manage Data Sources".
The Manage Data Sources Page is displaying
Click the Datasource1 link to open the edit the data source connection information.
Select "Stored Credentials"
Use an account that have read permissions on the databse used for this report. For example in my case, I used the SSRS service account credentials, that will be quite never done in real life.
Check the check box: "Use as Windows Credentials".
You can now display your report in:
- RSViewerPage.aspx
- Report Viewer Web Part
- Report Server Web Service from the SHAREPOINT2007 computer
- Report Server Web Service from the SSRS2008SPIM computer
A special thank you to Mahmoud Meflah for his help regarding DataSource Configuration in SharePoint.
