QlikView has been upgraded. After the upgrade, the AccessPoint does not load or is stuck in Loading Content
A possible root cause is the .json Mime Type not being recognized as a valid extension name. This is most often an issue with Microsoft IIS used as a Web Server, but could also occur in the QlikView Web Server.
Resolution
The .json Mime Type is missing as a valid file name extension in IIS.
-
Open the IIS Management Console
-
Select Website
-
Double Click Mime Type Icon Under IIs
-
Click Add Link in right hand side
-
File Name Extension = .json Mime Type = application/json
-
Click Ok.
- Restart IIS from IIS manager console
The .json Mime Type is missing as a valid file name extension in the QlikView Web Server.
- Go to the QlikView Management Console
- Open System
- Open the Setup tab
- Open your QlikView Web Server
- Switch to the Web tab
- Review if the JSON extension is listed. If not, add it as:
Extension: .JSON
Content: application/json

- Click Apply
Environment
QlikView any version
Microsoft IIS
Related Content:
QlikView Access Point not loading, shows a blank or greyed out screen showing "Loading Content"
The Loading Content message indicates a generic error message that can be caused by authentication failures, loading delays, and permission issues, as well as lacking prerequisites. This article outlines the most common causes and possible solutions.