Symptoms
Sharepoint 2013 Item Added event not triggering, manually starting the workflow does execute successfully.
_1
Enabling verbose ULS logging uncovered the following error:
Calling remote event receiver failed. URL = https://k2.denallix.com/SP15EventService/RemoteEventService.svc], App Identifier = , Event Type = ItemAdded], Exception = An error occurred while making the HTTP request to https://k2.denallix.com/SP15EventService/RemoteEventService.svc. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.]
_2
With the new cert, we are now seeing a timeout error:
Calling the remote event receiver url https://k2.contactd.aig.net/SP15EventService/RemoteEventService.svc. i:0i.t|ms.sp.ext|3308eaff-d056-4a32-9b1d-563f81bf06f9@7b060970-5429-4a63-b089-c2e615ca5a5e. The request channel timed out while waiting for a reply after 00:00:30:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
Diagnoses
_1
A Wildcard cert (*.denallix.com) was being used. Perhaps an additional HTTP.SYS configuration is necessary using the 'netsh' command, similar to the post below:
http://stackoverflow.com/questions/21281302/wcf-with-transport-security-via-certificates
_2
This was due to usage of a proxy.
Resolution
_1
A non-wildcard cert was requested for the K2 sites and this resolved the original error.
_2
Disabling the proxy server under eInternet Options > Connections > LAN settings] > by un-checking the 'Automatically detect settings' and 'Use automatic configuration script' option on both the K2 Server and Sharepoint server resolved this timeout issue and the Item Added event was working correctly. We also noticed that the proxy setting will get reintroduced after a certain period of time, I believe this is usually due to a Group Policy setting. As such, perhaps disabling the Group Policy that would put this proxy in place for these two servers or working with the Network team to determine why the timeout issue occurs when a proxy is in place as it is preventing the successful communication between the K2 server and Sharepoint server.
