Sharepoint Server and reporting services integrated configuration-go

Source: Internet
Author: User
I installed Moss yesterday and tried to integrate it with SSRs. After an afternoon, I wrote out the Troubles encountered by the Security Switch and shared them with you. According to msdn (1 February 2007), there are two levels of integration between SPS (Microsoft Office 2007 Sharepoint Server & Windows Sharepoint Server 3.0) and SSRs (SQL Server 2005 reporting services: 1. through Web parts, this is what is available in SPS 2.0, and the two Web parts used in SPS 3.0 are still 2.0. 2. Use the integration mode of SPs. In this mode, the SPS database needs to save the report content, and there is a synchronization process between SPs and SSRs databases. To use this mode, you must install SQL Server 2005 sp2 and SPS add-in for SSRs integration. I use a single server to Install SQL Server dB, reporting services, and Microsoft Office 2007 Sharepoint Server on one server. Both SSRS and moss databases use local SQL Server instances. Step 1: Install and upgradeProgram SS SP2 and SPS add-in processes are both smooth and there is no problem. Step 2: Configure IIS Because a web application has been created in moss and the web application occupies port 80, the website will be stopped by default. In the case of default installation, the two virtual directories of SSRs are under the default website. In this case, you need to specify a New TCP port for the default website in IIS and enable the default website.

The TCP port is 8080. Step 3: Modify the rsreportserver. config file
This step is shown on msdn. I don't know if it is necessary, but I did it.
Open \ Program Files \ Microsoft SQL Server \ mssql.3 \ Reporting Services \ reportserver \ rsreportserver. config. Find <urlroot> http: // esestt/reportserver </urlroot> [/url] and change it to <urlroot> [url] http: // esestt: 8080/reportserver </urlroot> the esestt here is the name of my server. Step 4: Configure SSRs
Open the Reporting Services Configuration Manager, select the "database installation" page, and create an SSRs database. Select "Create a Report Server database in SharePoint integration mode ".

After creation, the "SharePoint integration" page turns green and the virtual directory of report management is no longer available.
Step 5: Configure Moss
Open the SharePoint 3.0 management center and you can see the reporting services item on the Application Management page.

Click "manage integration Settings" and enter the SSRs URL and Authentication mode.

After "management integration Settings" is complete, return to the previous page and click "Grant Database Access Permissions". Here, you need to grant the SSRs account the permission to access the moss database.
Note that both the web service and Windows Service accounts must be able to access the SSRs database. Otherwise, the moss will prompt the error "an error occurs when you connect to the Report Server. Check whether the Report Server is available and configured in SharePoint integration mode. -- & Gt; the server cannot process the request. -- & Gt; the client finds that the response content type is 'text/html; charset = UTF-8 ', but should be 'text. xml '.", In addition, rs1_pointerror is displayed on the reportserver page of SSRs.
Here, I set the Windows service account to the Windows Account type. Both the computer account and the domain account can be used.

The Web service is set as a network service account.

To allow SSRs to obtain Moss database permissions, first add the network service account to the wss_wpg group.
In the SharePoint 3.0 Administration Center, the integration of Reporting Services option includes "granting Database Access Permissions ".

Enter the server name and Instance name, and click OK. Then, enter the account and the Windows Account previously set in the SSRs manager.
After configuring the database access permission, remember to restart IIS. It is best to restart Windows Server once.
After the restart, access the moss management center and continue to set the "set Server default value" option for SSRs integration. If the previous configuration is correct, the following page is displayed.
After this step is completed, the integrated configuration of SSRS and Moss is complete. After completing the integrated configuration of moss and SSRs, you can use moss to publish the SSRs project.
You can view a report in moss in either of the following ways.
One is to create, upload, and deploy report projects (including reports, report models, and data sources) in the moss library)

The other is to use moss for the Web Part of the report service.

To be continue... after a website set is created in Sharepoint, the report can be published in the library of the website. The steps are as follows:
Step 1.
In the top-level website of the website set, "website operations" -- "website Settings" -- "modify all website Settings"
On the "modify all website Settings" page, click "website set management" to make sure the "Report Server integration function" is activated.

Step 2.
In the SharePoint library that requires RS integration, click "Settings" -- "XX database Settings". Here I am "document library ".

On the "document library Settings" page, click "Advanced Settings" in "general settings ".
In "Advanced Settings", make sure "whether to allow content type management? "Option is set to" yes ". Step 3.
Go back to the document library settings page and click "add from existing website content type" in the "content type" column ".
Add three content types of Rs.

If the RS content type does not appear here, check whether the RS content type is available on the website or website set.

If you cannot find the RS content project, reinstall the add-in integrated Rs.
Step 4. Create an RS project in the database.

Note that if you have set backup access ing in the SharePoint management center, you must point to the default region when creating an RS project in the database. Otherwise, a region error is reported.

For example, the default URL here is Http: // 127.0.0.1 And exists is Http: // test/ To create an RS entry in the reportslibrary library. Http: // 127.0.0.1/reportslibrary /
For example, in Report builder, the report item points Http: // 127.0.0.1/reportslibrary /
Step 5. The reports developed in Visual Studio must be deployed to the SharePoint library.
In Visual Studio project properties, set targetserverurl to the Sharepoint Server URL ( Http: // <servername>/ )
Targetreportfolder is Http: // <servername>/<library>/<folder >
Targetperformancefolder is the data source directory
Transferred from Http://www.cnblogs.com/esestt/
Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.