K2 Service stalls when upgrading 4.6.11 to 4.7
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.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. 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.
Issue
When attempting to upgrade from 4.6.11 to 4.7 you may experience the following issue.
The upgrade fails with the K2 service going into a "starting state" and in turns this fails the upgrade scripts from completing in the installation.
Symptoms
When you terminate the K2hostserver service "starting state" and start the K2 service in console mode you will see the following behavior.
When you connect to the K2 SQL Database, do a select statement on table HostServer.LicensedUser.table.
If you notice over a 1000 licensed user rows, the steps provided below should resolve this issue.
Resolution
To resolve this issue complete the following steps:
- Connect the K2 SQL Database
- Truncate the HostServer.LicensedUser.table
- Then start the upgrade from 4.6.11 to 4.7 again
- The K2 service will behave as expected.
Please note that this is direct DB modification and without approval of K2 support will place your environment in an unsupported state.