InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 22:21:10 GMT20http://www.sqlservercentral.com/Forums/Topic711622-150-1.aspxPlease post your T-SQL query if possible ?And also try to use SQL Server profiler to get the exact query being passed along with parameter values selected to the database engine.Tue, 09 Oct 2012 04:59:53 GMTH4Khttp://www.sqlservercentral.com/Forums/Topic711622-150-1.aspxHi, See this link efficent way to pass the multivalue parameter http://www.bi-rootdata.com/2012/09/efficient-way-of-using-all-as-parameter.htmlMon, 08 Oct 2012 06:45:35 GMTsanjeewan99http://www.sqlservercentral.com/Forums/Topic711622-150-1.aspxI have the exact same problem using 2005 server, I was wondering if anyone has come up with an solution?ThanksFri, 05 Oct 2012 05:45:34 GMTnbushttp://www.sqlservercentral.com/Forums/Topic711622-150-1.aspxHiI ve used this 'Select All' for a parameter....bt havent faced a single problem while running the report....Tue, 06 Jul 2010 22:46:51 GMTnitin.guglanihttp://www.sqlservercentral.com/Forums/Topic711622-150-1.aspxI've seen this myself. There seems to be no pattern to the occurences. I wonder if it gets fixed with the application of the latest service pack.Wed, 30 Jun 2010 14:02:37 GMTmmartin1http://www.sqlservercentral.com/Forums/Topic711622-150-1.aspxHi,I have an issue to report paramtersI have a report which group by data based on 2 paramters and also from and to dates The Issue is that whenever during the report execution I do a “Select all” from the second parameter List–and when I click view reports it does not display the report. it throws an error Default value or value provided for the report parameter 'ProcessNm' is not a valid value. But this error is not thrown always. It is weird that sometimes it works perfectly with “Select all” the parameters.I assume that the above error could be occurring since it is trying to pass a comma separated parameter string into the dataset query which accepts this parameter.If we may think that this is a data parsing issue due to the fact that staging database has different data than development, but then it should never execute it from SSRS at all. The issue is that it execute same query with all the parameters selected sometimes.The interesting part is that The error mentioned above does not appear always and instead it just clears out the parameterAnother thing observed was that if the refresh button (not view report button) continuously it displays the report correctly once and next time it throws error then again displays correctly.The SSRS environment on staging and development are SQL 2005, but on staging SSRS is 2005 but database is SQL2008. The SSRS logs shows the error which appear randomly appear while calling GetReportParamters internal function The same query was captured from tracer when it worked on staging and was executed and works fine from backend. Also there are no null values in the parameter lookup tablesAnyone faced this situation in your report with muliple paramter "select all"Appreciate any help or clues towards the resolution.RegardsMPWed, 06 May 2009 15:16:52 GMTmpaul4u