You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I set up datasources.xml with only 1 DataSource section, everythin works fine. Connecting to the XMLA-server works with different datasources, each in combination with different frontends.
When I set up datasources.xml with 2 DataSource sections, I get the following error. The error occurs independently from frontends, so it should be a matter of mondrian or xmla components. I both tried with an own datasource as 2nd DataSource section and (to eleminate other sources of error) with just a copy of the 1st datasource as 2nd DataSource.
Confirming the same problem,is there anyone to help?
The error comes from here at mondrian.olap4j.MondrianOlap4jConnection.(MondrianOlap4jConnection.java:183)
where datasource limit is set exactly to one.
Hi,
not sure, if this is a problem of mondrian or olap4j-xmla or olap4j-xmlaserver project:
I'm running Saiku from trunk (http://ci.analytical-labs.com/job/saiku-mondrian4/), including
When I set up datasources.xml with only 1 DataSource section, everythin works fine. Connecting to the XMLA-server works with different datasources, each in combination with different frontends.
When I set up datasources.xml with 2 DataSource sections, I get the following error. The error occurs independently from frontends, so it should be a matter of mondrian or xmla components. I both tried with an own datasource as 2nd DataSource section and (to eleminate other sources of error) with just a copy of the 1st datasource as 2nd DataSource.
Here is the error message:
This datasources.xml is working without errors:
This one works, but only 1 datasource ist shown up in the frontend (1:1 copy of the 1st DataSource section)
This one gives the error message, no datasource ist shown up in the frontend (1:1 copy of the 1st DataSource section, modified in DataSourceName only)
The text was updated successfully, but these errors were encountered: