topic Re: clustering in QlikView

clustering

Mon, 26 Jan 2026 18:19:17 GMT

Dear Member,

I have clustering Activity

When i Applied this licence 2nd server is off duty

Kindly suggest me the solution

Re: clustering

Bill_Britt — Tue, 26 Nov 2013 01:11:39 GMT

Hi,

There are a couple of things you can look at. First is your root folder point to a Network Share (\\servername\share) and second do you have in you license NUMBER_OF_CLUSTER_NODES;2;;

Bill

Re: clustering

Wed, 27 Nov 2013 17:19:32 GMT

Hi Ramachandra,

Looking at your post, it would seem you are not running (Active/Active) clustering, you could be running (Active/Passive) active with cold standby (DR) which does not allow both QlikView components to run together. As Bill suggests, do you have a clustered LEF key and have you purchased a second QlikView Server or Publisher? Have you defined shared storage joining the cluster together, using a windows CIF share (the only supported and recommend shared storage)? Have you changed the parameters in the QMC to use the shared storage correctly?

I hope this helps?

Thanks Steve

Re: clustering

Anonymous — Wed, 27 Nov 2013 22:03:40 GMT

If you do have a cluster license/lef and have checked the above

could you post a screenshot of your server setup from the system --> setup tab (General settings)?

Re: Re: clustering

Thu, 28 Nov 2013 03:31:34 GMT

Dear friend kindly find this print screen

which i am getting error

Re: Re: clustering

Thu, 28 Nov 2013 03:33:19 GMT

Dear steve,

Kindly provide details steps if you have along with print screen

rearlly it helps me lot

Re: clustering

Alejandro_Hernández — Thu, 28 Nov 2013 03:59:13 GMT

is the QVS service running on server 02? Is port 4747 open?

Re: clustering

Thu, 28 Nov 2013 04:45:19 GMT

Thanks for quick reply

how do i check port 4747 is workinfg or not

Re: Re: clustering

Thu, 28 Nov 2013 10:27:45 GMT

Hi Ramachandra,

Please look at the attached document, it should help you config clustering.

I hope it helps

Thanks Steve

Re: clustering

prabhu0505 — Thu, 28 Nov 2013 15:04:00 GMT

How many boxes you are using for this environment?

Are you using IIS?

Step 1. Install IIS and check whether you are able access accesspoint. ("No Server" is the information on AP)

Step 2. Install QVS1

Step 3. Install QDS and QMC.

Step 4. Configure only with QVS1 and QVWS details. Check whether you are able to access the QV default documents.

Step 4. Then configure QMC with QDS. Restart services whenever you are prompted for.

Step 5. Ensure again that it is working with Single Server.

Step 6. Install QVS2 and mapping it on QMC. Restart the services.

Re: clustering

Fri, 29 Nov 2013 09:18:47 GMT

Dear friend,

last few days i am suffering with below issue

that is

i applied cluster licence in server 01

and i mapped server 02 with cluster licence

now i am getting error qvs is off duty in server 02

i am rearlly struggled

i am happy if u provide answer

Re: clustering

Fri, 29 Nov 2013 09:24:01 GMT

This is the error i am getting

Cluster Join Denied by inmchnqv01.ind.rsa-ins.com. This could be because of mismatching version or document root

Re: clustering

Bill_Britt — Sun, 01 Dec 2013 11:58:55 GMT

Hi,

I have checked your license and it is a cluster license.

Make sure you are running the same version on both QlikView servers. You can do that from the about tab in the QMC.

Also, to cluster you have to setup a share someone on the network that both machice can get to throught the UNC path ( \\servername\share) and this has to be set on the first server as the root directory.

Bill

Re: clustering

Anonymous — Mon, 02 Dec 2013 08:00:51 GMT

Another few things you could check. are you running more than one QMS (management service)? Did you do a custom install when installing or a full install single machine? Also as Bill mentioned you should check your build, an easy way to do this is to use the Power Tool QVSDetector. This will show you your buildnr on the different machines and what rootfolders are being used, also if there is another machine using the same license in your network this should show up as well. The last one also causes the same error you are experiencing