Skip to main content
Nintex Community Menu Bar

Upgrade to K2 Five detects legacy component that does not exist

  • February 16, 2021
  • 0 replies
  • 9 views
  • Translate

MillaZ
Nintex Employee
Forum|alt.badge.img+21
  • Nintex Employee
  • 671 replies
 

Upgrade to K2 Five detects legacy component that does not exist

kbt166895

PRODUCT
K2 blackpearl 4.6.10 to 4.7
K2 4.7 March 2018 Cumulative Update
BASED ON
K2 blackpearl 4.7
TAGS
Installation
Upgrading
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

You are unable to remove the legacy component when using K2 setup manager.

Symptoms

When trying to upgrade, the installer blocks you from upgrading until the unsupported component is removed.

Trying to remove the component via the installer fails.

Trying to remove the component via windows program and features is also unsuccessful.

Resolution

To resolve this, please log a ticket a support with K2.

Support can provide a tool that removes the missing component from registry.

This will allow the setupupgrade to complete successfully.

Did this topic help you find an answer to your question?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings