Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I hope someone can assist or has experienced a similar issue:
We have 3 Enterprise Qlikview Servers running on VM's - all are currently experienceing the same issue relating to their internal authentication (not the authentication of Users):
In the Q(E)MC's the Services are all showing as ok apart from the 'Qlikview Server' that shows as 'Disconnected' (All the Services are running), when we try to access the License tab everything greys out and we are left with the message 'Server Is Down', most of the other pages within the consoles are also unavailable.
This appears to be related to wider amends that have been made to our Domain Controllers and / or AD Group policies.
I have managed to get the servers running so as they can serve documents to users by amending the relevant Config.xml file to use 'NTLM' authentication instead of 'Negotiate' however the Q(E)MC issue persists along with the fact that we can't shedule / admiister tasks and documents and the existing tasks aren't sucessfully reloading.
I'm in contact with Qliktech Support but they are at a loss to explain what the QVS is trying to do to point us in the direction of the issue.
Below is an extract from the 'Management Service' log file:
Hi matt
For you issue I have few things
1. Check weather the account you are logged in with have administrative privilages. if not assign admin privilages to it.
2. Might be your licenses have expired. in this case contact support for further assistance
3. restart the server service and try to go to license tab. It will be available for you for first 10 min in case of license expires.
If you still have something beyond this
do let me know
Regards
ASHFAQ
Also make sure that the user running the services is a member of Qlikview Administrators local group. If already, reset the permissions and re-apply policies.
Already tried / checked all those things.
This doesn't appear to be a 'QVS Issue' but until we know what the QVS is trying to do that results in the errors we can't identify what to fix.
The amends to the AD Groups / Domain Controllers have been inherited from above so our DBA's aer unsure as to whats changed.
Thanks for the suggestions.
Matt