Errors occurring for Remote events over TCP
ReferencesSetting up Load balancing over TCP for EPiServer installationsA great tool from Paul Smith when throubleshooting Remote events
Listen to the logger "EPiServer.Events"
<level value="debug" />
You should look for
on the backend server sending the event and on the front end server
when receiving the event and
to list all opened endpoints from the server
To examine all send and recived events (with cygwin)
grep 9484e34b-b419-4e59-8fd5-3277668a7fce * | grep ReceiveEvent
grep 9484e34b-b419-4e59-8fd5-3277668a7fce * | grep RaiseEvent
grep "Could not connect to" * | sed -e "s/The connection attempt.*//g" | sort | uniq -c | sort
It takes long time to update remote servers
The remote events are handles synchronously and if one server gets a time out it going to delay every each server. To fix this set a smaller time out value for the binding
<security mode="None" />
The error "Port already in use"
This happens when you trying to open up the same port on the same machine (for example multisite installations where you have to sense all the sites are going to use the same web.config). To solve this enable “port sharing”.
And set the sites application pools ”Disable Overlapped Recycle” to true, sense this will use two different processers for the same shared virtual port.
<binding name="RemoteEventsBinding" portSharingEnabled="true">
TCP error code 10061: No connection could be made because the target machine actively refused it
When getting messages simulate to this in the EPiServer log
The connection attempt lasted for a time span of 00:00:01.0618064. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:13000
You can increase the time out (on this configuration 1 second).
All clients has to be up and running
If not all client can be connected, WCF are going to not deliver packages.