Discussion board where members can learn more about Integration, Extensions and API’s for Qlik Sense.
We are using Qlik Sense 2.01 via Qlik Server and I am having an issue importing extension through the QMC.
All of the extension that I am trying to import to Qlik Sense via Qlik QMC are getting
"Failed to import extensions. Please check the log file."
I went over the following 2 threads
And used their suggestions but still getting the error. Even when I run the ext-check I get no issue with the files.
Checking file "c:\bi-listbox_v2.zip" ...
5 files in 0 directories
0 files might be not accepted by Qlik Sense server.
Everything looks fine, go ahead.
The error comes up with any file size, (even the simplest file as above.)
C:\Users\smusaye>ext-check "c:\bi-listbox_v2.zip" -l
Usage of different file extensions in "c:\bi-listbox_v2.zip":
js 2 times used ( OK )
css 2 times used ( OK )
qext 1 times used ( OK )
Everything looks fine!
Please help if you have any suggestion.
Go to Solution.
It can be, I have too little knowledge in MS windows servers.
Some google results:
- Report Manager: “System.InvalidOperationException: This implementation is not part of the Windows Pl...- https://support.microsoft.com/en-us/kb/935434
Anyway, this doesn't look like Qlik Sense related issue - you should contact your system administrator.
I hope this helps,
could you please share the extension with me (just send it to swr (at) qlik (dot) com if you don't want to post here ...) ...
I'd like to investigate.
Did you have a look at the log-files, what can you find there?
Attached is a extension in question but the truth is that I wasn't able to get any extensions to import.
Any extension, so you always get the same error?
Also unable to locate the log file.
Hi Stefan, any advice that may help us importing extensions?
You can find the log files here: C:\ProgramData\Qlik\Sense\Log\Repository\Audit\
Uploading the extension seems to work on my system, maybe the logs will help us find the real issue.
Could this be the issue, found it in the log file you told me to look into.
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. (HTTP code: 500)
If yes, any solutions.