Microsoft KB Archive/940389

From BetaArchive Wiki
Knowledge Base


FIX: Error message when you display a report that uses SAP Business Information Warehouse 3.5 as the data source in SQL Server 2005 Service Pack 2 Reporting Services: “Can't find object <Object ID>”

Article ID: 940389

Article Last Modified on 8/31/2007



APPLIES TO

  • Microsoft SQL Server 2005 Reporting Services



Bug: #50001520 (SQL Hotfix)

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

SYMPTOMS

Consider the following scenario. You use SQL Server 2005 Reporting Services together with SAP Business Warehouse (SAP BW) 3.5. You create a report that uses SAP BW 3.5 as the data source. In SQL Server 2005 Service Pack 1 (SP1) Reporting Services, you create a query by using Query Designer in SQL Server 2005 Business Intelligence Development Studio (BIDS).

In this scenario, the report displays correctly in SQL Server 2005 SP1 Reporting Services and in SQL Server 2005 Service Pack 2 (SP2) Reporting Services. However, when you check the query in BIDS in SQL Server 2005 SP2 Reporting Services, the query is regenerated and the report no longer works. The query that is generated in SQL Server 2005 SP2 Reporting Services differs from the query that is generated in SQL Server 2005 SP1 Reporting Services.

Then, you take the following actions:

  • You re-create the report in BIDS by using the same query in SQL Server 2005 SP2 Reporting Services.
  • You deploy the report to the server.

When you display the report, you receive the following error message:

Can't find object <Object ID>.

Note In this error message, Object ID represents the actual Object ID value.

CAUSE

This issue occurs because the Reporting Services query definitions differ in SQL Server 2005 SP1 and in SQL Server 2005 SP2. In SQL Server 2005 SP1 Reporting Services, the query definition is stored in the <CommandText> element as escaped XML characters. In SQL Server 2005 SP2 Reporting Services, the query definition is stored in the <rd:QueryDefinition> element as regular XML characters.

RESOLUTION

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 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 2005 fix release. Microsoft recommends 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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released


Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 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 what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2


REFERENCES

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released


For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005


For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Keywords: kbsql2005rs kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced kbhotfixserver KB940389