Known Issue: How to resolve an object type conversion error

  • 24 February 2022
  • 0 replies
  • 8 views

Userlevel 3
Badge +8
 

Known Issue: How to resolve an object type conversion error

KB001413

PRODUCT
K2 blackpearl 4.6.5
BASED ON
K2 blackpearl 4.6.5
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.

 

This article highlights a known issue where refreshing an Endpoints Web Service or Endpoints WCF Service Broker service instance can result in a duplicate proxy assembly being loaded into host server memory. This issue may be experienced as a "Object of type '[SomeObject]' cannot be converted to type '[SomeObject]'" error when executing a SmartObject method that uses the refreshed service instance.

 

 

Issue:

There is a known issue where refreshing an Endpoints Web Service or Endpoints WCF Service Broker service instance can result in a duplicate proxy assembly being loaded into host server memory.  The result of this is that at runtime SmartObject methods that take serialized complex objects as inputs may not be able to deserialize the objects correctly resulting in a "Object of type '[SomeObject]' cannot be converted to type '[SomeObject]'" error.

 Image

Workaround:

Until this issue is addressed in a future product release, the workaround is to restart the K2 blackpearl service after refreshing Endpoints Web Service or Endpoints WCF Service Broker service instances. This will ensure that only one instance of the proxy assembly exists at a time.

 


0 replies

Be the first to reply!

Reply