Hi,
I have a problem that if you click cancel on the data loading dialog that appears after you select your parameters on the dashboard viewer and then try to refresh the dashboard again the datareader is not being terminated and the error appears like below:
Connection name: Test
Error message:
There is already an open DataReader associated with this Command which must be closed first.
The connection will eventually finish processing the data from the datasource and then you can run it again, but the idea of cancelling it is not working.
I have also noticed that the Report Designer also has this behaviour, but not the Report Viewer which you can press stop on the data loading at the bottom and it actually stops the datareader.
Also the data loading dialog on the Dashboard Viewer can go behind the form with Viewer on it, is there any way to prevent this or not show this dialog and handle the loading progress yourself?
Thanks
Craig
Hi Craig,
It is unclear which Cancel option you are referring to. If possible, provide a screencast to illustrate the scenario that causes the error during the data loading operation in the Dashboard viewer. We will check for a suitable solution.
Hi Alex,
Please see pictures in attached zip which show the data loading dialog which the dashboard viewer shows after you submit your parameters and if you press cancel on this dialog and then try to submit with different parameters the datareader doesn't close and the error appears like the error pic.
Thank you for your clarification, Craig. We will examine this behavior locally and will check for a suitable solution. Please bear with us.
Craig,
My attempts to reproduce a similar issue when cancelling the Data Loading procedure and reloading the dashboard were not successful. Please refer to the screencast produced on my test machine and let me know if I am missing something essential:
Cancelling the Load data operation in DashboardViewer.
Hi Alex,
Your data in your test looks to be returning to quickly for the problem to occur, you need to try an example with more data so that when you press cancel you have time to submit again before the datareader finishes.
Craig,
Thank you for your clarification. I will perform additional tests and update this ticket once I have any results. Your patience is appreciated.
Craig,
I have increased the total rows count returned by my sample query to three and four million, but I am still unable to replicate the error described in your original post. Just to clarify: are you using the latest version (v15.1.7) of DevExpress components on your machine? If not, I suggest that you download and install the latest installation package and install it on your developer machine.
Hi Alex,
Yes I am using V15.1.7.
This is really strange because I can replicate it every time on the dashboard designer and viewer. The test dashboard is a really simple one with 1 grid accessing data from a sql server stored procedure. I have attached the dashboard.
Hi Craig,
I have also used a sample dashboard only with one Grid element and linked the data source query parameter to the dashboard parameter. Would you please clarify how many records are fetched by your stored procedure? If you can provide your sample database snapshot to illustrate the issue, feel free to post it here. In addition, provide a screencast to illustrate the issue in action. This should make the situation clearer.
Hi Alex,
there are only 223 rows and it returns from sql management studio instantly. I have attached a video showing the problem.
It appears that you are referring to the Dashboard Designer (not the Dashboard Viewer that is used in my tests). I will try to reproduce a similar situation in my tests and let you know my results.
Craig,
We have reproduced a similar issue locally. It will require some extra time to find an appropriate solution. We will keep you informed on our progress.
Just a follow-up. We have also made a similar test using the next major version of DevExpress assemblies that are currently in the production state (v15.2) and found that it is not affected by this problem. Please let us know if you prefer to have this problem fixed in the current version (v15.1) and we will check for a suitable solution.
Hi Alex,
That is good that you have reproduced the problem. Will the next major release be a long time away? if not more than a week or so i'll wait otherwise I would like to get a release done by then. As the original post said I could see the same problem in the report designer and the dashboard viewer, is this fix to the library going to fix all the controls affected?
Hello Craig,
The next major release is scheduled for approximately late November or the beginning of December, so we're not going to ship a new version in the next few weeks. I've forwarded this thread to our R&D team to fix this issue in version v15.1.
Please watch for our updates in this thread.
Thanks,
Dmitry