Symptoms
Client event notifications were not being sent.
Diagnoses
n/a
Resolution
The first step was the creation of a simple test process that just contained a single client event to preclude having to run through a full fledged process.
We executed the process and then checked the EventBus.ClientRecorderError table and found this:
CustomEventID: 46 CustomEventLogID: 1714
System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation.
at System.Messaging.MessageQueue.MQCacheableInfo.get_WriteHandle()
at System.Messaging.MessageQueue.StaleSafeSendMessage(MQPROPS properties, ITransaction transaction)
at System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType)
at SourceCode.EventBus.ClientRecorder.MSMQDestination.AddEventToQueue(ResolvedCustomEvent resolvedCustomEvent)
at SourceCode.EventBus.ClientRecorder.Event.QueueEvent(ResolvedCustomEvent resolvedCustomEvent)
at SourceCode.EventBus.ClientRecorder.Event.RaiseEvent(Object context, String providerID, String eventName, String data)
This happens for one of two reasons:
1) MSMQ was not installed with the directory services integration. If that was intentional you will need to establish private message queues (http://help.k2.com/kb000198_)
2) This can also happen if the server has lost communication with the domain control at install in which case it will default to a workgroup installation. If that is the case, reestablish communication with the domain controller and reinstall MSMQ
After the workgroup business was sorted their were still no Client Notification being seen despite there being no errors in workspace. A check of the host server logs revealed that the connection string could not be resolved as it was null. Using the connectionstringeditor.exe it seen that although the appropriate strings existed, there was in fact a single connectionstring that was null so it was removed.
Still, no notifications were getting sent but at least we had another new error:
"15061709","2016-01-25 10:24:53","Error","MessageBus","61007","SendMessageException","MessageBusRuntime","61007 Permanent failure sending message New Task: System.Exception: No destinations could send the message New Task.
at SourceCode.MessageBus.Server.MessageBusRuntime.SourceCode.MessageBus.IMessageDestination.Send(String title, MessageExtendedInformation extended, IEnumerable`1 attachments, MessageBodyReaderd] messageBodies)","","","hgp006:C:Program Files (x86)K2 blackpearlHost ServerBin","15061709","7503ec9d68f545d482d0d4a9c9f72096",
The problem here was two fold:
1) The from address from our environment library was an old email address that was now longer in use.
2) One of our destination users was the smartactions account and K2 does not allow that to send itself emails.
