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

You are unable to select "Use existing service instance" while performing package deployment using the Package and Deployment utility. The required existing instance can be selected in a pop up window, but its' properties appear not being read and it looks like nothing was selected after you clicked on it.

Symptoms

Unable to select "Use existing service instance" while performing package deployment using Package and Deployment utility. Required existing instance can be selected in pop up window but its properties not being read and it looks like nothing was selected after you clicked on it.

This issue may appear after custom broker assembly was updated while service instance itself was not updated. After assembly update (file replacement) when it contains new or modified service instance settings it may be necessary to update service instance by means of right clicking on it in Tester Tool and selecting "Edit Service Instance" and completing this dialog (Next/OK etc.). To verify that all setting were updated you may extract instance definition XML from SmartBroker.ServiceInstance table in K2 database and compare them between source and destination environments. Symptoms described above may be caused by the fact that some instance property is blank in destination environment and edit/update of the service instance will correct this.

Resolution

The issue can be resolved by editing or updating the service instance so that the new property name is picked up and added into the service instance XML definition.