2 comments
.NET 
The following error is also not uncommon with SQL Reporting Services:
An error occurred during local report processing.
The definition of the report '/ABC' is invalid.
The report definition is not valid. Details: The element 'QueryParameter' in namespace 'http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition' has incomplete content.
List of possible elements expected: 'http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition:Value##other:*'.
The last time this happened after I threw away some ReportParameters, which were linked to. The trick to solve this one is as follows:
- Do right-click; view code on the rdl file.
- Look for QueryParameter elements that have no value element contained.
- Enter a value element corresponding to the pattern below
<QueryParameter Name="MyParam">
<Value>=Parameters!MyParam.Value</Value>
</QueryParameter>
After this, close the rdl file, and open it again, so that de designer will parse the file again, an so, no longer give the error
After this, close the rdl file, and open it again, so that de designer will parse the file again, an so, no longer give the error
After this, close the rdl file, and open it again, so that de designer will parse the file again, an so, no longer give the error
2 comments
Hello – I am new to SQL Reporting Services and just trying to navigate my way around… I created several reports that I was able to deploy successfully. Now all of a sudden none of the reports that have parameters deploy to the server (data sources and one report without parameters deploy with no issues). I am able to view the reports in Visual Studio (I’m using VS 2003), but when I try to deploy I get an error message “An unexpected error occurred in Report Processing”. Could you please help?
Thank you!
Yuliya Reusze
Sorry, have not had this situation occur.. I’ve primarely been using the 2005 edition.
Maybe there is more information in the eventlog or does it list a stack trace? (which would help to hunt down the problem)
Raimondb