search

xornand / alfresco-business-reporting

Automatically exported from code.google.com/p/alfresco-business-reporting
0 stars 0 forks source link

Report processing failed. org.pentaho.reporting.engine.classic.core.ReportDataFactoryException: Failed at query: #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. My installation was smooth, was able to create tables, I could see 
information entering in to the tables

What is the expected output? What do you see instead?
Getting error in Catalaina.out

What version of the product are you using? On what operating system?
Using 0.6.5 on Alfresco CE 4.0.e , on CentOS

Please provide any additional information below.
I am getting error message such as 
[layout.output.AbstractReportProcessor] [DefaultScheduler_Worker-4] : Report 
processing failed.
 org.pentaho.reporting.engine.classic.core.ReportDataFactoryException: Failed at query: SELECT
      COUNT(*) AS numberOfDocs,
     `document`.`sys_archivedBy` as deletor
FROM
     `document`
WHERE
      `document`.`sys_store_protocol`="archive"
  AND `document`.`sys_archivedBy`IS NOT NULL
GROUP BY
     `document`.`sys_archivedBy`
ORDER BY
     numberOfDocs DESC
LIMIT 10
        at org.pentaho.reporting.engine.classic.core.modules.misc.datafactory.sql.SimpleSQLReportDataFactory.queryData(SimpleSQLReportDataFactory.java:254)
        at org.pentaho.reporting.engine.classic.core.modules.misc.datafactory.sql.SQLReportDataFactory.queryData(SQLReportDataFactory.java:95)

I have added the catalina.out as attachment

Original issue reported on code.google.com by jjk.s...@gmail.com on 3 Oct 2012 at 6:26

Attachments:

GoogleCodeExporter commented 8 years ago 
Better late than never... (Not sure that is a valid English saying...)

Are you sure you have deleted content? The Report query is looking for deleted 
content. However, if the tool has never 'seen' deleted content, the core 
columns are not detected, thus not created. Then the report will fail. I 
considered pre-populating tables with deleted content, but then again that is 
not fail-safe either.

You have 2 options. 
1. Convince the SQL standardization body to enhance ANSI-SQL with a try-catch 
syntax
2. Delete some content and/or folders

Original comment by tjarda.p...@incentro.com on 13 Mar 2013 at 9:35

GoogleCodeExporter commented 8 years ago 
Since I think it works as intended, changed status to won't fix

Original comment by tjarda.p...@incentro.com on 13 Mar 2013 at 9:56