Worklist Service Broker

  • 12 November 2009
  • 34 replies

Show first post

34 replies

Thanks Tin!  I changed it to false but still not working yet.


I implemented this broker and noticed that the Impersonate connection string may need to include the domain in the 'UserID' parameter, I.e.:




I assume when calling the methods, the user that the k2 service account should be impersonating is also specified in the 'User Name' input property?  And that this username is also correct/owns worklist item?


Because it looks like you can specify any string in this 'User Name' input properties and it will not throw error even if the string is incorrect.

Userlevel 6
Badge +15

I ran a quick test, it should work.


Authentication Mode: Impersonate.

Below is my connections Strings:




Thanks Tin and Khanh!  Here is what I have now but still not working. :(






Hi guys,

Any other ideas why I have the same connection string but still not giving me anything back?  K2 SQL permission? K2 Workspace permission?



Did you come right with this yet?  What you could consider doing is creating a little console application for the pursposes of testing.  Add references to SourceCode.HostClientAPI and SourceCode.Workflow.Client. Try opening a connection to the K2 server using your connection string (Connection.Open()).  I've done so with your connection string which works.   If the issue persist then please call support.  While components on community are generally unsupported your console application would be supported.  

Hi All,


Is this K2 Cloud ready or rather can it be used in K2 Cloud ?


Thanks and Regards,




K2 Cloud does not support addition of custom brokers as per:




Badge +3



I'm using v0.5. I think this is the latest one.

I'm facing weird issue. It works fine on Dev environment. (single server).


On production env. (WFE + APP), I installed on app server. Service Acc has impersonation rights & given that in connection strings as suggested by