Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi
Since a few weeks we have following warning message in the qlikview server event log:
Warinng SE_LOG: Shared - ApplyBM: Could not update the Recall time on bookmark with id:
Does anybody have an idea how I can solve this problem? We use QlikView Server 11.2. SR7.
Thx
Ramon
Hi Sacho
Ok I think this is not really a bookmark problem. In our case this warning only occurs when we print a report. We tested it out and created a simple application with one table and printed a report. After clicking on the print button you see this warning in the event log. It seems that qlikview reports refers information from the application by bookmarks.
Greetz
Ramon
Additional information:
The bug will be corrected in 11.20 SR10.
Bug: 69124
QlikViewServer - Warning SE_LOG: Shared - ApplyBM: Could not update the Recall time on bookmark with id: " is always printed
Hi Ramon,
today i'm out of order. I worked the whole day solving our bookmark problems. May be there exists a relation between our issues. Since last Friday many many of our user bookmarks (server/shared, etc.) didn't worked anymore. So i started to analyse the event log file. There i found some entries regarding your question.
Shared - ApplyBM: Could not update the Recall time on bookmark with id:
So i remembered, that that i changed our Cockpit by a small matter last Friday. I changed on a hidden folder one property of 2 listboxes relating to the system fields $Table and $Fields. I selected the property "Always one selected value"!. Having removed this option afterwards everything operated correctly.
I think the qlikview bookmark engine works like this. The add bookmark option "include selection in bookmark" without the option "apply on top" tries to restore the original clear state. But this isn't possible by the option "Always one selected value"! My be the qlikview error-handling routine issues an error because this state isn't possible and breaks the processing of the bookmark.
Can this be the cause of your log file warning?
Greets from Germany....
Cheers Sacho
Hi Sacho
Thank you for your reply. We scanned all applications and deleted all objects we do not really need. But the problem is still there.
But today we found out that this warning only appears in applications with a "Print Report" action. Which version of QlikView Server do you use? I think this must be a little bug...
Cheers Ramon
Hi Ramon,
we are using 11.2 SR 7. Our Bookmark problem is solved, but be found out that this type of log file entry "Shared - ApplyBM: Could not update the Recall time on bookmark with id:" still exists. It does not become clear what exactly triggers these warning.
Cheers
Sacho
Hi Sacho
Ok I think this is not really a bookmark problem. In our case this warning only occurs when we print a report. We tested it out and created a simple application with one table and printed a report. After clicking on the print button you see this warning in the event log. It seems that qlikview reports refers information from the application by bookmarks.
Greetz
Ramon
Additional information:
The bug will be corrected in 11.20 SR10.
Bug: 69124
QlikViewServer - Warning SE_LOG: Shared - ApplyBM: Could not update the Recall time on bookmark with id: " is always printed
According to Qlik, this issue was solved in the SR10 Release as Bug #69124: QlikViewServer - Warning SE_LOG: Shared - ApplyBM: Could not update the Recall time on bookmark with id: " is always printed.
You can check it out in the Release Notes of that versio.
Regards
Could this be caused by a customer using a older version of the IE Plug-in?
I'm running QV 11.2 SR13 and still seeing the 'ApplyBM: Could not update the Recall time on bookmark with id' message.
I have some users with legacy IE Plugin versions earlier than v11.2 SR10, and didn't know if that was the issue.
These users will soon be migrated to the a version of the plug-in to match the server, but I was curious if this was a server or client related issue.
Thanks,
B
I wish I could provide you with more information. We're still in v11.20 SR7 and this message appears in our logs. So, looking for a solution I stumbled with a KB article that stated that this solved in SR10, but we haven't upgraded yet.
Regards.