agilelasas.blogg.se

To edit this action-sequence use the Pentaho Design Studio. This action-sequence was generated by the Report Design Wizard. This should have put the JNDI tag on the MDX lookup rule, instead it created a jdbc connection.Įrror: MDXBaseComponent.ERROR_0006 - Could not execute TopTen.xaction - (.MDXLookupRule)ĭebug: Starting execute of samples/reporting/TopTen.xaction (.ProSolutionEngine)ĭebug: Getting runtime context and data (.ProSolutionEngine)ĭebug: Loading action sequence definition file (.ProSolutionEngine)ĭebug: Adding variable source request to parameter output-type (.solution.SolutionRepository)ĭebug: Adding default value of "pdf" to parameter output-type (.solution.SolutionRepository)ĭebug: Adding variable source response to parameter report (.solution.SolutionRepository)ĭebug: audit: instanceId=9ada38ab-a028-11db-9348-f5d5c8b883ab, objectId=.ProRuntimeContext, messageType=action_sequence_start (.ProRuntimeContext)ĭebug: validateComponent validating component MDXLookupRule (.ProRuntimeContext)ĭebug: Validating component for action TopTen.xaction (.MDXLookupRule)ĭebug: validateComponent validating component JFreeReportComponent (.ProRuntimeContext)ĭebug: Validating component for action TopTen.xaction (.JFreeReportComponent)ĭebug: Validating component for action TopTen.xaction (.components.JFreeReportValidateParametersComponent)ĭebug: Executing action sequence (.ProRuntimeContext)ĭebug: Executing action definition: Iteration 0 (.ProRuntimeContext)ĭebug: audit: instanceId=9ada38ab-a028-11db-9348-f5d5c8b883ab, objectId=MDXLookupRule, messageType=component_execution_started (.ProRuntimeContext)ĭebug: execute pre-audit (.ProRuntimeContext)ĭebug: Setting component log level to DEBUG (.ProRuntimeContext)ĭebug: Initializing component (.ProRuntimeContext)ĭebug: executeComponent starting audited execute (.ProRuntimeContext)ĭebug: execute validation=true (.MDXLookupRule)ĭebug: executeComponent finished audited execute (.ProRuntimeContext)Įrror: RuntimeContext.ERROR_0012 - ActionDefinition for MDXLookupRule did not execute successfully (.ProRuntimeContext)ĭebug: audit: instanceId=9ada38ab-a028-11db-9348-f5d5c8b883ab, objectId=.ProRuntimeContext, messageType=action_sequence_failed (.ProRuntimeContext)Įrror: SolutionEngine.ERROR_0007 - Action sequence execution failed (.ProSolutionEngine)Ĭreated using the Pentaho Report Designer. Another issue, was that the I selected Use JNDI from the publish dialog.

But, since it's empty, it won't jump anywhere.

Doing the latter might prevent a navigation (new load) to the same page and instead try to jump to the element with the id in the fragment identifier. action'' will resolve to the page's address +, which will mean an empty fragment identifier.

After publishing a mondrian report create with the Report Designer, the report doesn't work when launch from the web.īy doing a little investigation, I noticed that the mondrian schema that I'm using on the desktop doesn't get published to the server so the datasource doesn't exists. action'' will resolve to the page's address.