Hi,
We have upgraded all Jet Reports components to the latest version for a customer.
After the upgrade, reports take much longer to process than before.
Current Jet Reports version: 23.3.1.2922.
Prior version before upgrade was 20.6.20143 afaik.
Date
Votes
7 comments
-
Ingo Korte Hi,
same problem here. We upgraded to 23 in summer (from a 22 Version) and experience severe performance losses in reports to the point we get errors in lookups possibly due tot time outs. We are running on 23.3.0.2321 at the moment. The problems persist.
We will try installing the latest update from last tuesday tonight to see if it fixes our problems.
If that doesn't work, we will reset the server and go back to the last 22 version or further until its working again.
We already had contact to tech support, but that did not help.
best regards,
Ingo
-
CascadiaDataworks Note that Insightsoftware support does not monitor these boards. I would highly recommend providing this feedback to the ISW support team.
-
Rob Fontaine Exact same problem here after upgrading the Jet Service Tier and Jet Excel Add-in to 23.4.0.3181 this week, but only affecting some users with no clear pattern. Insightsoftware Support has not been helpful so far, their only suggestion was to disable the option to share usage stats which is a hidden field in the Jet Service Tier database, but this didn't do anything to resolve the poor Excel performance. Clearly there is a bigger issue with the recent releases that needs to be investigated and the lack of communication with customers compared to the old days when Jet owned the product is disappointing.
We ended up having to downgrade users to 23.3.1.2922 and switch them all to "Local user profile" and then manually configure the data sources on each computer, which was a major time-consuming inconvenience with many remote users to support. Urgh!
-
Ingo Korte The problem seems to be solved for us.
We deleted the datasource and set up a new one. We updated the server to version 23.4.0.3181. We ensured that all designers use exactly the same datasourcesettings. Although we assumed that use of the service tier would have taken care of that, not all designers used the same settings.
I suspect, that in the end the deactivated setting "Leere Tabellen anzeigen" (in english i guess: "show empty tables") was the main cause for our problems.
I cannot be sure though, because we tried many things and had problems to identify the effects of single changes. We often experienced, that changes to settings of the datasource in the tier adminitration didn't reflect in the corrosponding datasource in the jet addins of the designers.
At the moment we hope that this situation lasts and won't touch the datasource settings ever again! 😁
-
Rob Fontaine This is the updated response I got this morning. #2 is definitely the issue we just went through. It's disappointing that this information is not being proactively shared with customers and that a fix is not being prioritized more quickly during the critical year-end period for many businesses.
1. There is an issue connecting to our CEIP servers which is causing a slow down. Typically this would make Jet navigation slow and slow loading of excel. You can check if this is set to Yes under settings --> app settings --> general --> Customer Experience Improvement Program.
2. There is a bug in 23.3.1 and later where the service tier connection runs a check whenever excel runs a recalculation (I think that's what you are seeing).
In this case, we'd recommend downgrading the service tier to 23.3.0, you should be able to keep the same database and the add-ins can stay on 23.4.
We'd expect this to be resolved in the release which is expected at the end of January/beginning of February. -
CascadiaDataworks Ingo brings up a good subject. Your Jet Service Tier should never be on a version behind the version of Jet Reports that is installed. It may be that you need to update your full deployment if you are having problems.
The Jet Service tier manages a central source of settings for users, but if you have users that created their own data sources, this could also account for some users having a different experience than others.
-
Ingo Korte CascadiaDataworks one adittion to your comment.
We used the same versions on the local installations and the tier. The differences lay in the datasource settings of the source that was provided by the tier. There were no local databases present.
That was astonishing to me, because I was under the impression, that changes in the tier datasource settings would be pushed out to the client datasources and override any local changes to the settings of the source.
That seems to be the case for the main settings, but not the settings open for change by the user.
Please sign in to leave a comment.