Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We have configured QMC to be accessible by Active Directory IDs (windows id). When user login to their machines using AD id, if they open QMC link, it will automatically take them to QMC without asking any details. All of sudden, since yesterday, QMC is showing a pop-up to enter windows credentials and not going inside.
Document Admins and Qlikview Administrators are not able to login QMC as it is prompting for windows credentials.
Can anyone experience this issue ? Appreciated your help and suggestions on this issue.
Best Regards,
Mamidipaka.
Have you tried the "classical" advice of restarting the qlikview services and if this failed to restart the machine?
- Marcus
Have you tried the "classical" advice of restarting the qlikview services and if this failed to restart the machine?
- Marcus
Hi Marcus,
Yes, I have restarted the services first and then restart of machine also, but still the problem exists.
-Thanks.
i have experienced this issue one time and it walks again without any action .
have a look to your services if everting is started and like said Marcus it will works normally .
Hi Marcus,
After a first restart, no change in the issue. But after a couple of restarts, issue is resolved and QMC working fine.
We have not done anything except restart the server. Looks very strange. As this is a PRODUCTION server, restarting the server is also a big issue and need many approvals.
Thanks for your advise.
Best Regards,
Mamidipaka.
Reasons for this behaviour could be a lack of RAM for the whole system which could corrupt some windows services. If this happens (too) frequently you should take a look on the working set settings from the qv server and to the ressourcen consumption within the qv logs (governance dashboard) and within the windows event- and performance-logs.
Another reasons could be windows updates or security-changes within your domain (adjusting from group policies and so on) - quite often I notice strange behaviour from my system after them and simply restart it instead of searching and fixing anything manually.
- Marcus