Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Knowledge
Dashboard extensions do not install from the Feb 2019 build
Article Number: 000068118 | Last Modified: 2019/03/21Description
Dashboard extensions will not install from the installer for Qlik Sense Feb 2019. The Extension bundles are selected for install During installation process. When the installation is complete they will not appear when creating a new sheet in the HUB. Extension Bundles will still appear in the C:\Program Files\Qlik\Sense\ExtensionBundles default location and in the Programs and Features Section of the Control Panel.
Analysis of the Sense System Repository logs will produce an error similar to:
178 20190304T133036.038-0500 ERROR RM-PRD-BI System.Repository.Repository.Core.Resource.LogArchivingResource 26 928e829f-3cd4-4b14-a626-1e1c08da5af3 DOMAIN\username Error when rolling log files for 'script' (995b2624-c020-44b3-9490-80560da1cdc9.2019_03_04_18_30_32.8A171B7BCE10E09437B3.log) This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.↵↓Exception has been thrown by the target of an invocation. at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()↵↓ at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)↵↓ at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)↵↓ at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)↵↓ at System.Security.Cryptography.MD5.Create()↵↓ at Repository.Core.Hashing.Hasher.ComputeHashInternal(Func`2 func)↵↓ at Repository.Core.IO.StreamValidator.ComputeHash(String path)↵↓ at Repository.Synchronization.Logs.LogEntityManagerWorker.ConvertToFileReference(String filePath)↵↓ at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()↵↓ at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)↵↓ at Repository.Synchronization.Logs.LogEntityManagerWorker.CopyToArchiveRepository(String[] newRolledLogFiles)↵↓ at Repository.Core.Resource.LogArchivingResource.ArchiveLogFiles(String logrootsubfolder, IEnumerable`1 files) 928e829f-3cd4-4b14-a626-1e1c08da5af3
Environment:
Analysis of the Sense System Repository logs will produce an error similar to:
178 20190304T133036.038-0500 ERROR RM-PRD-BI System.Repository.Repository.Core.Resource.LogArchivingResource 26 928e829f-3cd4-4b14-a626-1e1c08da5af3 DOMAIN\username Error when rolling log files for 'script' (995b2624-c020-44b3-9490-80560da1cdc9.2019_03_04_18_30_32.8A171B7BCE10E09437B3.log) This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.↵↓Exception has been thrown by the target of an invocation. at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()↵↓ at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)↵↓ at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)↵↓ at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)↵↓ at System.Security.Cryptography.MD5.Create()↵↓ at Repository.Core.Hashing.Hasher.ComputeHashInternal(Func`2 func)↵↓ at Repository.Core.IO.StreamValidator.ComputeHash(String path)↵↓ at Repository.Synchronization.Logs.LogEntityManagerWorker.ConvertToFileReference(String filePath)↵↓ at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()↵↓ at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)↵↓ at Repository.Synchronization.Logs.LogEntityManagerWorker.CopyToArchiveRepository(String[] newRolledLogFiles)↵↓ at Repository.Core.Resource.LogArchivingResource.ArchiveLogFiles(String logrootsubfolder, IEnumerable`1 files) 928e829f-3cd4-4b14-a626-1e1c08da5af3
Environment:
- Qlik Sense February 2019 (13.9.1)
Cause
Qlik Sense is not FIPS compliant.
Resolution
FIPS is enabled on the Server. Disable FIPS in Local Policy Security Setting.
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us