Try our conversational search powered by Generative AI!
AI OnAI Off
EPiServerRemoteEventsListener tool using TCP
Problem solved!
I had the wrong service name after copying the sample code from the articles. I changed the name to the following and it worked:
<system.serviceModel>
<services>
<service
name="EPiServerRemoteEventsListener.RemoteEventListener"
...
So now its working. I have also configured the remote events in EPi to use TCP and it works. So know our "network guys" are happy not using UDP.
So thank you Fredrik Haglund and EPiServer for your articles.
/Hans
Oct 14, 2009 16:26
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
I have read these to articles:
http://blog.fredrikhaglund.se/blog/2009/09/22/episerver-cms-how-to-configure-remote-events-with-many-servers-and-firewalls-between-them/
http://world.episerver.com/FAQ/Items/Multicast-UDP-not-working/
I want to configure the EPiServerRemoteEventsListener tool for TCP instead of UDP. I have tried to configure it by following the two articles but I get an exception when I try to run the tool:
System.InvalidOperationException: Service 'EPiServerRemoteEventsListener.RemoteEventListener' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element.
What do I need to do?
/Hans