5 Replies Latest reply: Apr 6, 2017 4:38 PM by Scott Parry RSS

    Creating Server Bookmarks Causes Crash



      I recently recieved a request for a comments field on a certain chart in one of my QV documents. After doing a little research I decided that an ImputField would be a good solution. However, I was disappointed to find out that user bookmarks were not saving Input Field values when connecting to the doc via IE plugin. Since server bookmarks save to the shared.file I decided that these were my best bet. I enabled the server bookmarks and server objects on both the doc and the QEMC. I created my server bookmark through IE plugin and saw the size of my shared file increase ( which I though was promising). However when I exit the doc and attempt to re-open to see if input field values stuck, my screen freezes ...and the server response time slows down greatly...and sometimes crashes all together. Has anyone experienced an issue like this with server objects and bookmarks?


      Any thoughts would be greatly appreciated.




        • Re: Creating Server Bookmarks Causes Crash

          Not sure if you're still grappling with this or not.  I had a very similar issue.   It was caused by a bad shared file.    To fix it, our server team used a utility called, "Qlikview Power Tools".     Not sure where to get it.


          Either way, Qliktech's take on using this tool appears to be that you're on your own if it breaks anything.


          So bear that in mind.    For us however, it broke nothing but fixed the problem.



          • Re: Creating Server Bookmarks Causes Crash
            Jonas Gros

            We have a similar problem. A shared file with over 400 MB caused a poor server performance for the whole application. All users were affected. Got many bad featback from customers. The shared file was not broken. It was just very fragmented and there was a very large bookmarks of a user with alone about 170 MB.

            Defrag the shared file did the job. I did not delete the 170 MB bookmark first. Now I did. Deleting this big one and defrag the whole thing shrunk down the filesize from 430 MB to 4.1 MB. No joke!!!

            Application works fine for now. A shared file killed down the useability of an whole application. Could not believe it.