Code Fix: Unable to deploy a workflow using K2 Package and Deployment when the cached ClaimsToken expires

  • 16 February 2021
  • 0 replies
  • 19 views

Badge +5
 

Code Fix: Unable to deploy a workflow using K2 Package and Deployment when the cached ClaimsToken expires

KB002025

PRODUCT
K2 blackpearl 4.7
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 Description

When deploying a workflow using K2 Package and Deployment and an expired ClaimsToken is still cached in MSBuild an error is logged in the HostServer.log file and the pacakge does not deploy.

 

 

Error Message

Unable to validate the environment field 'Mail Server'. The environment library is not connected.

 

 

Resolution

  1. Ensure you have K2 4.7 installed.
  2. Download and install the K2 4.7 August 2017 Cumulative Update from K2 Partner and Customer Portal.
  3. Get the K2 4.7 August 2017 Cumulative Update FP4 from Regional Support.
  4. Install the K2 4.7 August 2017 Cumulative Update FP4 to apply the fix.

 


0 replies

Be the first to reply!

Reply