Hello Christian,

I am sorry to hear that there are multiple unresolved bugs that are stopping your development process. Would it be possible to send over a list with the issues, so I can forward them to the people responsible for the planning?

About the issue at hand, I have forwarded this for review and marked it as recently reported. This will increase its priority, but I cannot give any specific promises on when it is going to be resolved. This is why I suggest you to keep following this feedback item in order to get notified when its status changes.

Regards,
Martin Ivanov
Progress Telerik

Hello,

Thank you very much for the provided image and for taking the time to replicate the issue.

I can confirm that I was able to replicate the exception at my end and have updated our backlog item accordingly.

I'm afraid that I cannot suggest a suitable workaround for the time being so I can only advise you to follow this bug report to get notified about any changes in its status. I do apologize for any inconvenience caused by this.

Regards,
Dilyan Traykov
Progress Telerik

Hello,

It is not of importance what data is used as long as we manage to replicate the same exception which is causing the issue at your end. If you find it useful, you can use the data from the database used in our demo application. The connection string for it is the following:

            <pivot:AdomdDataProvider.ConnectionSettings>
                <pivot:AdomdConnectionSettings 
           Cube="Adventure Works" 
                    Database="Adventure Works DW 2008R2" 
             ConnectionString = "Data Source=https://demos.telerik.com/olap/msmdpump.dll;Catalog=Adventure Works DW 2008R2">
                </pivot:AdomdConnectionSettings>
            </pivot:AdomdDataProvider.ConnectionSettings>

Please let me know if you find this helpful.

Regards,
Dilyan Traykov
Progress Telerik

Hello,

Indeed, if you're not using the XmlaDataProvider which is used in the demo application in which I tested this exception, it is possible that the cause of the exception is different.

With this said, we would need to be able to replicate this exception at our end to be able to investigate a possible solution for it. If you do not wish to share your project publicly, you can open a new support ticket and provide it there. Please let me know if you would find this possible.

Regards,
Dilyan Traykov
Progress Telerik

Hello,

For the time being, you can try to use the AdomdDataProvider instead. I tested it in our demos application with the setup from the image you provided and received a response rather quicker than the XmlaDataProvider (which is used by default) without any exceptions.

Please let me know whether the AdomdDataProvider resolves the exception in your original application as well.

Regards,
Dilyan Traykov
Progress Telerik

Hello,

Thank you for the provided image and feedback.

I can confirm that I was able to replicate the issue in the demo and have thus logged it in our internal backlog. We will also consider implementing the cancel functionality.

Regards,
Dilyan Traykov
Progress Telerik