While investigating problems related to a Service Broker, our team wanted to isolate a single K2 server of a farm to perform some troubleshooting. Our intention was to temporarily disable workflow execution while still allowing access to SmartObject execution. But how?
Technically, you won’t find the answer in Program Files (x86)\K2 blackpearl\Host Server\Bin\Hosted Servers.
KO.dll is responsible for workflow execution. If that library file is moved out of Program Files (x86)\K2 blackpearl\Host Server\Bin\Hosted Servers — that’s moved, not just renamed, mind you — and the K2 Server Service is restarted, you will effectively disable workflow execution on the server while retaining its other capabilities. Consider moving the DLL to a backup location, from which it may be easily restored.
Hope you find this tip effective and if you have any other K2 related technical questions please contact me at tfarrelldiscovertechnologies.com