Hi


We are on Fp3 and this is regarding Buyer Homepage , we get the rerror as below for Charts/reports :

"ReportDesign (id = 1):
+ Cannot execute the statement.
SQL statement does not return a ResultSet object.
SQL error #1: Error, Execute Statement with statementID='76' : License error

odaconsumer.CannotExecuteStatement ( 1 time(s) )
detail : org.eclipse.birt.data.engine.core.DataException: Cannot execute the statement.SQL statement does not return a ResultSet object.SQL error #1: Error, Execute Statement with statementID='76' : License error at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.execute(PreparedStatement.java:567)"

Any ideas on how to resolve. This occurs only for some of the Charts/Reports in homepages.

Thanks A lot.

looks like you're missing a license in your SLM

License error at org.eclipse.birt.data.engine.odaconsumer

Birt is possibly licensed separately.

Dave

Hi

Thanks for the response. But if it were to be a licensing error, how could some of the other homepages -charts /reports (for ex. warehouse manager homepage) are working correctly without any error.

Regards.

Good question. but let's look at it another way.

If it wasn't a license error, why would it say "License error" in the error message?

Dave

Can you use the Report Viewer in Webtop with RPT- Design enabled Reports without error? You need a license for this kind of reports.
Can you search here or at Infor support website for this error?

Hi all,


i've encountered the same error in the past, and asked the support too about this.

this is the answer:

Dear Roy,

As per standard support policy, Homepages on ERP LN FP5 are 'controlled available'. So We suggest you to use Infor MyDay Product.

Should you need Homepages on ERP LN FP5 please contact your Support Account Manager in your region.

Hence, We are closing this incident now.

We appreciate your understanding.

Thanks,
Infor Global Support.

i hope you get a better answer though....this problem makes me have to install the myday :mad:

Roy

Hi All

Thanks for the Support and help. The problem got resolved.
Indeed it was a licensing problem.

Thanks.