Alexandr, I have an idea at this point as to what may be the root cause given our trouble replicating things. Is there any chance you can recreate your Settings.ini file for your Desktop client to see if that fixes the issue? I suspect there may be a setting hanging out there that is causing the issue, so if the recreate fixes things, we have a workaround, and if you can get me your old and new one, we may be able to have a look to see what the offending setting may be at that point to document things etc...
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
Alexandr, thanks for that, @ToniKautto I think this may be an issue with Russian language version maybe? Does not explain how Rob W was able to replicate things though in that case, so I am still a little stumped, but that is the only thing I noticed in the ini file that likely might explain things.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
after removing the settings.ini and I said earlier that I tested it on a clean system on a virtual machine (English for system and QV).
Windows and QV were installed for the first time
I think just @ToniKautto not understand my English and do something not so. No other ideas. But I sent him a video that clearly shows how it happens. On forum post is deleted if fling exile.
You mentioned a check with a complete new OS and new QV in a VM and also testing the issue on further machines - but are those machines really significantly different to each other? If they are all quite similar they might have all the same "error" respectively unfortunate settings.
Here I'm thinking about processor-types, bios-settings and similar things which may be conflicting with the SR16 - SR19 releases (and like above already mentioned if it's worked with all the previous releases the change must have come from the changes/bugfixes of SR16).
Could you check this again on a complete different type of machine - maybe your private laptop?
Ok. the machines are quite different so that's rather unlikely that they all share the same kind of unfortunates errors/settings. At the moment I'm out of ideas.
I noticed the following. If you do not close the QV application, the following reloads do not give an error. But if you close the QV application (Not the project) the error will repeat. This is important when you try to retry the error.
I am sure that if anyone does exactly as in the video above, it will be possible to repeat the error.
@barakovskikh there is nothing unclear about your description. I tried closing and reopening the client 10s of times without seeing anything unexpected on my side.
I can see the numbers being distorted when QVW is opened, but every reload returns the correct sequence on my side. It does not seem possible for me to replicate the issues as shown in the video.
Throughout the whole discussion it wasn't mentioned if this issue produced each time exactly the same erroneous data or only quite similar ones or if they are quite randomly if it happens. This either in the kind of erroneous data as well in the amount of them. Maybe this could give some hints what could be the cause respectively what rather not and it may give an opportunity to automatically check the occurrence of this issue. Wrong data are probably very difficult to detect but to check the fieldvaluecount() against the noofrows() would be rather an easy job.
Further it might be helpful to check if this happens only with autogenerated data (autogenerate and also while with iterno) or if it happens by loadings from a qvd/txt, too.
Another thought goes in the direction to enforce a further processing of the data, for example with:
load ... where 1=1;
or
fabs(value * 1) as ...
This may produce further possibilities to bypass the issue and may also give Qlik some hints in regard of the internal processing.
.png "Former Employee"){kind=icon}
