18 Replies Latest reply: Oct 3, 2012 11:09 AM by qvd1rkqv RSS

QVS Cluster Issue

qvd1rkqv

We just added a 2nd QVserver to our environment for the purpose of load balancing documents for users. We're using the native QV clustering and are not running IIS. We use the IE Plugin.

 

Scenario:

Server1 - QVS - QVWS - Management

Server2 - QVS

Server3 - QDS

 

Server1 and Server2 are setup to Cluster. Upon setup we found all was working except that some users were getting an error in IE referring to (iis_authenticate ..... QVSTunnel.dll%3Fhost%3DServer2)

 

We opened a case with QlikTech which at one point they had us add a "Link Machine Name" in the cluster setup. This stopped the user errors .... however now all users are connecting to server1. Even though in the web logs it shows a descision is being made to load balance to server2 the document is being loaded on server1.

 

Caviat: the name that we entered in for "Link Machine Name" is a DNS name that resolves to server1.

 

Ports are open and server1 and server2 respond on port 4747. We are not tunneling.

  • QVS Cluster Issue
    Daniel Rozental

    Can you check the QVWS config file and see if both servers are being referenced there?

    • QVS Cluster Issue
      qvd1rkqv

      Thanks Dan. Here's the reference:  

       

      <AddCluster>

          <Name>QVCluster</Name>

          <LoadBalancing>LoadedDocument</LoadBalancing>

          <AlwaysTunnel>False</AlwaysTunnel>

         <AddQvs>

            <Machine>Server1</Machine>

            <Port>4747</Port>

            <LinkMachineName>DNSName</LinkMachineName>

            <Weight>1</Weight>

          </AddQvs>

          <AddQvs>

            <Machine>Server2</Machine>

            <Port>4747</Port>

            <LinkMachineName>DNSName</LinkMachineName>

            <Weight>1</Weight>

          </AddQvs>

      • QVS Cluster Issue
        Daniel Rozental

        Both servers should point to different locations not to the same, I think you should insist with support.

        • QVS Cluster Issue
          qvd1rkqv

          Thanks again. I just called QlikTech after over 24 hours of not hearing anything and found out that I'm not going to hear anything until Tuesday. So. I could not find any significant documentation on the Link Machine Name and what it does and how it works. Our servers and customers are all internal.

          • QVS Cluster Issue
            Daniel Rozental

            I don't think it applies in your case, at least what the documentation says is that it would be used for external users.

             

            - The users having problems were always the same ones or was this more like a random issue? Did you make sure all the users were not going through a proxy to get to eiher qlikview server?

            - Did you tried the same thing with ajax? were you getting problems there as well?

          • QVS Cluster Issue
            Bill Britt

            The link machine name is used for the Plugin Client. It should be the FQN for the server.

            • QVS Cluster Issue
              qvd1rkqv

              Dan - We're using the DNS names. I would prefer to remove the Link Machine Name as the clustering works fine without this in my environment however I get the QVSTunnel.dll error when some clients connect the Server2.

               

              Bill - Should it be the FQN for the Access Point or the QlikView Server?

              • QVS Cluster Issue
                Daniel Rozental

                Maybe some of the users have a firewall blocking the 4747 port for accessing Server2. Have you checked that?

              • Re: QVS Cluster Issue
                Bill Britt

                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

                 

                  FromRequest

                 

                in the link machine name.

                • QVS Cluster Issue
                  qvd1rkqv

                  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.

                  • QVS Cluster Issue
                    Bill Britt

                    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.

                    • QVS Cluster Issue
                      qvd1rkqv

                      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.

  • Re: QVS Cluster Issue
    Adam Vaughan

    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)

  • QVS Cluster Issue
    qvd1rkqv

    Issue resolved by adding the 2nd server in the cluster to Trusted Sites. See MS KB934366

     

    support.microsoft.com/kb/934366

    • Re: QVS Cluster Issue
      David Strudwick

      Hi

       

      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?

       

      Thanks

       

      David