This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
An error appears when starting the K2 Service:
"K2HostServer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFB924DAC4B (00007FFB924D0000) with exit code 80131506. Faulting application name: K2HostServer.exe, version: 0.0.0.0, time stamp: 0x54ef076c Faulting module name: clr.dll, version: 4.7.2563.0, time stamp: 0x5a3356b3 Exception code: 0xc0000005 Fault offset: 0x000000000000ac4b Faulting process id: 0x1654 Faulting application start time: 0x01d398e199805675 Faulting application path: C:\Program Files (x86)\K2 blackpearl\Host Server\Bin\K2HostServer.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: d8c7098f-04d4-11e8-810e-000d3ab4eeb0 Faulting package full name: Faulting package-relative application ID:"
This occurred after a Microsoft Update (May 8, 2018-KB4103723
) which resulted in this error.
- The fix required to address the .NET 4.7.1 compatibility which is included in the K2 4.7 Nov 2017 CU FP9, but this requires the K2 4.7 Nov 2017 CU before it can be installed.
- The K2 November 2017 Cumulative Updates (CU) includes all prior released updates. (Previous CUs and previous Fix Packs.)
- The K2 4.7 Nov 2017 CU Fix Pack 9 (FP9) includes all updates released after the release of the K2 4.7 November CU.
(There is an additional Microsoft Update (May 8, 2018-KB4103723) that caused this error.
Download and install the latest November CU from the K2 Portal site first, then FP9 to resolve this issue.