asked on April 15, 2016
Hello,
I encountered an issue when trying to connect to my SSAS Olap Cube using the report.xml file. When I load my page, I keep getting this message : "Error! Cannot connect to datasource. Please check if Flexmonster Accelerator is running." It is running, and everything looks fine in the Accelerator Manager. In the Developer Tools' Console in Chrome I have a GET Error (405, Method Not Allowed). When I go to http://localhost:50005/, it displays :
Flexmonster Data Speed Accelerator for Microsoft SSAS
Proxy URL : http://localhost:50005/
So, what could be wrong ?
I attached my report.xml file, if it can help to find the issue.
Thanks in advance.
⋅ April 15, 2016
Hi!
I can't find attached file but I recommend you to check if your configuration has true e.g.
<dataSource type=”microsoft analysis services”>
<binary>true</binary>
<catalog>Adventure Works DW Standard Edition</catalog>
<cube>Adventure Works</cube>
<proxyUrl>http://localhost:50005/</proxyUrl>
</dataSource>
Regards,
Roman
⋅ April 15, 2016
Yes it has the binary tag set to true.
Sorry I don't know what happened to the attached file, I put its content below.
<config>
<dataSource type="microsoft analysis services">
<proxyUrl>http://localhost:50005/</proxyUrl>
<catalog>TestCube1</catalog>
<cube>Cube</cube>
<binary>true</binary>
</dataSource>
<defaultSlice>
<axes>
<axis name="rows">
<hierarchy>
<dimensionName>[dimLabel]</dimensionName>
<hierarchyName>[dimLabel].[Juridical Entity Label]</hierarchyName>
</hierarchy>
<hierarchy>
<dimensionName>[dimLabel]</dimensionName>
<hierarchyName>[dimLabel].[Budgetary Entity Label]</hierarchyName>
</hierarchy>
<hierarchy>
<dimensionName>[dimLabel]</dimensionName>
<hierarchyName>[dimLabel].[Envelope Label]</hierarchyName>
</hierarchy>
<hierarchy>
<dimensionName>[dimLabel]</dimensionName>
<hierarchyName>[dimLabel].[Struct Label]</hierarchyName>
</hierarchy>
</axis>
<axis name="columns">
<hierarchy>
<dimensionName>[dimAnnees]</dimensionName>
<hierarchyName>[dimAnnees].[Year0]</hierarchyName>
</hierarchy>
</axis>
</axes>
<measures>
<measure>[Measures].[Amount0]</measure>
<measure>[Measures].[Budget0]</measure>
<measure>[Measures].[FTE Paid0]</measure>
</measures>
</defaultSlice>
</config>
⋅ April 15, 2016
Hello Julien,
Could you please try to load in your application the report.xml file with the following connection to our Flexmonster Accelerator version 2.210:
<config>
<dataSource type=”microsoft analysis services”>
<catalog>Adventure Works DW Standard Edition</catalog>
<cube>Adventure Works</cube>
<proxyUrl>http://olap.flexmonster.com:8085</proxyUrl>
<binary>true</binary>
</dataSource>
</config>
Please let us know if the pivot component in your application works fine in this case.
Kind regards,
Iryna
⋅ April 18, 2016
Hello Iryna,
Thanks for your answer. Unfortunately, I get the same error using your configuration.
⋅ April 18, 2016
Hello Julien,
Thank you for the response.
Seems that there is an issue with a configuration on the client side.
Could you please provide us with a sample of the code where "flexmonster.embedPivotComponent()" method is called.
Also, could you please check the "client/demo.html" page from Download Package, does it work fine or not?
Thanks,
Ian
⋅ April 18, 2016
Using the "client/demo.html", I can connect to your cube. So I copied & pasted the source code of the page in mine and I get the error "jsSHA is not defined" in pivot.min.js file.
So my code is the same as the demo, but my web page includes a MasterPage, that's the only difference.
<div id="pivotContainer"></div>
<script type="text/javascript" src="flexmonster/flexmonster.js"></script>
<script type="text/javascript">
var config = {
licenseKey: "Z51T-5A1EB1-1M1B-080S-160P-2M0Y-1G1F-0U13-00",
dataSourceType: "microsoft analysis services",
// URL to the Data Speed Accelerator
proxyUrl: "http://olap.flexmonster.com:8085/FlexmonsterProxy",
// Catalog name
catalog: "Adventure Works DW Standard Edition",
// Cube name
cube: "Adventure Works",
// Flag to use Data Speed Accelerator instead of XMLA protocol
binary: true,
// Slice
rows: [
{ uniqueName: "[Product].[Style]" },
{ uniqueName: "[Product].[Product Categories]" },
{ uniqueName: "[Measures]" }
],
columns: [
{ uniqueName: "[Product].[Color]" }
],
measures: [
{ uniqueName: "[Measures].[Reseller Order Quantity]" },
{ uniqueName: "[Measures].[Discount Amount]" }
]
};
flexmonster.embedPivotComponent("flexmonster/", "pivotContainer", "100%", "615", config, true);
</script>
⋅ April 18, 2016
Thank you, it seems OK.
As for the “jsSHA is not defined” error, could you please verify that the contents of "html5-assets" folder and "flexmonster.js" file are up-to-date (the same as in the Download Package). Especially, pay attention to "html5-assets/js/sha1.min.js" file.
⋅ April 18, 2016
I copied & pasted the content of the "html5-assets" folder and the flexmonster.js file from the download package in my project and I still get the jsSHA error.
By the way, I can connect to my cube using the following code. Something's wrong with the Data Speed Accelerator, I don't know what
flexmonster.embedPivotComponent("flexmonster/", "pivotContainer", "99%", "99%", { jsPivotCreationCompleteHandler: "pivotCreationCompleteHandler" }, true);
function pivotCreationCompleteHandler() {
flexmonster.connectTo({
dataSourceType: "MSOLAP",
proxyUrl: "http://localhost/OLAP/msmdpump.dll",
catalog: "TestCube1",
cube: "Cube"
})
}
⋅ April 18, 2016
Julien,
We have prepared a simple demo for you - https://s3.amazonaws.com/flexmonster/bizzdev/FLEXMONSTER-2016-BIZZDEV-APR18.zip
It contains sample configurations for both XMLA and Accelerator.
Please check demo.html (configured for Flexmonstrer data source) and demo_localhost.html (configured for your localhost data source).
Hope this helps to figure out the issue.
Regards,
Ian
⋅ April 18, 2016
Thank you very much for the time you dedicated to my issue.
I tested the demo_localhost and everything is working as expected, so my Data Speed Accelerator is well configured. I tried the same code in my page and it doesn't work with the Accelerator so I guess the issue comes from my MasterPage. Maybe it adds some JavaScript code that the component doesn't like.
I'll try to find out what causes this issue precisely.
Again, thank you very much for your team's support and reactivity.
Kind regards,
Julien