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.

Issue

The K2 service is terminating abruptly and sits in a stuck state in services.

The K2 service stopped at the exact same time every day and required a server restart as a workaround.

Symptoms

After switching both servers to run the K2 service in console mode, this is what happened on the console outputs:

Debug 8039 Receiving 172.16.5.217:1989 Bytes From 8 Debug 8039 Receiving 172.16.5.217:1989 Bytes From 10 Debug 8037 Sending 172.16.5.217:1989 Bytes to 60 Debug 8039 Receiving 172.16.5.217:1989 Bytes From 8 Debug 8039 Receiving 172.16.5.217:1989 Bytes From 3464 Debug 8039 Receiving 172.16.5.217:1989 Bytes From 3472 Debug 8039 Receiving 172.16.5.217:1989 Bytes From 9158 Info 1025 Ending Session 82B4E19D6EEA2A71F72F78000958E34E Debug 8121 Connection to 172.16.5.217:52466 terminated: An existing connection was forcibly closed by the remote host

Resolution

There is one similar case referencing the following article http://help.k2.com/kb001813.

The issue was caused by the K2 Transaction Rollbacks which did not function correctly.

It is recommended that you apply the latest CU for 4.7 to resolve this issue.

Applying February CU for 4.7 and FP1 resolved the issue:

8121 Connection to 172.16.5.217:52466 terminated: An existing connection was forcibly closed by the remote host.