FIX: Error message when you open a report by specifying a multivalued parameter in a URL in SQL Server 2005 or SQL Server 2008 Reporting Services: "Default value or value provided for the report parameter '<Parameter>' is not a valid value"

In Microsoft SQL Server 2005 Reporting Services or in Microsoft SQL Server 2008 Reporting Services, you disable session cookies by setting the UseSessionCookies property to False. Then, you define a multivalued parameter for a report. When you try to open the report by specifying the multiple values for the multivalued parameter in the URL for the report, you receive the following error message:

Cumulative update information

The release version of SQL Server 2008

Important You must install this cumulative update package if your computer is running the release version of SQL Server 2008.

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: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:

SQL Server 2008 Service Pack 1

Important You must install this cumulative update package if your computer is running SQL Server 2008 Service Pack 1.

The fix for this issue was also released in Cumulative Update 3 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: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. 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: Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3

Important You must install this cumulative update package if your computer is running SQL Server 2005 Service Pack 3.

The fix for this issue was first released in Cumulative Update 4 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: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: 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.

To work around this issue, use one of the following methods, as appropriate to your circumstances.

Workaround 1

Enable cookie sessions by specifying rs:ClearSession=true in the URL for the report.

Workaround 2

If you construct the URL for the report in an application, follow these steps to work around this issue:

1. In the application, call the LoadReport() method to load the report. When you do this, a new ExecutionInfo object is returned.
2. To pass the multivalued parameter to the report, call the SetExecutionParameters() function.
3. Construct the URL by referencing the ExecutionInfo.ExecutionID property of the object that was generated when you called in the LoadReport() method.

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

For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base: 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: For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the new improvements in SQL Server 2005 Service Pack 3, 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: