I am developing my first Silverlight DV application. I thought I would start simply with a grid, a splitter, and a dataselector. I already had a datacube, so I followed the instructions on MS Technet to set up Http access to it. Here is the code:
<UserControl x:Class="TestPivotGrid.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" mc:Ignorable="d" d:DesignHeight="480" d:DesignWidth="640" xmlns:olap="http://schemas.infragistics.com/olap" xmlns:sdk="http://schemas.microsoft.com/winfx/2006/xaml/presentation/sdk" xmlns:xmla="clr-namespace:Infragistics.Olap.Xmla;assembly=InfragisticsSL4.Olap.Xmla.v11.1" xmlns:igPivot="clr-namespace:Infragistics.Controls.Grids;assembly=InfragisticsSL4.Controls.Grids.XamPivotGrid.v11.1" > <Grid x:Name="LayoutRoot" Background="White" DataContext="{Binding}"> <Grid.ColumnDefinitions> <ColumnDefinition MinWidth="310" /> <ColumnDefinition Width="Auto" /> <ColumnDefinition MinWidth="300" Width="300" /> </Grid.ColumnDefinitions> <Grid.Resources> <olap:XmlaDataSource x:Key="DataSource" ServerUri="http://imsds1/olap/msmdpump.dll" > <olap:XmlaDataSource.Credentials> <olap:XmlaNetworkCredential Password="xxxx" UserName="JSmith"> </olap:XmlaNetworkCredential> </olap:XmlaDataSource.Credentials> </olap:XmlaDataSource> </Grid.Resources> <igPivot:XamPivotGrid DataSource="{StaticResource DataSource}" DataContext="{Binding}" Grid.Column="0" HorizontalAlignment="Stretch" Margin="0" Name="XamPivotGrid1" VerticalAlignment="Stretch" /> <sdk:GridSplitter Grid.Column="1" Grid.ColumnSpan="1" HorizontalAlignment="Center" Margin="0" Name="GridSplitter1" VerticalAlignment="Stretch" Width="4" HorizontalContentAlignment="Stretch" Background="DarkGray" /> <igPivot:XamPivotDataSelector DataSource="{StaticResource DataSource}" DataContext="{Binding}" Grid.Column="2" HorizontalAlignment="Stretch" Margin="0" Name="XamPivotDataSelector1" VerticalAlignment="Stretch" /> </Grid> </UserControl>
In the ServerUri above, if I change "imsds1" to Sampledata.Infragistics.com", it works fine. I can see the AdventureWorks DB in the dataselector. If I change it back to "imsds1" I get nothing. This would suggest that something is wrong with my Http setup. However, it passes both tests given in the Technet article for testing your connection. If I enter http://imsds1/olap/msmdpump.dll in IE, I get the following correct response:
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
In SSMS, if I select Connect to Analysis Services and enter http://imsds1/olap/msmdpump.dll, it connects just fine and shows the databases and cubes.
I thought perhaps it was an authentication problem, so I changed the access from Windows Authentication to Anonymous. I also checked the permissions on the directories to make sure they are accessible to Everyone.
I saw some posts about problems with the grid in 10.3, so I upgraded to 11.1. No change.
At this point I'm stumped. Any suggestions?
Hello,
Nothing has changed regarding the XMLA service configuration and its IIS configuration. I have configured such service few days ago. You can check few things:
1. Put your xmla service uri (like http://localhost/olap/msmdpump.dll) in Chrome. If you have configured IIS properly you should see displayed the xml with an error message like mentioned in the blog post.
2. Look at Authentication section in IIS settings and make sure you have enabled Anonymous mode and the user you have specified there (the default is IUSR) is a member of a database's role in SSAS.
3. Please look at you network traffic in order to see if clientacesspolicy.xml is present and found during the request.
Regards,Plamen
Plamen,
Has anything changed in the 2012.2 release that's different from these examples given on your link? We're also using SQL Server 2012 for our application. Is there anything that we should do that hasn't been mentioned in the link you gave or has been updated for these new releases? Because we can't seem to get any of this working after going through all the documentation and community discussions.
We get a "System.Security.SecurityException". HRESULT 0x8013150A originating from the InfragisticsSL.Olap.Xmla assembly.
Thanks.
It turned out that I was missing clientaccesspolicy.xml. Once I added it, it fired right up.
Evidently, the fact that it was missing didn't keep SSMS from connecting, but did prevent my app from connecting.
Did you look at this post.
Regards,PPilev