Good day all. This error just started with a couple of our reports. I have not made any updates to the RDL files, so I don't understand why this is occurring. Any help would be greatly appreciated. Thank you.
Good day all. This error just started with a couple of our reports. I have not made any updates to the RDL files, so I don't understand why this is occurring. Any help would be greatly appreciated. Thank you.
Hi Nathan,
when do you see the error? When you try to run the reports?
When RDLs haven´t change, do you still use the same Innovator?
How are the SQL queries used in your SQL? Do you hardcode the queries or do they reference to views?
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.
The reports worked in the past. I don't remember making any changes to these reports in the month or two. Any changes I made I would test to make sure that they worked correctly. I'm really confused about what has changed to cause this problem.
Can you post your complete first error message? It wasn´t clear if it comes from Aras or from the report server. The other error with the "@" definitely was caused by report server.
But did the first one also contain the "Reporting.Services" hint?
Do you call the Report directly, or do you use a Form in between?
Edit: You call directly, but do you have an additional Method in the Report item?
This is the full 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
But this is the Error message you get when using @. I would revert the change, cause if it worked before without @, then this wasn´t the error. I assume you have Innovator related problem.
And you still haven´t answered the question if you have generic or item-based report.
The report is Item based.
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.
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.
