Troubleshooting

Application Thumbnail in Access Point: No Preview Available

Check Reduce setting which applies thumbnail picture to the application. Check that the desired image is located at '.._IMG\Thumbnail.png'.

QlikView Application doesn't build

Check line ending conversions settings. During the Git installation, option the Checkout as-is, commit as-is should be selected. This option is reset by the QOps installer by default. Alternatively, it may be set by following git-bash command manually.

$ git config --global core.autocrlf false

System.IO.FileNotFoundException: Could not load file or assembly...

Check that .NET Version used is no lower than required. Following Powershell command may be used for checking this.

(Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name Version, Release -ErrorAction 0 | where { $_.PSChildName -match '^(?!S)\p{L}'} | select PSChildName, Version, Release | Select -ExpandProperty Version | Sort-Object -Descending )[0]

Import-Module: module cannot be imported

Check that Powershell version is no lower than required. Following Powershell command may be used for checking this.

$host.version

Command was found in the module 'QOpsModule'

If after installation you encounter such a problem, you need to allow ps1 scripts to run

For this you can use the following command in PowerShell

Set-ExecutionPolicy Unrestricted

Qlik Sense refuses to create an app: Forbidden [403]

If a build on Qlik Sense needs a new app and the server refuses, for example with Forbidden [403]:Forbidden(Object write failed.), the QOps log file names the app, the server address and virtual proxy, the user the build connected as and the authentication mode. It also records which rights Qlik Sense would give that user on a new app of that name, and which license the user holds (Professional, Analyzer, User access or none).

Check the license first: with user-based licensing only a Professional user can create apps, even when the security rules allow it. Each session also records once which user and address it connects with. Passwords, tokens and certificate contents are never written to the log.

New in version 3.0.21