SO, I found out what caused the problem. I had Report Error turned on and it didn't like the "itemtype" property that I had added. Once I removed the property, everything worked fine. Thanks for all of your help with this.
AngelIp,
Good day. The error message appears instead of the form that the report is supposed to generate. These reports are a weird form of a BOM (currently not using the OOTB Aras Part, I'm trying to fix this). The report is named the same as the RDL and the Report Query has this:
np:item_number=<xsl:value-of select="item_number"/>&rs:Format=PDF
I did not write the SQL reports. I made a couple of modifications to clean them up and they were working fine when I had them uploaded. I'm not sure what you are referencing by hardcode or reference to views. Thanks for your help.
Sorry, forgot to include the error message.
An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DataSet1'. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors
I think your "item_number" misses the prefix @ so report server cannot assign the variable:
E.g.
np:id=<xsl:value-of select="@id"/>&rs:Format=EXCELOPENXML
Trying your suggestion with @id, I receive this error now.
An attempt was made to set a report parameter 'id' that is not defined in this report. ---> Microsoft.ReportingServices.Diagnostics.Utilities.UnknownReportParameterException: An attempt was made to set a report parameter 'id' that is not defined in this report.
Trying it with @item_number, I receive the same error as before.
What shall you report return as result? Is it a generic report (e.g. show all Parts) or is the content based on the selected item (e.g. Part BOM)?
Your error messages indicates, that the @id or @item_number parameter is not specified in the rdl. But if you just have generic report, you wouldn´t need these variables at all.
Are you really sure the reports worked before? Do you have renamed the report items in Aras? That could case an error, as they always have to have the same name than the rdl.
