I have gotten the following exception a couple of times:
Service 'Translator' 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.
There are a number of things that could potentially cause this exception but the one that has gotten me a couple of times is making sure the name attribute of the service element in the .config contains the fully qualified class name. So for example if I have the following service:
namespace BabelFish.ServiceHost.Web
{
public class Translator : BabelFish.Services.Translator
{
}
}
The service name should be as follows (in bold):
<configuration>
<system.serviceModel>
<services>
<service behaviorConfiguration="TranslatorBehavior" name="BabelFish.ServiceHost.Web.Translator">
<endpoint address="http://localhost/BabelFish.ServiceHost.Web/Translator.svc" binding="wsHttpBinding" name="Translator" contract="BabelFish.Services.Contracts.Service.ITranslator"/>
<endpoint address="mex" binding="mexHttpBinding" name="MetaDataExchange" contract="IMetadataExchange"/>
</service>
</services> ... </system.serviceModel>
...
</configuration>