Forum Discussion

Nathan_H_'s avatar
Nathan_H_
Ideator I
5 years ago
Solved

SQL Report Error - itemtype doesn't have a prefix

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.

  • 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.

12 Replies

  • 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?

    • Nathan_H_'s avatar
      Nathan_H_
      Ideator I

      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"/>&amp;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.

      • Nathan_H_'s avatar
        Nathan_H_
        Ideator I

        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