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.
When trying to retrieve large volumes of SmartObject definitions using the BrokerManagement.exe or modifying SmartObjects from K2 Workspace, timeout errors occur. This is due to the Broker Tool experiencing a time out after approximately 30 seconds and the SQL query requiring a longer period to execute on a large SmartBroker database.
Important: 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. The connection strings previously stored in these files are now retrieved from the K2HostServer.exe.Config file.
- Create a large SmartBroker database. (Requires thousands of SmartObjects to be linked to a single service instance)
- Execute BrokerManagement.exe and record the time it takes to execute the query. (The query will timeout)
Error populating SmartObjects: The timeout expired.
An extra configuration setting has been added to allow the increase of the default SQL command timeout in the Service Broker Store implementation.
To affect the change, navigate to the SourceCode.SmartObjects.Runtime.config file in the following location:
C:\Program Files (x86)\K2 blackpearl\Host Server\Bin
Find the node below and replace or create the value with the required time.
Note: The value is reflected in seconds
<add key="commandtimeout" value="30" />
This Hotfix is contained within the latest K2 Update. Install the update package to resolve the error.