We found that with some of our clients this error crops up when people are making the documents a Favourite in IE, using the URL as shown when you open a document.
I'll have to aska colleague about the solution. You might find the favourites are causing an issue for you too.
Also, re: the cluster. Depending how you set the balancing to work, users may never see server 2 (unless you do round robin)
The plugin client talks to the server on port 4747. So once you click a link in the accesspoint to open the document in plugin, it needs a way to get back to the server. Most of the time it is the same as the AccessPoint.
Another thing you can try is just putting
in the link machine name.
OK makes sense. The DNS name we have in Link Machine Name is a name we have resolving to the Access Point server. Can you explain what putting "FromRequest" in for the Link Machine Name would do? Thanks.
It is some old code that is still used. What it does it looks at the URL the request came from and that is what it uses for the link machine name. If you can find an old version 9 manual you will find it in there.
Link Machine Name
If your QlikView Server cluster is not exposed outward
with the same name as is used internally, you must enter
your external name here in order for the QlikView Plug-in
and the QlikView Java clients to work.
If left empty, the name exposed for the clients will be the
computer name of the QlikView Server.
To mimic the behavior of version 8.5, you can enter
(FromRequest) here. The name exposed outward will
then be the same as the url the client uses to connect to the
AccessPoint, that is the setting is taken from the request
coming from the client.
Thanks for the info. I tried "FromRequest" and it didn't help. I also tried another QV plugin as things seem to be pointing there but to no avail as well. I have a call scheduled with QlikTech shortly and will report back the results. Thanks.
We are experiencing a smilar issue on our clustered environment running QV11 SR1. Can you expand on what your solution was? Did you need to add the second server to the Trusted Sites on every users machines or on the server itself?
Also we have found that even when we set a document to be available only on one of the nodes (through User Documents --> ... --> Document Available = Never), QlikView ignores this option and will still load the document here anyway. I just wondered if you might have experienced this same issue?
Trusted sites needs to be added on all client machines. We did this via system policy. We don't limit a specific document to a specific server so have not experienced that problem.