Hi!

Your config above is using TCP protocol, not UDP. Just to avoid confusion, is the above your current config? If yes, do you have the following config on the other server?

<system.serviceModel>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
    <services>
      <service name="EPiServer.Events.Remote.EventReplication">
        <endpoint name="RemoteEventServiceEndPoint" contract="EPiServer.Events.ServiceModel.IEventReplication" bindingConfiguration="RemoteEventsBinding" address="net.tcp://10.255.11.194:5000/RemoteEventService" binding="netTcpBinding" />
      </service>
    </services>
    <client>
      <endpoint name="10.255.11.195" address="net.tcp://10.255.11.195:5000/RemoteEventService" binding="netTcpBinding" bindingConfiguration="RemoteEventsBinding" contract="EPiServer.Events.ServiceModel.IEventReplication" />
    </client>
    <behaviors>
      <serviceBehaviors>
        <behavior name="DebugServiceBehaviour">
          <serviceDebug includeExceptionDetailInFaults="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <bindings>
      <netTcpBinding>
        <binding name="RemoteEventsBinding" portSharingEnabled="true">
          <security mode="None" />
        </binding>
      </netTcpBinding>
    </bindings>
  </system.serviceModel>

Hi Mattias,

Sorry, I pasted the TCP config by mistake. The curent config we're using is the UDP one. I updated my initial post.

Regards,

Roxana

Hi again,

Do you have multiple installations on the same network (are Test and Production on the same network)? Then you need to make sure you use unique port numbers for each Episerver installation. I would also suggest reading this blog post if you haven't already:

https://www.nimeshjm.com/episerver-remote-events-troubleshooting/

You can also try to use TCP.

Let's assume web server 1 in Test has IP address 192.168.0.100 and web server 2 in Test has IP address 192.168.0.101.

Config for server 1 would look like this if you would use port number 13000:

<system.serviceModel>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
    <services>
      <service name="EPiServer.Events.Remote.EventReplication">
        <endpoint name="RemoteEventServiceEndPoint" contract="EPiServer.Events.ServiceModel.IEventReplication" bindingConfiguration="RemoteEventsBinding" address="net.tcp://192.168.0.100:13000/RemoteEventService" binding="netTcpBinding" />
      </service>
    </services>
    <client>
      <endpoint name="192.168.0.101" address="net.tcp://192.168.0.101:13000/RemoteEventService" binding="netTcpBinding" bindingConfiguration="RemoteEventsBinding" contract="EPiServer.Events.ServiceModel.IEventReplication" />
    </client>
    <behaviors>
      <serviceBehaviors>
        <behavior name="DebugServiceBehaviour">
          <serviceDebug includeExceptionDetailInFaults="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <bindings>
      <netTcpBinding>
        <binding name="RemoteEventsBinding" portSharingEnabled="true">
          <security mode="None" />
        </binding>
      </netTcpBinding>
    </bindings>
  </system.serviceModel>

Config for server 2 would look like this:

<system.serviceModel>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
    <services>
      <service name="EPiServer.Events.Remote.EventReplication">
        <endpoint name="RemoteEventServiceEndPoint" contract="EPiServer.Events.ServiceModel.IEventReplication" bindingConfiguration="RemoteEventsBinding" address="net.tcp://192.168.0.101:13000/RemoteEventService" binding="netTcpBinding" />
      </service>
    </services>
    <client>
      <endpoint name="192.168.0.100" address="net.tcp://192.168.0.100:13000/RemoteEventService" binding="netTcpBinding" bindingConfiguration="RemoteEventsBinding" contract="EPiServer.Events.ServiceModel.IEventReplication" />
    </client>
    <behaviors>
      <serviceBehaviors>
        <behavior name="DebugServiceBehaviour">
          <serviceDebug includeExceptionDetailInFaults="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <bindings>
      <netTcpBinding>
        <binding name="RemoteEventsBinding" portSharingEnabled="true">
          <security mode="None" />
        </binding>
      </netTcpBinding>
    </bindings>
  </system.serviceModel>

No, Test and Production don't have access to each other. Actually, the issue was present before we set the Production environment.

I went through the document, but didn't try to use any of the tools to troubleshoot the issue. I will try and let you know the results.

Hi Mattias,

No, Test and Production don't have access to each other. Actually, the issue was present before we set the Production environment.

I went through the document, but didn't try to use any of the tools to troubleshoot the issue. I will try and let you know the results.

I already tried the TCP config and UDP unicast as well, but no luck. 

The Exception you pasted, I might be wrong but that seems not to be related to event system but rather for websocket updates in UI.

Do you get any other information in the logs regarding event system when you update a page? Does it work in any direction?

What you could do is to verify that service is running on the server on that port with "netstat -a" in commando prompt.

In the windows firewall depending on your profile. Make sure that both inbound and outbound is enabled for UDP packets on port 5000. This is often the case that you have to add it manually.

Also if you have multiple NICs on the server make sure the packets are sent on the correct network. See my blog post:

https://world.episerver.com/blogs/Sebastian-Lundh/Dates/2011/7/Multicast-configuration-with-multiple-NICs/

Update: We fixed the issue by using the TCP configuration. We also added an inbound & outbound rule on each server, to allow TCP packets on port 5000.

We couldn’t make UDP multicast work even with the firewall down.

Thank you for your suggestions, Mattias and Sebastian.

Regards,

Roxana