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.
K2 blackpearl 4.6.8 (4.12060.1600.0) allows for a clean install or upgrade from a previous version of the product. The 4.6.8 release builds on top of the K2 4.6.7 release and contains bug fixes and enhancements as listed in KB001599 – K2 blackpearl 4.6.8 Resolved Issues List.
The K2 blackpearl 4.6.8 Setup Manager is available as an independent installation package that can be downloaded from K2 Partner and Customer Portal.
The Knowledge Base articles below list the issues resolved in this release:
The Knowledge Base article KB001598 lists the known issues in this release.
This update includes hotfixes included in previous K2 4.6 Updates, so there is no need to install the updates listed below. The following links are provided for reference to view the enhancements and resolved issues contained within the previous updates: KB001590 – Update K2 4.6.7 (4.12060.1590.0) KB001560 – Update K2 4.6.6 (4.12060.1560.0) KB001550 – Update K2 4.6.5 (4.12060.1550.0) KB001540 - Update K2 4.6.4 (4.12060.1540.0) KB001530 - Update K2 4.6.3 (4.12060.1530.0) KB001520 - Update K2 4.6.2 (4.12060.1520.0) KB001500 - Update K2 4.6.1 (4.12060.1500.0)
- Claims and Kerberos– If your environment is using impersonation and Kerberos, manual configuration is required when upgrading or setting up your environment. For more information see KB001607 – Delegation Settings to Allow Impersonation with Kerberos.
- The K2 Server (Host Server) has a dependency on .NET Framework 4.5 as a result of the change in the way claims functions. Ensure that you have .NET 4.5 installed on the server before upgrading to K2 4.6.8.
- K2 Package and Deployment has been included in the K2 blackpearl installer and is no longer a separate installation.
- Claims – The claims configuration has been moved from the K2HostServerweb.config file to the K2 database. For clean installations the K2 Setup Manager will configure your environment to run with claims and will enter the required configuration settings in the new database tables. For upgrades the claims configuration will remain in the web config file and will also be migrated to the new database. See the K2 blackpearl Installation and Configuration Guide for more information.
- HTTPS/HTTP - During the installation of K2 4.6.7 and K2 4.6.8 all K2 sites will be certified and configured to run as HTTPS or as HTTP. The K2 Workspace site can run as previously configured (HTTP) or it can run as a certified site (HTTPS). When using the K2 installation to create your sites, both HTTP and HTTPS will be setup and created with certificates generated by K2. Upgrades will use previously configured bindings, with the user having the ability to choose which bindings must be configured for K2.
- Behavioral change: Changes have been made in the SmartObject Service Broker that will affect all services that return a decimal or float as a result. Previously, all decimals were converted to a float, but this caused precision issues. The issue applies particularly to the SQL Server Service which is a native integrated service that returns decimal or float values (table, view or stored procedures), but may affect other Service Instance types (non SQL, like WCF endpoint broker) that also return a decimal or float in the result. The decimal value is now the correct type providing the required accuracy. The resulting datatable’s value type has been changed from a float to a decimal. When comparing strings, an error could occur or the result was incorrect, for example 0.1 (Decimal type) is equal to 0.100000 (Decimal type), but 0.1 (String type) is not equal to 0.100000 (String type). If decimals in SmartObjects are treated as strings in your current environment, for example when a compare inline function or custom APIs that use the SmartObject API to check for a returned value has been used, on upgrading you need to check that the returned value still matches.
- Behavioral change: The LDAP path entry LDAPPath=LDAP://DC=[PARENTDOMAIN],DC=[PARENTDC]; is no longer required in the RoleInit role provider section of the security label in Host server. It is only required in the DataSource path of the RoleInit. When upgrading the entry will persist but will be ignored by the system. Any new security label configurations do not require the entry and should resemble the following:
DataSource Path="LDAP://DC=DOMAIN,DC=COM" NetBiosName="DENALLIX"/>
NetBiosName="DENALLIX" UserName="Domain\Name" Password="xxx"/></
A user name and password can now be added to the RoleInit in the SecurityLabels table in the HostServer database which will allow access to a read-only domain. Note that a Host and a Port can be added to the DataSource Path if necessary and can be the FQN or an IP address.
||Note: This configuration is NOT for connecting to Active Directory as a specific user.
NetBiosName="DENALLIX"/><DataSource Path="LDAP://domain.com/DC=DOMAIN,DC=COM" NetBiosName=
"DENALLIX" UserName="Domain\Name" Password="XXX"/></
- There is one installer that will facilitate the following:
- For customers who already have K2 blackpearl 4.6 installed, download and install this update from portal.k2.com.
- For customers who do not have K2 blackpearl installed, download the installer from portal.k2.com.
- Upgrades: The following versions of K2 can be upgraded to K2 4.6.8:
- K2 blackpearl 4.5 (4.10060.1.x)
- K2 blackpearl 4.6 (4.12060.x.x)
- K2 blackpoint 4.6.4 (4.12060.1540.0)
Note: If your environment is using impersonation and Kerberos manual configuration is required when upgrading or setting up your environment. For more information see KB001607 – Delegation Settings to Allow Impersonation with Kerberos
- If you are currently on Windows Server 2008 R2 you will require Windows Server 2008 R2 Service Pack 1 when upgrading.
- The K2 Server (Host Server) requires .NET Framework 4.5. Ensure that you have .NET 4.5 installed on the server before upgrading to or installing.
- Refer to the K2 4.6.8 documentation available in the installation package or on Help.K2.com for detailed installation instructions.
- The K2 4.6.8 installation package must be installed by running the K2 Setup Manager (K2Setup.exe) found within the package.
- Ensure that you have the correct permissions to run the install to avoid installation issues. For the correct installation permissions refer to the installation and configuration guide.
- After the K2 Setup Manager finishes, if SharePoint 2010 is present (or there are SharePoint 2010-compatible site collections in SharePoint 2013) in the environment the K2 for SharePoint Configuration wizard will run and must be allowed to complete to fully update the K2 Features in SharePoint with any changes. If the K2 for SharePoint Configuration wizard is not run, the update will not be installed properly and your K2 installation will not function correctly.
Note: The K2 for SharePoint Configuration wizard does not need to be run if you are installing in a SharePoint 2013 environment.