Wednesday, August 24, 2011

SSRS Report and Subreport Debugging Issues Debugged!

Excuse the awful formatting; this is from a Word Doc. 

Report isn’t compiling: Go to Project - <Project’s name> Properties. Change the Start Item to the main report, and apply your changes. The report will now compile correctly.
  
The value expression for the query parameter ‘@param1’ refers to a non-existing report parameter ‘assigned_value’. Letters in the names of parameters must use the correct case: This comes from spelling the assigned value or parameter wrong. It also will not compile correctly even when fixed.
o   I’ve found, in order to recognize that the change has been made, copy the query and delete the dataset.
o   Next, create a new dataset and paste the query back in, and the error will be gone

The value provided for the report parameter is not valid for its type.
o   If this error occurs, it is due to a bug with the Allow Blank Value checkbox in the parameters definition.
o   Open up the properties of the parameter, switch it to the default datatype of string, uncheck the checkbox, then switch back to your previous datatype.

Error: dataset or values are undefined/do not exist: This can be solved a couple different ways depending on the exact problem.
o   Value:
§  Re-add it in the query. It will clear the error.
§  The value was from a different dataset, or a dataset with a different name. Change out the old ‘name’ for the new one. Yes, it actually matters to SSRS.
o   Dataset: If you had to delete a dataset and redo it, it will throw errors that the old table was the one it wanted.
§  Also, see below
§  Recreate your dataset.
§  Or you can delete the values in the report throwing the error.

Compile Warning: Report item not linked to a dataset
o   Right click on the table, Tablix Properties.
o   Drop down Dataset Name:, and select your dataset.


Subreport Errors: The subreport “X” could not be found at the specified location. Please verify the subreport has been published. This is an incredibly misleading error, and could mean a lot of different things. The best way to troubleshoot this is to go to the subreport and preview it; then you will return errors that make sense. Usually it’s a missing value, or your parameters arent being passed correctly or at all, etc.

No comments:

Post a Comment