topic Re: Issue since applying security updates in QlikView https://community.qlik.com/t5/QlikView/Issue-since-applying-security-updates/m-p/1410627#M1325446 <HTML><HEAD></HEAD><BODY><P>Finally, the problem wasn't related to the security updates, that was only a fluke. </P><P></P><P>The real issue resides when a user toggles a Straight Table to a Pivot Table when there are a lot of dimension columns. The memory balloons up to the maximum available, then the server freezes.</P><P></P><P>We solved the situation by creating two distinct prepared objects, one pivot table, and one straight table.</P></BODY></HTML> Mon, 11 Dec 2017 20:38:47 GMT pgrenier 2017-12-11T20:38:47Z Issue since applying security updates https://community.qlik.com/t5/QlikView/Issue-since-applying-security-updates/m-p/1410626#M1325444 <HTML><HEAD></HEAD><BODY><P>Good morning,</P><P></P><P>Has anyone experienced issues with their QlikView 12.0 SR5 server since the installation of the following Windows security updates:</P><P>KB4038792</P><P>KB4040972</P><P>KB4040956</P><P>KB4038793</P><P>KB4036586</P><P>KB4034672</P><P></P><P>We've been experiencing strange behaviors on Virtual Memory usage on our server, which was very stable before those updates as can be observed using the Governance Dashboard:</P><P><IMG alt="QV-issues.jpg" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/177677_QV-issues.jpg" style="height: 184px; width: 620px;" /></P><P></P><P>Restarting the services fixes the problem for a while, but it is far from a permanent solution</P><P></P><P>Any insight would be most helpful.</P><P></P><P>Cheers,</P><P></P><P>Philippe</P></BODY></HTML> Mon, 26 Jan 2026 18:19:17 GMT https://community.qlik.com/t5/QlikView/Issue-since-applying-security-updates/m-p/1410626#M1325444 pgrenier 2026-01-26T18:19:17Z Re: Issue since applying security updates https://community.qlik.com/t5/QlikView/Issue-since-applying-security-updates/m-p/1410627#M1325446 <HTML><HEAD></HEAD><BODY><P>Finally, the problem wasn't related to the security updates, that was only a fluke. </P><P></P><P>The real issue resides when a user toggles a Straight Table to a Pivot Table when there are a lot of dimension columns. The memory balloons up to the maximum available, then the server freezes.</P><P></P><P>We solved the situation by creating two distinct prepared objects, one pivot table, and one straight table.</P></BODY></HTML> Mon, 11 Dec 2017 20:38:47 GMT https://community.qlik.com/t5/QlikView/Issue-since-applying-security-updates/m-p/1410627#M1325446 pgrenier 2017-12-11T20:38:47Z