Verrouillé AppFabric production Problem

  • Wednesday, April 04, 2012 6:46 AM
     
     

    in our production server we get repeatedly below errors.

    1 - WMS was not able to activate any of the hosts - backing off. Store name 'defaultSqlPersistenceStore' ('Root).

    2 - Failed to invoke service management endpoint at 'net.pipe://servername//ServiceManagement.svc' to activate service '/Retail/LoanDomain/Application/Web/Loan.xamlx'.\rException: 'The message with To 'net.pipe://servername//ServiceManagement.svc' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher.  Check that the sender and receiver's EndpointAddresses agree.'

    We are using AppFabric on Win2008R2, and persistence and monitoring is enable. And also, recycling is disabled on app poll.


    • Edited by Ugur KARATAS Wednesday, April 04, 2012 6:48 AM
    •  

All Replies

  • Tuesday, April 10, 2012 1:52 PM
     
     

    Has this issue started to manifest itself after some time or after a deployment?

    Please make sure the machine is not missing any service packs or updates.


    Arthur My Blog

  • Tuesday, April 17, 2012 7:28 AM
     
     

    AppFabric Workflow Management Service requires that the "net.pipe" binding is enabled for the Site and Application containging the service, see

    http://msdn.microsoft.com/en-us/library/ff383422.aspx (Not "important" at start of the article).

    In IIS Management console check "Enabled Protocols" in Advanced Properties of the Site as well as the application.
    It should at least state Enbabled Protocols "http, net.pipe". Append ", net.pipe" if not present.

    Nico

  • Thursday, August 16, 2012 3:26 PM
     
     

    I'm experiencing the same problem. 

    I've checked that net.pipe protocol is enabled and net.pipe binding is configured as well.

    I know that this post is quite old but did you find what the problem was?

    Reading the documentation in msdn:

    "The Service Management Service supports only the net.pipe protocol for bindings. The address of a Service Management Service added to an application conforms to the following address pattern: {scheme}://hostname:port/<application>/ServiceManagement.svc. For example: net.pipe://localhost/VirtualApplicationB/ServiceManagement.svc."

    In the exception message the address pattern is not followed, in your case I reckon it should be:

    net.pipe//servername/Retail/ServiceManagement.svc (assuming that your application is called "Retail").

    So the question now is... Why is not following the specified pattern?