Solved: Share Session (Collaboration) with QV11.2IR - Qlik Community

Report Inappropriate Content · ‎2013-02-19

I'm not seeing the Share Session option with the AJAX client. Using QV Server 11.2 IR.

I've verified the following:

* System | Qlikview Servers | QVS@<servername> | Documents tab - Allow Session Collaboration enabled

* Documents | User Documents (for appropriate dashboard) | Availability - Session Collaboration enabled

(Server Objects is also allowed (for All Authenticated Users) for the document.)

Note to those using Publisher: You'll want to verify that the Server Objects and Availability sections on the Server tab of your Publisher task are set accordingly, otherwise what you set for the Document will be lost when the task rebuilds the document.

The test QVW document is a QV11.2 document, and under Document Properties (Server tab), all Server objects are enabled. I've also verified that for the Sheet Properties, Add Sheet Objects is enabled (only because someone suggested as much in another treaad-- it really makes no sense that this should be needed)

Yet, when I open the dashboard using AJAX, I do not see the button or option on the right side of the toolbar for Sharing a Session.

What am I missing?

Report Inappropriate Content · ‎2013-02-21

Worked with QlikTech this morning on this issue. We troubleshooted a good while, first trying to rename the QlikViewServer and DistributionService folders (in \ProgramData\QlikTech), then restarting services to verify. When that resolved it, we narrowed to QlikViewServer, then narrowed our focus to Settings.ini. After a lot of experimenting with various configurations, what it came down to this (and this makes absolutely no sense).... the QlikView Root folder specificiation.

On this server, the name of the QlikView root documents folder is D:\QlikViewRoot

There are multiple folder mounts specified, but all are named in a similar way, but with a .XXX suffix, so things like D:\QlikViewRoot.Admin, D:\QlikViewRoot.Demo, etc.

And for reasons not yet well understood (QlikTech is doing more testing), this sort of combination seems to trip the Session Collaboration. By specifing any other folder for the root (D:\test, D:\QlikViewDocuments, etc.), the problem is resolved.

QlikTech opened a new case to do more testing to see if they can reproduce on their end, so we'll see. If so, this will result in a bug report.

View solution in original post

Bill_Britt · ‎2013-02-20

Hi Donald,

I have tested this and it works for me.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.

Report Inappropriate Content · ‎2013-02-21

Worked with QlikTech this morning on this issue. We troubleshooted a good while, first trying to rename the QlikViewServer and DistributionService folders (in \ProgramData\QlikTech), then restarting services to verify. When that resolved it, we narrowed to QlikViewServer, then narrowed our focus to Settings.ini. After a lot of experimenting with various configurations, what it came down to this (and this makes absolutely no sense).... the QlikView Root folder specificiation.

On this server, the name of the QlikView root documents folder is D:\QlikViewRoot

There are multiple folder mounts specified, but all are named in a similar way, but with a .XXX suffix, so things like D:\QlikViewRoot.Admin, D:\QlikViewRoot.Demo, etc.

And for reasons not yet well understood (QlikTech is doing more testing), this sort of combination seems to trip the Session Collaboration. By specifing any other folder for the root (D:\test, D:\QlikViewDocuments, etc.), the problem is resolved.

QlikTech opened a new case to do more testing to see if they can reproduce on their end, so we'll see. If so, this will result in a bug report.

Report Inappropriate Content · ‎2013-02-21

UPDATE: QlikTech responded and confirmed they were able to reproduce, so this is being pushed up the chain as a potential bug (issue has been logged with the QlikTech Issue Analysis Team).

So just something to be aware of in the unlikely event you choose to name your mount folders and your root folder in a similar way and see this problem.