Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The QlikView Management Console performance is very poor/slow, or otherwise unstable and eventually unreachable. Access to the QlikView server node configuration tabs and AccessPoint is very slow or doesn't show any documents.
The Windows Event log might show multiple entries of error: “The communication with QlikView Server failed (TimedOut)!”
After a restart of the server, the Management Console (QMC) is temporary available. But after time it becomes unreliable again.
Also see:
QlikView , all versions
If the QlikView Server is required to scan too many directories and files, the QVS.exe will utilize too many of its resources on scanning the files, therefore slowing down itself and the Management Console as well.
It is important to know that when you mount a folder, all sub-folders also gets scanned.
One possible root cause for this is a large number of folders and files included in the mounted Qlik Documents folders. These files and directories may not even have QlikView documents (.qvw) included in them.
If the QlikView Server is required to scan too many directories and files, the QVS.exe will utilize too many of its resources on scanning the files, therefore slowing down itself and the Management Console as well.
It is important to know that when you mount a folder, all sub-folders also gets scanned.
To check if this is the issue, verify that the QlikView Server log verbosity is set to High. See Recommended Log files to analyze QlikView problem for details on how to change the logging level.
Open the QlikView Server event log. (Default location is C:\ProgramData\QlikTech\QlikViewServer)
Check for the entries that looks like the one below. There will be one for each folder that the QlikView Server will scan through. This will be done every 10 minutes by default.
Make sure that only folders that contain QlikView relevant documents (.qvw, .shared. meta) are included in the mount list or the subfolders.