An error occurred while getting property "result"

i got many errors of this kind when i was starting to develop schemas, and mostly were schema errors, even though the schema is validated (it has the correct formation) it does not mean that is correct, only by creating some mdx querys and running them you will get the full picture, also like sherman, i recommend restarting the server first

swood
Wrote:

I've tried to put schema definition in different folder and also I've tried to restart server but error still appears :(

Michal Szymanski

rodriguezum
Wrote:

If it was a schema error though wouldnt it fail when you uploaded it to the server? In these cases the schema and MDX query is validated, both in the workbench and on the server its self. Its only when you try to launch the view that the error occurs.

Here is a small example schema and MDX query that i have tried to upload.

<Schema name="Demo">
    <Cube name="Demo" cache="true" enabled="true">
        <Table name="febuary_billing">
        </Table>
        <Dimension type="StandardDimension" foreignKey="sequencing_division" name="Seq_division">
            <Hierarchy hasAll="true" primaryKey="sequencing_division">
                <Table name="febuary_billing">
                </Table>
                <Level name="seq_division" column="sequencing_division" type="String" uniqueMembers="true" levelType="Regular" hideMemberIf="Never">
                </Level>
            </Hierarchy>
        </Dimension>
        <Dimension type="StandardDimension" foreignKey="project_name" name="Project">
            <Hierarchy hasAll="true" primaryKey="project_name">
                <Table name="febuary_billing">
                </Table>
                <Level name="project" column="project_name" type="String" uniqueMembers="true" levelType="Regular" hideMemberIf="Never">
                </Level>
            </Hierarchy>
        </Dimension>
        <Measure name="New Measure 0" column="passed" aggregator="sum" visible="true">
        </Measure>
    </Cube>
</Schema>

and the MDX

SELECT
{[Measures].AllMembers} ON COLUMNS,
{([Project].[All Projects],[Seq_division].[All Seq_divisions])} ON ROWS
FROM [Demo]


----------------------------------

|                                  | New Measure 0 |
+--------------+-------------------+---------------+
| All Projects | All Seq_divisions |           150 |

I also tried the workbench generated MDX but with the same result

SELECT
[Measures].AllMembers ON COLUMNS,
Hierarchize(([Project].[All Projects].Children * [Seq_division].[All Seq_divisions].Children)) ON ROWS
FROM [Demo]
 

Now, both the workbench and the server can find no fault with this, until you try to run the view. Question is is it a problem with the server/workbench for sucessfully validating somethnig which is wrong? Or is the problem with the running of a view thats correct?

I have no doubt that i have made a mistake somewhere in my coding but its annoying to have two apps validate it ok, only for it to fall down at the last hurdle.

Hopefully we can all find a solution to this, i can almost taste the jasperanalysis goodness around the corner, plus the kudos this will bring when i can demo it to the bosses.

Today I've submited error  to tracker http://jasperforge.org/projects/jasperserver/tracker/view.php?id=4247

Michal Szymanski

http://blog.szymanskich.net

I had a similar problem where my database and query worked in older version of jasperserver (2.x)  but when attempting to upgrade to 3.5 it failed.

My data source is view of several tables for simplicity.   All data is entered into the relational tables and since my dataset is fairly small I took the liberty to create a View to create a fact table from the other relational tables.  It worked a treat until 3.5.

The schemas are unchanged and valid in the workbench and upload to the server.  What I found out, for my problem, was that the field type of one of my fields after a concatenation of an integer and text field produced a VARBINARY(263) data type.  This can be understood by the older version but not with 3.5.

Solution:  Change the data type on the database to VARCHAR by casting the integer to a CHAR before CONCAT.  Bingo it works!

Offending code:
 
      concat(`P`.`PROJECTNUMBER`,_utf8' : ',`P`.`PROJECTNAME`) AS ACTIVITY
 
to:
 
      concat(CAST(`P`.`PROJECTNUMBER` AS CHAR),_utf8' : ',`P`.`PROJECTNAME`) AS ACTIVITY
 
 
 
Cube:
	<Dimension name="Activity">
 
		<Hierarchy hasAll="true" allMemberName="All Activities">
 
			<Level name="Project" column="ACTIVITY" type="String" uniqueMembers="true" levelType="Regular" hideMemberIf="Never">
			</Level>
 
		</Hierarchy>
 
	</Dimension></td></tr></tbody></table>

 I am also getting the same error message in 3.5 with mysql datbase connection when trying to view an analysis view that was created without any errors in the process .

MDX query was executed sucessfully in Schema workbench:

SELECT

[Measures].AllMembers ON COLUMNS,

Hierarchize(([Service].[all services].Children)) ON ROWS

FROM [FSConfiguration]

javax.servlet.jsp.el.ELException: An error occurred while getting property "result" from an instance of class com.tonbeller.jpivot.tags.OlapModelProxy
 
javax.servlet.jsp.el.ELException: An error occurred while getting property "result" from an instance of class com.tonbeller.jpivot.tags.OlapModelProxy