akrause Posted June 19, 2009 Share Posted June 19, 2009 I have defined a SQL2005 connection in the Workbench's connection dialogue which seems to work ok because i can browse all my tables of the SQL2005 database.I have defined my cube, dimensions and measures.Workbench forces me to use the "dbo" schema when using tables otherwise i can not continue modelling my cube.But when i try a MDX Query for my cube it presents the following error:SELECT[Measures].AllMembers ON COLUMNS,Hierarchize(([Zeit].[Alle].Children * [Debitoren (Gruppe)].[Alle Debitoren].Children)) ON ROWSFROM [sales]----------------------------------Mondrian Error:Internal error: Error while executing query [select [Measures].AllMembers ON COLUMNS, Hierarchize(([Zeit].[Alle].Children * [Debitoren (Gruppe)].[Alle Debitoren].Children)) ON ROWSfrom [sales]]Mondrian Error:Internal error: while building member cache; sql=[select "tblDimZeiten"."Jahr" as "c0" from "dbo"."tblDimZeiten" as "tblDimZeiten" group by "tblDimZeiten"."Jahr" order by "tblDimZeiten"."Jahr" ASC]Invalid Objectname 'dbo.tblDimZeiten'.This table does of course exist in my database, otherwise i could not have used it in the table dropdown in my cube definition.I need help! What's wrong here? Link to comment Share on other sites More sharing options...
akrause Posted June 20, 2009 Author Share Posted June 20, 2009 Is seems to be a bug (?) in the Workbenck only, because when i test the schema in JasperServer then everything is ok here. But it would be great if testing the schema directly in the Workbench would work too. Has anyone a solution to this problem? Post Edited by akrause at 06/20/2009 09:32 Link to comment Share on other sites More sharing options...
swood Posted June 30, 2009 Share Posted June 30, 2009 It looks like a bug. I have been working more on the Workbench and there were some issues with setting connections. Is the connection you are using the default or first connection in the list? If you set it to be the default, does that work? ShermanJaspersoft Link to comment Share on other sites More sharing options...
swood Posted July 3, 2009 Share Posted July 3, 2009 It was a bug. The new version of the Workbench, which is now released, fixes this issue. ShermanJaspersoft Link to comment Share on other sites More sharing options...
rodriguezum Posted July 8, 2009 Share Posted July 8, 2009 where can we get the new workbench? Link to comment Share on other sites More sharing options...
mgeise Posted July 10, 2009 Share Posted July 10, 2009 Look under "releases" within this (JasperServer) project - the workbench is listed there. MattJaspersoft Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now