Episerver remote UDP events after upgrading to CMS 11

After upgrading a site from CMS 10 to CMS 11, this error surfaced:

Server Error in ‘/’ Application.


Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The type ‘Microsoft.ServiceModel.Samples.UdpTransportElement, EPiServer.Events’ registered for extension ‘udpTransportCustom’ could not be loaded.

Source Error:

Line 55:   <binding name="RemoteEventsBinding">
Line 56:     <binaryMessageEncoding />
Line 57:       <udpTransportCustom 
multicast="true"/>
Line 58: </binding> Line 59: </customBinding>

Source File: C:\Alloy\web.config    Line: 57


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2633.0

Let’s figure out what’s wrong!

The message complains about the configuration of remote events over upd, that invalidates the cache in a load balanced setup. Once an editor publishes a change on the admin server, the frontend servers are notified and the cache is invalidated. The configuration looked like any other example out there, so what was wrong?

The type UdpTransportElement has moved, so we will have to change:

<extensions>
    <bindingElementExtensions>
        <add name="udpTransportCustom" 
            type="Microsoft.ServiceModel.Samples.UdpTransportElement, 
                EPiServer.Events"/>
    </bindingElementExtensions>
</extensions>

to:

<extensions>
    <bindingElementExtensions>
        <add name="udpTransportCustom" 
             type="Microsoft.ServiceModel.Samples.UdpTransportElement, 
                 EPiServer.Framework.AspNet"/>
    </bindingElementExtensions>
</extensions>

That’s all!

Legg igjen en kommentar

Din e-postadresse vil ikke bli publisert. Obligatoriske felt er merket med *