Lot of problems with 2019.2.1
Lot of problems with 2019.2.1
Hello,
I updated the libraries to 2019.2.1 to use the latest enhancements.
After some use I found that errors pop up from nowhere, like "Exception generated from call destination" (or something like this, in italian) while just trying to add a new control to the dashboard.
Also I'm not able to open for design dashboards edited on 2019.2.1 desktop on the web designer, the same "Exception generated from call destination" comes out.
I still have problems with memory, after adding a new column to the chart query to use as a filter I get System.OutOfMemory exception… but there are only 2180 records and 8 out of 13 columns are just numbers, while the other 5 are char(5) codes.
I updated the libraries to 2019.2.1 to use the latest enhancements.
After some use I found that errors pop up from nowhere, like "Exception generated from call destination" (or something like this, in italian) while just trying to add a new control to the dashboard.
Also I'm not able to open for design dashboards edited on 2019.2.1 desktop on the web designer, the same "Exception generated from call destination" comes out.
I still have problems with memory, after adding a new column to the chart query to use as a filter I get System.OutOfMemory exception… but there are only 2180 records and 8 out of 13 columns are just numbers, while the other 5 are char(5) codes.
Soft System srl
-
- Posts: 6270
- Joined: Tue Mar 20, 2018 5:34 am
Re: Lot of problems with 2019.2.1
Hello,
Could you send us a step by step guide how to reproduce the issue?
Thank you.
Could you send us a step by step guide how to reproduce the issue?
Thank you.
Re: Lot of problems with 2019.2.1
Hello,
using 2019.2.1 (both web and desktop)
1. create a dashboard with web designer, reloading it works fine
2. edit the dashboard on the desktop designer
3. open the web designer and load the dashboard -> "Exception generated from call destination"
or
3b. open the dashboard on web preview (works fine)
4. edit the dashboard on the web designer -> "Exception generated from call destination"
I also found another problem.
After creating a dashboard and working on it for some time on the web designer I loaded it on the web preview and for every filter I set I get "ExecuteReader: the CommandText property is not initialized". On the web designer preview it works fine.
using 2019.2.1 (both web and desktop)
1. create a dashboard with web designer, reloading it works fine
2. edit the dashboard on the desktop designer
3. open the web designer and load the dashboard -> "Exception generated from call destination"
or
3b. open the dashboard on web preview (works fine)
4. edit the dashboard on the web designer -> "Exception generated from call destination"
I also found another problem.
After creating a dashboard and working on it for some time on the web designer I loaded it on the web preview and for every filter I set I get "ExecuteReader: the CommandText property is not initialized". On the web designer preview it works fine.
Soft System srl
-
- Posts: 6270
- Joined: Tue Mar 20, 2018 5:34 am
Re: Lot of problems with 2019.2.1
Hello,
We couldn't reproduce the issue.
Please send us reports after 1 and 2 steps.
Also, could you reproduce the issue on http://demo.stimulsoft.com ?
Thank you.
We couldn't reproduce the issue.
Please send us reports after 1 and 2 steps.
Also, could you reproduce the issue on http://demo.stimulsoft.com ?
Thank you.
Re: Lot of problems with 2019.2.1
Hello,
I tried with http://demo.stimulsoft.com and I seem able to edit the dashboard with the desktop designer and open it again on the demo designer.
I need to investigate more about this problem, it may be something I added on the designer.aspx.cs file.
Or it may be related to the database, I use MSSQL 2012
I'll reply as soon as I'll find something
Thank you for looking
EDIT: it seem that rebooting the computer fixed the problem with loading desktop created dashboards on the web version. Maybe the dlls weren't yet registered and it still used the 2019.1.1 ones
I tried with http://demo.stimulsoft.com and I seem able to edit the dashboard with the desktop designer and open it again on the demo designer.
I need to investigate more about this problem, it may be something I added on the designer.aspx.cs file.
Or it may be related to the database, I use MSSQL 2012
I'll reply as soon as I'll find something
Thank you for looking
EDIT: it seem that rebooting the computer fixed the problem with loading desktop created dashboards on the web version. Maybe the dlls weren't yet registered and it still used the 2019.1.1 ones
Soft System srl
-
- Posts: 6270
- Joined: Tue Mar 20, 2018 5:34 am
Re: Lot of problems with 2019.2.1
Hello
Ok.
Please let us know if you need any additional help.
Thank you.
Ok.
Please let us know if you need any additional help.
Thank you.
Re: Lot of problems with 2019.2.1
I found the reason of this problem, for reports.web I execute report.Compile() in the preview.aspx.cs Page_Load() event after setting some variables and the connection string, but for dashboards.web it seem to be a wrong thing to do.r.bianco wrote: ↑Fri Feb 15, 2019 7:41 am I also found another problem.
After creating a dashboard and working on it for some time on the web designer I loaded it on the web preview and for every filter I set I get "ExecuteReader: the CommandText property is not initialized". On the web designer preview it works fine.
Removing the instruction works fine.
Thank you for giving a look
Soft System srl
Re: Lot of problems with 2019.2.1
Hello.
You can't use the Compile() method for dashboards.
The dashboards are working in the Interpretation mode only.
Thank you.
You can't use the Compile() method for dashboards.
The dashboards are working in the Interpretation mode only.
Thank you.
Re: Lot of problems with 2019.2.1
Thank you
I had this suspect since it was the only line that made the error disappear when commented.
But what if I have a report.web with a dashboard page?
Reports now use their own preview.aspx and .cs just to not be broken by trying the dashboards, and as I understood reports must be compiled for both memory and expressions execution problems.
I had this suspect since it was the only line that made the error disappear when commented.
But what if I have a report.web with a dashboard page?
Reports now use their own preview.aspx and .cs just to not be broken by trying the dashboards, and as I understood reports must be compiled for both memory and expressions execution problems.
Soft System srl
Re: Lot of problems with 2019.2.1
Hello.
You don't need to run the Compile method explicitly.
The compilation will be run by our engine if it is needed.
Do you get any issue if you remove the Compile method?
Than you.
You don't need to run the Compile method explicitly.
The compilation will be run by our engine if it is needed.
Do you get any issue if you remove the Compile method?
Than you.