FIX: Error message when you run a report in SQL Server 2005 SP2 Reporting Services by using a URL from a subscription: "Object reference not set to an instance of an object"

Article translations Article translations
Article ID: 971114 - View products that this article applies to.
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.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • In Microsoft SQL Server 2005 Service Pack 2 (SP2) Reporting Services, you subscribe to a report.
  • You receive the report URL that lists parameter values whose total length exceeds the value of the StoredParametersThreshold property.
    Note You can customize the value of the StoredParametersThreshold property. The StoredParametersThreshold property has a default value of 1500.
  • The list of parameter values in the URL is replaced with a StoredParametersID parameter.
  • You use this URL to run the report.
In this scenario, you receive the following error message:
Object reference not set to an instance of an object.

Additionally, the following error messages are logged in the SQL Server Reporting Services log file:
3wp!library!7!10/06/2008-11:52:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.Diagnostics.CatalogItemContext.ResolveServerParameters(IParametersTranslator paramsTranslator, NameValueCollection allParametersCollection, NameValueCollection rsParameters, NameValueCollection rcParameters, NameValueCollection dsuParameters, NameValueCollection dspParameters, NameValueCollection reportParameters, Hashtable& reverseLookup, String& itemPath)
at Microsoft.ReportingServices.Diagnostics.CatalogItemContext.ParseQueryString(String itemPath, IParametersTranslator paramsTranslator, NameValueCollection allParametersCollection, NameValueCollection& rsParameters, NameValueCollection& rcParameters, NameValueCollection& reportParameters, DatasourceCredentialsCollection& dsParameters, Hashtable& reverseLookup)
at Microsoft.ReportingServices.Diagnostics.CatalogItemContext.ParseQueryString(NameValueCollection allParametersCollection)
at Microsoft.ReportingServices.WebServer.ReportViewerHost.OnLoad(EventArgs e)

CAUSE

When the length of a list of parameter values exceeds the StoredParametersThreshold property in Reporting Services, the list does not pass through the URL. Instead, a StoredParametersID parameter passes through the URL, and the list of parameter values is stored on the server. When this occurs, the StoredParametersID parameter is used to retrieve the values of the parameters from the server.

However, the server handles incorrectly the shortened URL that contains the StoredParametersID parameter. Therefore, Reporting Services cannot retrieve the correct values to initialize the parameters. This behavior creates the NullReferenceException exception that is mentioned in one of the error messages from the "Symptoms" section.

RESOLUTION

Cumulative update information

SQL Server 2005 Service Pack 2 (SP2)

Important You must install this hotfix if you are running SQL Server 2005 Service Pack 2 (SP2). The fix for this issue was first released in Cumulative Update 14 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
970278 Cumulative update package 14 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.

Cumulative update information

SQL Server 2005 Service Pack 3 (SP3)

Important You must install this hotfix if you are running SQL Server 2005 Service Pack 3 (SP3). The fix for this issue was first released in Cumulative Update 5 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
972511 Cumulative update package 5 for SQL Server 2005 Service Pack 3
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:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. 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.

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 List of the builds that are available 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:
http://go.microsoft.com/fwlink/?LinkId=71711
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

Properties

Article ID: 971114 - Last Review: August 17, 2009 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
Keywords: 
kbsurveynew kbexpertiseadvanced kbqfe kbfix KB971114

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