Here is my source code
<UserControl x:Class="mytest.MainPage" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:olap="http://schemas.infragistics.com/olap" xmlns:xmla="clr-namespace:Infragistics.Olap.Xmla;assembly=InfragisticsSL4.Olap.Xmla.v10.2" mc:Ignorable="d" d:DesignHeight="300" d:DesignWidth="400" xmlns:ig="http://schemas.infragistics.com/xaml"> <Grid x:Name="LayoutRoot" Background="White"> <!--<Grid.Resources> <olap:XmlaDataSource x:Key="DataSource" ServerUri="http://sampledata.infragistics.com/olap/msmdpump.dll" Database="Adventure Works DW Standard Edition" Cube="Adventure Works" /> </Grid.Resources>--> <Grid.Resources> <olap:XmlaDataSource x:Key="DataSource" ServerUri="http://localhost/olap/msmdpump.dll" Database="Animal Cube" Cube="Crop Test" /> </Grid.Resources> <ig:XamPivotDataSelector HorizontalAlignment="Left" Margin="249,0,0,0" Name="xamPivotDataSelector1" VerticalAlignment="Top" DataSource="{StaticResource DataSource}" /> <ig:XamPivotGrid HorizontalAlignment="Left" Name="xamPivotGrid1" VerticalAlignment="Top" DataSource="{StaticResource DataSource}" Width="243" /> </Grid></UserControl>
when I use the first Datasource(ServerUri="http://sampledata.infragistics.com/olap/msmdpump.dll"),everything is ok;but when I use my own Datasource(ServerUri="http://localhost/olap/msmdpump.dll) the XamlPivotGird and XamPivotDataSelector do not work. ServerUri="http://localhost/olap/msmdpump.dll is correct,and I used it in WPF version.
Hello, I have the same issue.
Do you have a solution for it? I can connnect to my OLAP server through http but the XamlPivotGrid cann't.
Hi, guys,
Have a look at this article:
http://blogs.infragistics.com/blogs/atanas_dyulgerov/archive/2010/01/27/how-to-set-up-xmla-http-access-for-sql-server-analysis-service-2008-and-access-the-adventure-works-2008-from-an-infragistics-pivotgrid-application.aspx
Take a special note on the part where you set the permissions for the access and also the client access policies.
All the best,
Atanas Dyulgerov
Could you provide more debug info. Try using fiddler to see if any exceptions are thrown. Also enable the Common Language Runtime Exceptions from the Debug->Exceptions dialog.
Have you looked into the log for your web server? Are you sure the client access policies are in the right place (in the root of the application directory - its a common error)?
How about the SQL log files? Any messages that might point us in the right direction?
I have checked the log files of SQL and the web server, but I can't find any problem.
Where the client access policies should be placed?
Are there any other problems in my code?
Can you give me a simple example about XamlPivotGird?
clientaccesspolicy must go in the IIS root for the server and be accessible.
"Place a clientaccesspolicy.xml file at the root of the domain where the service is hosted" - http://msdn.microsoft.com/en-us/library/cc197955%28VS.95%29.aspx This is the root of your application, not the IIS root. In some situations it might be different. If client access policy is in the right place and something else is breaking you should be getting the Not Found error.
If no errors are thrown at all and data is not loaded I would believe that debugging is not fully enabled. Try debugging in a different browser and playing with the debug settings of VS. I also did not understand if fiddler reported anything?
Hi Atanas, my msmdpump.dll works now, but there is still a problem. There are three databases in my server, only one can be loaded in the xamPivotDataSelector, the other two databases which are built later do not work. In the xamPivotDataSelector, I can only see the database names. The later databases’ cubes and measures cannot be loaded.
Do you have any suggestion with this problem? Thanks a lot...
Thank you for your help...
Hello,
It's due a bug caused by lack of some additional settings that are needed when more than one base is running on the server. When these settings are missing SSAS returns proper information only for the first database. Thank you point us to that issue. We are going to fix it in the next service release.Plamen.