Destination Rule error: "SmartObject is empty"

  • 15 February 2022
  • 0 replies
  • 206 views

Userlevel 5
Badge +20
 

Destination Rule error: "SmartObject is empty"

kbt171417

PRODUCT
K2 Five 5.0 to 5.2
K2 blackpearl 4.7
BASED ON
K2 blackpearl 4.7
TAGS
K2 Server
K2 Studio
Installation and Configuration
SmartObjects
Administrator
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.

Issue

When you have created a solution that includes a SmartForm to kickflow to initiate a process, you will see that it fails to initiate. When checking to see the status of the workflow via Workspace or K2 Management you will see the following error:

“Smart Object Is Empty”

In some cases you may see this working for other environments as expected, however there may be one environment that has this issue.

Symptoms

Checking in the Hostserver logs or the event viewer the following error may be seen:

“DestinationRule: SmartObject is empty” An unexpected error has occured while trying to resolve a value for Resolver ID 106C5886-18B1-4c09-BEB3-6F7342669D18. InnerException: An unexpected error has occured while trying to resolve a value for Resolver ID 106C5886-18B1-4c09-BEB3-6F7342669D18. InnerException: An unexpected error has occured while trying to resolve a value for Resolver ID 106C5886-18B1-4c09-BEB3-6F7342669D18. InnerException: An unexpected error has occured while trying to resolve a value for Resolver ID 59F5D9BC-3B14-45ca-9C94-6FCB3C4D862F. InnerException: SmartObject is empty.

Hostserver log files can be accessed on the K2 server: 
Program Files x86 > K2 Blackpearl > Hostserver > Bin.

Troubleshooting Steps

You need to verify the following on the K2 Servers:

- Check to see if the environment library hostname for the SmartObject server and SmartForm server is correct. This can be checked via the K2 Management page as below:

- Make sure that the correct string table has the correct name.

If the Hostname appears to be incorrect, update it and then redeploy the process. It should then be working as expected.

 

 


0 replies

Be the first to reply!

Reply