KB000510

SEE ALSO K2.net 2003 Hotfix Downloads Page

Introduction

This hotfix addresses several issues that may occur when using K2.net 2003 SP4. These include: memory usage, a Remoting object timeout exception, an OpenProcessInstance API call error, a Socket connection TIME_WAIT state, lost Escalations and an Error Repairing problem.

Error Scenario

Note: The circumstances described in this article are one scenario under which this issue may, or is known to occur. The description is intended to be specific to the scenario described and does not take into account all possible scenarios or circumstances.

This hotfix addresses the following issues:

Issue 1: Memory Usage

The K2 server currently executes processes using application domains. Prior to this hotfix, the application domains were not unloaded from the memory and thus resulted in a high memory usage of K2 server. With this hotfix, the memory will still climb with server usage, but will also drop to previous levels if/when resources are running low.

Issue 2: Timeout on Remoting Objects

When executing long running server events within K2 server, the timeout for the object’s lifetime within the AppDomain were by default set to 5 minutes. Having an event execute for longer than 5 minutes, resulted in the exception shown below:

[System.Runtime.Remoting.RemotingException: Object '{SmartObject}' has been disconnected or does not exist at the server.].

This fix adjusts the lifetime of the remoting objects to be infinite.

Issue 3: OpenProcessInstances API call

In certain circumstances, an error occurred when calling the OpenProcessInstance method through the K2ROM API.

Issue 4: Evaluation Licenses

Evaluation Licenses defined to expire after 31 December 2009 has been resolved.

Issue 5: Socket connection State enhancements

The socket connections close properly after this hotfix is applied and no longer enters the TIME_WAIT state.

Issue 6: Escalation

On an Escalation which is configured to repeat multiple times, the escalations are lost when the active process instance is stopped and started again as the Escalations entries gets deleted.

Issue 7: Error Repairing

In certain circumstances prior to this hotfix, duplicate Process definition assemblies were created in the Work folder when Errors were repaired.

Error Resolution

This Hotfix is contained within Hotfix 9 for K2.net 2003 SP4. Install the Hotfix to resolve the error by following the installation steps below:

1. Stop the K2Server Service(s)
2. Make backups of the existing files in your environment (only the files which will be replaced by this hotfix) from the [install directory]Bin folder – by copying them to a different location.
3. Replace the existing files with the files contained within the downloaded archive.
4. If any custom applications are used (and for Workspace), the K2ROM of these applications will also need to be backed up and replaced.
5. If the K2 Service Manager is installed on separate machines, the K2Mng, K2CSC and ADUM dlls on these machines will also have to be backed up and replaced.
6. Start the K2Server Service(s) again.

The hotfix is available at: http://portal.k2.com/downloads/sets/hotfixes.aspx?pid=2