SOAP requests do not execute with MEX binding

Question

I have a strange problem with some services. I am not a developer, I am a system administrator.

We have some SOAP services running in the development environment. Some SOAP services started to crash. Here is one example. They both come from the same web configuration.

        <endpoint address="http://<URL>/<folder>/service.svc"
                  binding="wsHttpBinding"
                  bindingConfiguration="wsHttpBinding"
                  contract="eConsentSvc.IeConsent"
                  name="WSHttpBinding_IeConsent" />

This is not:

        <endpoint address="http://<URL>/<folder>/service.svc/mex"
                  binding="wsHttpBinding"
                  bindingConfiguration="wsHttpBindingText"
                  contract="MetaDataSvc.IMetaData"
                  name="WSHttpBinding_IMetaData">
        </endpoint>

This second one causes error 404. The generated error:

There was no listening to endpoints at http: ////service.svc/mex that could receive the message.

The obvious difference is "/ mex". The developers insist that it should be there, so it should be there. Why should this have reset the 404 error with MEX?

If I remove / mex, then the service starts and generates the XML document that it needs to create.

Please, help. I am completely at a dead end.

Answer 1

binding="wsHttpBinding" mex*, : mexHttpBinding.
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>

<endpoint address="http://<URL>/<folder>/service.svc/mex"
              binding="wsHttpBinding"
              bindingConfiguration="wsHttpBindingText"
              contract="MetaDataSvc.IMetaData"
              name="WSHttpBinding_IMetaData">
</endpoint>