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.
Users are not receiving their K2 task notification emails. The Email events work. There are no errors in the K2 host server log, MSMQ diagnostic log or Eventbus.ClientRecorderError logged at the time of the task assignment. It is also possible to see that the queue exists and messages gets queued into it.
At the very beginning of the latest K2 host server log, these three error messages can be seen:
"Error","EventBus","7030","Initializing","MSMQ.TestConnectivity","7030 Unable to create 'K2SERVER_NAME\EventBus' queue : 'A connection with Active Directory cannot be established. Verify that there are sufficient permissions to perform this operation.'"
"Error","EventBus","7030","Initializing","MSMQ.TestConnectivity","7030 Unable to create 'K2SERVER_NAME\EventBus Error' queue : 'A connection with Active Directory cannot be established. Verify that there are sufficient permissions to perform this operation.'"
"Error","EventBus","7026","Initializing","EventQueueProcessing.Main","7026 Unable to load EventBus Server"
The error messages mentioned above normally mean that the Message Queuing service was not started (or was not fully started) at the time of the K2 service startup. As the K2 host server service initializes its MSMQ processing thread (EventBus Server) at startup this means that there won't be MSMQ messages processing until you restart the K2 service to ensure correct initialization of the MSMQ thread.
To resolve this issue you need to do the following:
1. Ensure that the Message Queuing service is started on the K2 server (just in case, you may want to restart it and wait for 5 minutes to ensure it is fully initialized.)
2. Restart the K2 service and make sure that:
A) In the beginning of the host server log file there are no error messages similar to those which were mentioned above.
B) Verify that task notifications work.
To prevent this situation from happening in the future you may want to configure the K2 service startup to Automatic (Delayed Start) while keeping Message Queuing configured for Automatic start. Another option will be to configure dependency on MSMQ service for K2 (sc config "K2 blackpearl Server" depend= MSMQ).