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

KB000691 updates all K2 connect version 4.10060.1.0 installations with the latest product hotfixes, as detailed below. The installer will update K2 connect 32-bit and 64-bit installations.

The following issues have been fixed and are contained within this update:

KB000689 - Hotfix: K2 connect for SAP Security Enhancement: SAP SSO Support
KB000688 - Hotfix: ERP Version 4.10.22 Thai Language Support
KB000687 - Hotfix: K2 Designer for Visual Studio: Microsoft Visual Studio 2010 Support

Note: Uninstall ERPConnect Version 3 or Version 4 and then install ERPConnect Version 4.10.22 before installing this K2 connect update

Installation

K2 connect Update (4.10060.1.691) is available as an independent installation package which can be found here: http://portal.k2.com/downloads/k2connect/Default.aspx.

Installation Prerequisites

The following are prerequisites to K2 connect Update (4.10060.1.691) and must be installed prior to installing this update:

  • Full Installation: K2 blackpearl 4.5 (4.10060.1.0) 

Known Issues

The items(s) listed below are issues that have been known to occur and for which there may be workarounds. The circumstances listed below may not be the only instance(s) under which the error occurs and the resolution / workaround noted below is one recommendation that may resolve the issue(s).

SQL Connection Error

Once K2 connect for SAP has been installed, and the user attempts to open the K2 connect Server Configuration UI an error occurs to the effect that the SQL Server Instance cannot be located. For full details on the error see the image below.

Resolution: The error occurs because the connection string does not contain the name of the data source i.e. the SQL Server Instance. To resolve the issue, the user updates the SQL connection string with the identity of the Data Source and thereafter the K2 connect Server Configuration UI will load correctly.

Note: The Administrator or User, as highlighted by the red circle must enter the name of the SQL Server Instance to which the K2 connect Server instance connects. The datasource used in the image above is not literal and is there for illustrative purposes only.