The QlikView AccessPoint is blank.
The QlikView Accespoint is empty, no documents are loading.
The QlikView AccessPoint is greyed out, doesn't load, or is stuck in a "loading content" loop.
In 12.xx versions you may notice a different behavior:
- Are all prerequisites installed on the server (.NET Framework 4.0 for Qlikview 11+) and if IIS is in use, have all pertinent role features been added? See How to configure: QlikView and IIS for details regarding IIS installation.
- Ensure the Service Account running the Directory Service connector has the proper permissions to resolve usernames. This may be an authentication related issue. One way to check this is to view the Windows Logs (Event/Security) to see if the Service Account is failing audit or generating other authentication/permission-related messages.
- If the Service Account does not have access to Active Directory, ensure a proper login account is configured in the Directory Service Connector settings in the Management Console.
- If the Directory Service Connector is installed on a different server, ensure TCP port 4730 is not blocked inbound or outbound.
- Check location of domain controller(s) in relation to servers, if not local to the servers, even with low latent network connections, this may still pose issues when the environment is fairly busy with users coming into the AccessPoint.
- The host name of the server address may not include an underscore (Internet Explorer (IE) in particular), as no cookies can be set, which may cause the authentication process to fail:
- Enhanced Security settings for IE should be turned off for Administrators.
- Does the QlikView Server have full control on the ProgramData\QlikTech folder?
c:\programdata\qliktech\qlikview server as well as the mounts configured for the QlikView Server resource in the Management console should allow Full Control rights.
- Are there a large number of folder mounts, or do the folder mounts contain a high number of none-QlikView related files? Note: the QVS scans the folder mount content regularly, which may lead to delays or timeouts.
- Ensure the Qlikview Webserver machine connection is using the QlikView Server host name and not
Localhost, in QlikView Management Console check the following:
System > Setup > QlikviewWebserver > Accesspoint > Server > Connections
General (client side)
- Add the QlikView AccessPoint site to the Local Intranet security zone or trusted sites in IE.
- Have cookies been allowed in the browser for the currently logged on user?
- The account running the Application Pool is the same account as the one running the QlikView Services,
or is in the QlikView Administrators and Local Administrators Security Groups. Note: Ensure that the /QvAjaxZfc and /WebTicketSite websites are using the "QlikView IIS" Application Pool and not the DefaultAppPool.
- Incorrect .NET Trust levels. See Index.htm not fully loaded.
- If Windows Authentication is being used, ensure it is installed/enabled. To do so, review the enabled features in the IIS Roles configuration. See below:
Click Add Roles and check Web Server (IIS). Click Add Required Features and Click Next.
On the page Select Role Services ensure the following is checked: > Security > Windows Authentication
If the issue persists, proceed as follows:
Test one of the QlikView .aspx pages by browsing to, (for example), http://server/QvAjaxZfc/QvClient.aspx.
Is an error similar to the following returned:
HTTP Error 500.21 - Internal Server Error
Handler "WebServiceHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in
its module list.
- Run the following command to register ASP.NET v.4 in IIS:
- %windir%\Microsoft.NET\Framework64\v4.0xxxx\aspnet_regiis.exe -i (Windows 2008)
- dism /online /enable-feature /featurename:IIS-ASPNET45 /all (Windows 2012)
- Ensure ASP.NET feature is activated in IIS role
- Verify the application pool in IIS used by QlikView, "QlikView IIS", is using the .NET Framework v4.0
Should none of these steps help, please contact QlikView Support for further assistance.