Reports and schedules are deleted from the report server database if SQL Server 2008 or SQL Server 2008 R2 Reporting Services cannot communicate with the SharePoint object model

Article translations Article translations
Article ID: 2543217 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You configure Microsoft SQL Server 2008 Reporting Services or Microsoft SQL Server 2008 R2 Reporting Services to run under the Microsoft SharePoint integrated mode.
  • The ReportServer and ReportServerTemp databases are on a different SQL Server from the SQL Server that hosts the SharePoint content databases.
  • When Reporting Services cannot communicate with the SharePoint object model, synchronization occurs. This occurs, for example, when a communication failure occurs to the SQL Server that hosts SharePoint content databases.
In this scenario, all the reports and schedules are deleted from the report server database. When this problem occurs, the reports that use shared datasources fail, and no subscription will work.

RESOLUTION

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2567713 Cumulative Update package 9 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

For Microsoft SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2544793 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

For Microsoft SQL Server 2008 R2 release edition (RTM)

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2534352 Cumulative update package 8 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

For Microsoft SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 4 for Microsoft SQL Server 2008 Service Pack 2 (SP2). For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527180 Cumulative Update 4 for SQL Server 2008 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how to configure the Reporting Services for SharePoint 3.0 integration, visit the following MSDN webpage:
Configuring Reporting Services for SharePoint 3.0 Integration
For more information about storing and synchronizing Report Server content, visit the following MSDN webpage:
Storing and Synchronizing Report Server Content With SharePoint Databases

Properties

Article ID: 2543217 - Last Review: August 15, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2008 Reporting Services
  • Microsoft SQL Server 2008 R2 Reporting Services
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2543217

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com