Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
You stated in your other post you are using Certificate Trust option, so in that case the service accounts do not make any difference, other than the fact whatever account is running the services on each server does need to be in the QlikView Administrators local security group as well as local Administrators security group, but the QlikView Service authentications are being handled by our self-signed certificates which are created by QMS the first time the service starts and it realizes Certificate Trust is in use. These certificates must exist on all nodes in the environment, so if QMS and QVS are on different machines, you have to get the certificate pushed from the QMS to the QVS server for starters.
Here are some Help links that may be useful:
The second one likely being the one of most use in this case, that will walk you through what you should have done to get the certificate pushed to the other server. Once that is done, things should then go live.
Regards,
Brett
So what you likely have going on is a port issue at this point, be sure both TCP 4747 and 4749, the latter is what is used for the QMS to QVS certificate authentication, and I am betting that is blocked from the QMS to the QVS in this case? If you are getting the dialog in the png you attached, if you go to the other server and open a web browser and put in the URL and then the password on the resulting page, you should receive a 'successfully unlocked' message at that point. Sorry for the long delay here, I do not always get a chance to get back to posts quickly, apologies for that.
Regards,
Brett
You are currently running your Management Service on another server than your QlikView Server service? Are the two able to communicate, i.e. did you correctly configure the connection to the original server in QMC? You should do this for all services that are hosted on another machine.
Also check your original server for blocked ports in Windows Firewall. Each service uses a specific port for communicating with non-client parties. The QMS should be able to get in touch with the QVS through the qvp port.
You can always put your QMS in Debug logging mode (see QMC->System->Setup->Management service->General->Logging level) and let it explain in detail what kind of problems it is experiencing when trying to talk to the QVS.
Hi. Can you provide screen capture of what you're seeing in QMC > System > Licenses > QlikView Server > QlikView Server License tab? Also, are you receiving a specific error message? Can you provide the exact wording of the message?
If the QVS is down and your organization isn't able to use QlikView, I would suggest you contact Qlik Support and get a case started.
The QVS is probably not "down" but the Management service cannot talk to it. If you cannot talk to it, you certainly can't send it a new license. The QVS needs the license information to become usable, not the QMS.
You need to fix these communication problems before you can license a QVS.
And be very careful. Do not use the same license a second time, or you will take down the server that is currently servicing your end-users (both will go "off-duty")
Hi,
Did you try to do a telnet instead of a ping to test all the need port between the QMS and QVS machine ?
https://support.qlik.com/articles/000019890
https://support.qlik.com/articles/000003505
More information on our KB - https://qliksupport.force.com/QS_CoveoSearch#t=All&sort=relevancy
Cheers,
How are the QlikView services authenticated - by AD groups or certificates? You can check in QMC > System > About, referring to the QMS service under the Product Information heading > Service authentication