SmartStarters error when installing package: "The following errors occurred while compiling the process (with framework version 3.5)"

  • 16 February 2021
  • 0 replies
  • 9 views

Userlevel 5
Badge +20
 

SmartStarter error when installing package: "The following errors occurred while compiling the process (with framework version 3.5)"

KBS100078

PRODUCT
K2 blackpearl 4.7
BASED ON
K2 blackpearl 4.7
TAGS
.NET Framework
K2 Studio
SmartStarters
Package and Deploy
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 may face the following error when installing the SmartStarter package:

 

Image

Symptoms

This error occured when installing the 4.7 App Framework package

 

This is the full error message which you may see in the Hostserver log files:

 

"The following errors occurred while compiling the process (with framework version 3.5): Deployment was unsuccessful due to an unknown error. System.Reflection.TargetInvocationException: The following errors occurred while compiling the process (with framework version 3.5):
Deployment was unsuccessful due to an unknown error. ---> System.Exception: The following errors occurred while compiling the process (with framework version 3.5):
Deployment was unsuccessful due to an unknown error."

Resolution

This issue occurred because the K2 Studio component was not installed on the system.

 

Once K2 Studio was installed, we were able to correctly deploy the workflow from the package. 


0 replies

Be the first to reply!

Reply