Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I upgraded the version from 12.20 to 12.40.20100, 2019 april SR1, but there is a problem
I'm trying to connect to the QMC browser, but Internet Explorer can't connect, and an error like the attached picture appears.
But it's coming out fine in chrome
Up to what version of Internet Explorer is the upgrade QlickView version compatible with?
What's the matter?
Hi @jtj02080208
Checking logs is always one of the first things to do when troubleshooting issues.
When it comes to "how to disable", it is explained in the link that I have previously posted.
I will reformulate it here:
Should the key not be present in 12.30 or higher, insert it manually. Make sure to restart the QMS after saving the file.
Why would this help? IE is an obsolete browser, and it might not be able to properly handle forgery protection.
In 12.20 the default was "false", in April 2019 the default is "true".
So, by changing the value, you'll just go back to the old default, which should work with IE.
However, as said previously, while we allow people to still use Internet Explorer, you should probably consider moving to a modern browser.
Hi @jtj02080208 !
For the moment, we have decided not to take away Internet Explorer support, despite the browser not being supported by Microsoft. This is because the current technology in QlikView is still compatible with IE.
I'd still advise you to use a browser that is supported by the vendor, though, like Edge or Chrome. But you'll be able to use QlikView with IE, anyway.
You mention the AccessPoint in the description, and QMC in the title. The screenshot is about the QlikView Management Console. Are you having problems with both or just the QMC?
I would suggest that you look into the QlikView Management Service logs (standard location: C:\ProgramData\QlikTech\ManagementService\Log ) to see what is happening there.
You might want to disable this setting, to see if that solves your issue.
When it comes to compatibility you should always consult the system requirements in the help.
But Internet Explorer is generally supported by all version (system requirements for version details).
You picture shows the task status page in the QMC, so you must have been able to get that far.
It would be helpful if you can you explain a bit more, like when exactly in the process are you are getting this? Do you get the same message in the AccessPoint?
Where you able to find anything it the QMS logs?
Is there a reason that you are not upgrading to the latest version?
I made a mistake and edited the post.
I have a problem logging in to qmc.
Is there anything to check other than checking logs and disabling settings?
How to disable.
Are you treating the value of QVManagementService.exe.config as false?
I made a mistake and edited the post.
An error window appears when logging in after entering id and password in qmc in Internet Explorer.
Are you talking about the log file location for qms?
I don't know why it didn't, but I upgraded from 12.20 to 12.40. I think you're going to upload it slowly
Hi @jtj02080208
Checking logs is always one of the first things to do when troubleshooting issues.
When it comes to "how to disable", it is explained in the link that I have previously posted.
I will reformulate it here:
Should the key not be present in 12.30 or higher, insert it manually. Make sure to restart the QMS after saving the file.
Why would this help? IE is an obsolete browser, and it might not be able to properly handle forgery protection.
In 12.20 the default was "false", in April 2019 the default is "true".
So, by changing the value, you'll just go back to the old default, which should work with IE.
However, as said previously, while we allow people to still use Internet Explorer, you should probably consider moving to a modern browser.
I can't log in with Internet Explorer even after deactivation, is there anything else to check?
Beside everything above the qmc-access requires that you call it on the port 4780 and that this isn't blocked from the firewall or group policies. Also all the other services are using specific ports to communicate with each other. You should check this first.
- Marcus