Issue Description

We have found that the following Microsoft .NET Framework Updates for .NET 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 will cause a licensing issue within KnowledgeLake Imaging and Connect's connection to Capture Server 4 :

.NET Framework updates for Windows Server 2012: KB 4338419
.NET Framework updates for Windows Server 2012 R2: KB 4338418
.NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2 for x64 (KB4340006)
.NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2016 (KB4338814)

If the above options are not the OS you are running the following link will help you find the update for your operating system:

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8202 

The error message you will receive is noted below :

Imaging:

==: An error occurred trying to load the license file à System.TypeInitializationException: The type initializer for ‘Microsoft.Licensing.SLMRuntime’ threw an exception. à System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Capture Server (found in Fiddler logs when making the connection in Connect):

soap:ServerSystem.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.InvalidOperationException: There was an error generating the XML document. ---> System.InvalidOperationException: There is an error in XML document (5, 4). ---> System.TypeInitializationException: The type initializer for 'KnowledgeLake.Capture.Server.Security.Encryptor' threw an exception. ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) at Microsoft.Licensing.SLMRuntime.ExecuteMethod(Object obj, String SVMMethodId, String _assemblyId, Object[] args, Type[] genericTypeParams, Type[] genericMethodParams)

Issue Diagnosis

You can check if these are applied to your server by opening the command prompt and entering :
systeminfo

This command lists all system information and KB's that are applied on your server.

Issue Resolution

Either removing the applicable updates and rebooting your server, or following the instructions in the below article will resolve this issue. This will need to be done on all WFEs. The instructions are copied below:

To resolve this issue, apply the July 30, 2018 update applicable to your operating system and .NET Framework installed:

4346877 Update for Windows 10, version 1607 and Windows Server 2016: July 30, 2018
4346406 Update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 and 4.7.2 on Windows 8.1, RT 8.1 and Server 2012 R2 (KB 4346406): July 30, 2018
4346405 Update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 and 4.7.2 on Windows Server 2012 (KB 4346405): July 30, 2018
4346407 Update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 and 4.7.2 on Windows 7 SP1 and Server 2008 R2 SP1 and .NET Framework 4.6 on Server 2008 SP2 (KB 4346407): July 30, 2018
4346408 Update for .NET Framework 4.5.2 on Windows 8.1, RT 8.1 and Server 2012 R2 (KB 4346408): July 30, 2018
4346739 Update for .NET Framework 4.5.2 on Windows Server 2012 (KB 4346739): July 30, 2018
4346410 Update for .NET Framework 4.5.2 on Windows 7 SP1, Server 2008 R2 SP1 and Server 2008 SP2 (KB 4346410): July 30, 2018
4346745 Update for .NET Framework 3.5 SP1 on Windows 8.1, RT 8.1 and Server 2012 R2 (KB 4346745): July 30, 2018
4346742 Update for .NET Framework 3.5 SP1 on Windows Server 2012 (KB 4346742): July 30, 2018
4346744 Update for .NET Framework 3.5.1 on Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB 4346744): July 30, 2018
4346743 Update for .NET Framework 2.0 SP2 and 3.0 SP2 on Windows Server 2008 SP2 (KB 4346743): July 30, 2018