Unable to view data on RadPivotGrid due to Clientaccesspolicy.xml and CrossDomain.xml error Please Help

[Sandeep]

Hello Everyone,
I tried to integrate RadPivotGrid with OLAP cube. But unable to get the data displayed on the PivotGrid due to Clientaccesspolicy.xml and CrossDomain.xml error. I have placed the clientaccesspolicy.xml and crossdomain.xml file in my root directory (C:\inetpub\wwwroot\OLAP). 
My ConnectionSetting Code for my OLAP Cude is as follows
<UserControl.Resources>
        <pivot:XmlaDataProvider x:Key="DataProvider">
            <pivot:XmlaDataProvider.ConnectionSettings>
                <pivot:XmlaConnectionSettings
                        Cube="ImskoncrettaDWCube"
                        Database="imskoncretta_DW" 
                        ServerAddress="http://localhost/olap/msmdpump.dll">
                </pivot:XmlaConnectionSettings>
            </pivot:XmlaDataProvider.ConnectionSettings>                   
        </pivot:XmlaDataProvider>
    </UserControl.Resources>
Could You Please tell me where am I going wrong....As I am new to this technology.
Thanks In advance
Sandeep

[Polya]

Hi Sandeep,

It appears that not everything is setup correctly for the server-client communication to work.
Please take a look at these articles that give information on how to Setup the HTTP access to the SQL Server, how to configure the IIS and how to debug some XMLA problems to get more information on the issue:
- Set HTTP access to SQL Server
- Debugging XMLA problems

Hopefully this helps.

Regards,
Polya
Telerik

 

 

[Sandeep]

Hi Polya

Good Day to you..

Thanks for getting in touch. I have followed all the step mentioned in the above email...But still unable to get the output data on the screen due to clientaccesspolicy and crossdomain error(404).Please find the attached snapshot of my project flow. Please let me know where I am going wrong.

Kind Regards,
 Sandeep

[Polya]

Hi Sandeep,

Here are a few suggestions where the problem might lie:
1) The clientaccesspolicy.xml is not setup correctly. You might need to chenge the http-request-headers to SOAPAction or SOAPAction,Authorization and provide authorization.
2) Also you might have limited database permissions for the role you created for the IUSR IIS default user.
I would suggest you to check very carefully if you have performed all steps described in this article. The clientaccesspolicy.xml setup is at the end of it, but please be sure you have completed all steps.

Also you can try to break when there is an exception - in Visual Studio go to Debug -> Exceptions and mark all checkboxes. This may give you more information what is the problem.

Regards,
Polya
Telerik