Discussion Board for collaboration on QlikView Management.
Hello all,
Qlikview 11 has been installed in our server instead of Qlikview 10.
After the installtion, all the services seem to be ok :
However, when when I try to go on the accesspoint, I have the following message :
Have you got any idea of this problem ?
Thanks for your help,
Best regards,
Jaymerry
There is a couple of things that will cause this. The first thing to check is to make sure that the QlikView IIS application pool is set for .net V4. If not set it and try again. If that doesn't work then run this command
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i and go back check step one.
Here a screenshot of the accesspoint message :
Thanks,
Hi Jaymerry,
The .Net 4 is a required in the QV11 installation.
You'd better install the .Net 4 framework before installing the QlikView server.
Hope this helps.
.NET 4 framework is a requirement for QV11, so this should not be the issue.
I have the same issue while using a mobile browser on an android phone and while using Firefox on a windows 7 machine, chrome and IE are fine.
Hello all,
I'm trying to go on the access point with IE, on windows 7.
.NET 4 framework is installed ; the authentification type is Ntml..
Have you any idea of this problem ?
Thanks for your help
Are you running IIS or QvWebServer? Is the QVS service reporting OK in the QMC? Can you use "Open in Server" from a Developer/Desktop client and get a document list and open documents? Have you tried starting Fiddler (www.fiddler2.com) web debugging tool to see if you get any error responses back from the web server?
Hello,
Sometimes I've got the same problem.
The page is not loading and keep showing "Loading Content".
We are using a reverse proxy and we are suspecting that this may cause the problem.
Regards
Kevin
Hi all,
I also had this problem with QV11 using IIS.
The problem was solved by using the qlikview webserver instead of IIS.
I suppose there was in the IIS configuration. But, as using the QV webserver is ok for me, I don't search the exact problem.
In the url try with the IP address instead of server name