LEGACY CONTENT
This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. 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.

Introduction

When a K2Server node (Node1) is stopped in a three node NLB environment, Node2 displays a “could not connect to [Server]” error message for both Node1 and Node3.

Error Scenario Steps

Note: The steps below describe one scenario under which this error may occur. They are simplified and not all steps are shown or described.
  1. Set up a K2Server farm (Node1, Node2 and Node3) with Microsoft NLB
  2. Run the K2Server in console mode
  3. The following happens in the NLB environment:
  • Stopping the K2Service on Node1:
    Node2 will then display a “could not connect to [Server]” error message for Node1 and Node3.
  • Stopping the K2Service on Node2:
    Node1 will then display a “could not connect to [Server]” error message for Node2 and Node3.
  • Stopping the K2Service on Node3:
    Node1 and Node2 runs fine without any warning messages.

Error Messages

The following error message relate to this issue:

A “could not connect to [Server]” error message displays for a Node that is not stopped in an NLB cluster containing more than 2 nodes.

Error Resolution

This Hotfix is contained within the latest K2 blackpearl 0807 Update. Install the update package to resolve the error. 

The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx