K2 Workflow not automatically started after the modification/add/delete of the Sharepoint List/Library (EventReceiver issue)

  • 23 March 2017
  • 0 replies
  • 6 views

Badge +7


 

Symptoms


When we add an item to a Sharepoint list, the corresponding workflow (setup as "An item was added") not started.
 

Diagnoses


No issue if we start the workflow manually for the same item.

? We made sure that the Event Receiver was registered on the SharePoint list by Executing the ?Get Event Receivers? SmartObject
? We made sure that the correct Endpoint URL matched the WebServices URL
? We made sure the correct Connection Strings where in the SP15EventServiceWeb.config
? We checked the HostServer Log for any errors
? We made sure that the RemoveEventReceiver was accessable from the SharePoint Environment (In our case are public as it's Sharepoint OneLine)
? We made sure that the Endpoint Certificate was valid


We go in MSMQ: Computer management/Service and Application/Message Queuing.
We found that the 'eventbus' and 'eventbus error' was not present.

We follow
https://help.k2.com/onlinehelp/k2blackpearl/icg/4.6.9/webframe.html#msmq.html:
Select Message Queuing Services and sub-nodes Message Queuing Server and Directory Services Integration

We ask to customer to test K2 Blackpearl Client event: It certainly does not work.
? The EventBus Events were certainly not registered in the K2EventBus Table (Not really tested - SELECT * FROM [Eventbus].[CustomEvent] ORDER BY 1 DESC)

As the 'eventbus' and 'eventbus error' are not automatically created Public Queues , and as the customer don't use K2 in Farm mode,
we advise to create manually, connected as K2 Service account ,the 'eventbus' and 'eventbus error' in private Queues:
See "Creating private queues when installing K2 on a non-domain server or Workgroup machine" on https://help.k2.com/onlinehelp/k2blackpearl/icg/4.7/default.htm#prepare/scc/messagequeuing.htm

After this,
? We made sure that the K2Service account had access to the MSMQ

In Event viewer we get:

Event ID 2164 ? Message Queuing Functioning in Domain Mode

Event Details
Product: Windows Operating System
ID: 2164
Source: MSMQ
Version: 6.0
Symbolic Name: EVENT_JOIN_DOMAIN_OBJECT_EXIST
Message: The Message Queuing service will not join the %1 domain. An MSMQ Configuration (msmq) object exists in the new domain with an ID differing from the service ID.

 

Resolution

Found on: https://technet.microsoft.com/en-us/library/cc733521(v=ws.10).aspx

To delete stale computer objects:
1. Click Start, point to Administrative Tools, right-click Active Directory Users and Computers,and then click Run as administrator.
2. On the View menu, ensure that Users, Contacts, Groups and Computers as containers is selected and that Advanced Features is selected.
3. Browse to the particular computer. Check whether there are Message Queuing objects present under that computer.
4. If there are Message Queuing objects and Message Queuing with Active Directory integration is not installed on that particular computer, these objects are stale. Delete the particular Message Queuing Active Directory object, and then restart the MSMQ Service or, if necessary, restart the computer.




 

0 replies

Be the first to reply!

Reply