Refreshing or updating service instance results in a timeout


Refreshing or updating service instance results in a timeout

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.
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.


Refreshing or updating an existing service instance from the SmartObject Service Tester tool results in a timeout.

"SmartObject Server Exception: Timeout Expired"


The error is not specific to a service type as any existing instance would result in the same error.

Troubleshooting Steps



With the release of K2 4.6.9 the SourceCode.SmartObjects.Runtime.config has been consolidated into a single configuration file called K2HostServer.exe.Config file, which is located in the ...\K2 blackpearl\Host Server\Bin folder on the K2 Server.

Increase the commandtimeout value or add this key under <appSettings> 

If not found, in SourceCode.SmartObjects.Runtime.config located in the following directories:

  1. ...\K2 blackpearl\Host Server\Bin
  2. ...\K2 blackpearl\Service Broker

    <add key="commandtimeout" value="900" />


Labels: (1)
Version history
Revision #:
2 of 2
Last update:
4 weeks ago
Updated by: