Hello =)
Cube olap dll files used by XMLADataSouce SQLSERVER2008 R2 is not supported?
sampledata.infragistics.com/.../msmdpump.dll If you specify this address ServerURL successful run
Dll file created in SQL_SERVER2008 R2 fails not successfull from the PivotGrid
dll files is not problem PivotGrid do not support the SQL SERVER2008 R2?
Samples provided by the SQL SERVER versions infragistics.com - SQL 2008 SP1 (10.00.2531)I made a dll version of SQL 2008 R2 (10.50.1600.1)Dll that I created to be used in PivotGridDo I need to create in SQL_2008 SP1?
I use the environment
Window 2008 R2 Enterprise
SQL SERVER 2008 R2 Enterprise
Thanks.
Have a nice day :)
Hi
Did you try with control from latest Service Release? I recommend you to use it. If you are not sure about your version please contact you support department.
RegardsTodor
Thanks, but
I was using the latest versionHere is the address http://es.infragistics.com/downloads/default.aspxNetAdvantage_SilverlightDV_2010 Vol.3 not this latest version?I've used this version takes.Why it was not loaded?I don't know that why dll files made in SQL SERVER2008 R2 version didn't load.
Dll files do not create a problemSo in SQL SERVER 2008 R2 does not support the PivotGrid?I want to hear the correct answer
Thanks =)
Hi,
I just finished testing your scenario from scratch on a clean machine. New MS Win7 install, new SQL Server install, new PivotGrid sample with latest 10.3 assemblies.
I can confirm: XamPivotGrid works with SQL Server 2008 R2 with Adventure Works 2008 R2.
I also doubt this is an issue with the PivotGrid's version. Try working with your security settings. Make sure the user that runs the olap application in IIS is also an SQL Provisioning account. Check your clientaccesspolicy.xml - both its content and its location.
I hope this is helpful.
Atanas
I installed a fresh copy of win7, new instance of sql 2008 r2, then the adventure works sample database, I followed my own howto article and it all worked straight away.
You start by verifying that your clientaccesspolicy,xml file is in the root of the webserver, not in the application folder. This is a common mistake. In my case it is in C:\inetpub\wwwroot and its contents are:
<?xml version="1.0" encoding="utf-8"?><access-policy> <cross-domain-access> <policy> <allow-from http-request-headers="*"> <domain uri="http://*"/> </allow-from> <grant-to> <resource path="/" include-subpaths="true"/> </grant-to> </policy> </cross-domain-access></access-policy>
If this does not help find out which is your provisioning account. When you find it, make sure it is the one that starts the olap application in IIS settings.
Was previously using the latest version fromclientaccesspolicy.xml file was also setIt must be running in SQL-SERVER2008 R2?So I start from where you solve the problem?IIS? SQL-SERVER? Have relevant information?Thanks for answers