2010
01.15
  1. Go to Central Administration > Application Management page and provision a new web application on port 81. The url for this web will be http://SRV1:88.
  2. Provision a new site collection using the template of your choice to the newly created web application (http://SRV1:88)
  3. Go to the server that will be hosting the Reporting Service (SRV1)
  4. Start the Reporting Service Configuration Wizard (All Programs >Microsoft SQL Server 2005 >Configuration Tools > Reporting Service Configuration
  5. In the Instance Selection menu, enter SRV1 in the Machine Name and MSSQLSERVER in the Instance Name. Click Connect.
  6. Verify “Service Status shows “Running” under the “Report Server Status”
  7. Go to “Report Server Virtual Directory” page and set configuration as follows:


 

  1. Verify that Report Manager Virtual Directory is grayed out. This may not grayed out until a new database is created in SharePoint integration mode.
  2. Go to Windows Services Identity page and set configuration as follows:


  1. Go to Web Service Identity page and set configuration as follows:


  1. Go to Database Setup page and set configuration as follows:


  1. Go to Central Administration > Application Management > Manage integration settings page and set configuration as follows:


Note: if you don’t see Configure Reporting Services Integration option on your Application Management, you need to make sure the feature is enabled.

  1. Go to Central Administration > Application Management > Grant database access page and set configuration as follows:


  1. Go to Central Administration > Application Management > Set server defaults page and set configuration as follows:


 

At this point you should be able to browse to http://SRV1:88/reportserver and see listing of site collections. It can take a long for the page to render time if you have many site collections. Our’s took about 30min for the page to come up.


 

  1. Troubleshooting

Problem:

Reporting Services Error

An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help Error executing child request for /ReportServer/Pages/ReportViewer.aspx.

The type Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessages, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c does not implement IReportViewerMessages or could not be found

Resolution:

Add <remove key=”ReportViewerMessages” /> in the web.config located in C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer.

You can verify the integration of Reporting Service with the SharePoint by uploading a report file to a SharePoint site and see if the report gets generated. You should test a bare minimum test report first.

Problem:

An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integration.

 


Resolution:

Add the DisableLoopbackCheck Registry Key to web front ends

  1. Open the Registry Editor (regedit).
  2. Open the following key: HKLM\System\CurrentControlSet\Control\Lsa.
  3. Create a new DWORD value called DisableLoopbackCheck.
  4. Set the value to 1.
  5. Reboot the server.

Problem:

Report Server has encountered a SharePoint error (rsSharePointError) Get Online Help User cannot be found.


Resolution:

Follow directions from http://krichie.wordpress.com/2008/09/12/resetting-the-author-on-a-sharepoint-site-or-wherefore-art-thou-author-redux/

and

http://vspug.com/nrdev/2008/08/26/tip-report-server-quot-user-cannot-be-found-quot-error-fix/

Problem:

Reporting Services Add-in for Microsoft SharePoint Installation fails and rolls back. “Product: Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies — Installation failed” shows up in the event log.

Resolution:

1. Open the command window (Start>Run type cmd and press enter)

2. Navigate to the path where the installer (SharePointRS.msi) is stored

3. Execute SharePointRS.msi SKIPCA=1

4. CD to %temp%

5. Execute rsCustomAction.exe /i  to auto-configure the installed files.

No Comment.

Add Your Comment