Service has zero application non-infrastructure endpoints

Question

I recently created a WCF service  dll  and a service host  exe   I know my WCF service is working correctly since I am able to successfully add the service to WcfTestClient    However  I seem to be running into an issue when I comes to utlizing my WCF from a service host  exe   I can add a reference to the WCF  dll  to my service host  exe  and create the necessary componets to the exe  such as the service installer  service host  and the app config  compile and then finally install the exe using InstallUtil  But  when I tried to start the service in the Microsoft Management Console  the service immediately stops after being started    So I began investigating what could exactly be causing this issue an came up with this error from the Application Log in the Event Viewer    Description       Service cannot be started    System InvalidOperationException    Service  Service  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    This error is actually generated in the OnStart  of my exe  when I perform this call ServiceHost Open    I ve seen numerous posts where other individuals have run into this issue  however most if not all of them  claim that the service name or contract  namespace and class name  are not being specified  I checked both of these entries in my config file  in the exe as well as in the dll  and they match up PERFECTLY  I ve had other people in the office double check behind me to make sure I wasn t going blind at one point  but of course they came to the same conclusion as me that everything looked like it was specified correctly  I am truly at a lost as to what is going on at this point   Could anyone help me with this issue    Another thing that came up as a possible reason this may be happening is that the app config is never being read  at least not the one I think should be getting read  Could this be the issue  If so  how can I go about addressing this issue  Again  ANY help would be appreciated

User · Answer

I just worked through this issue on my service. Here is the error I was receiving:

Service 'EmailSender.Wcf.EmailService' 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.

Here are the two steps I used to fix it:

Use the correct fully-qualified class name:

<service behaviorConfiguration="DefaultBehavior" name="EmailSender.Wcf.EmailService">

Enable an endpoint with mexHttpBinding, and most importantly, use the IMetadataExchange contract:
```
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
```

User · Answer

I had the same problem  Everything works in VS2010 but when I run the same project in VS2008 I get the mentioned exception   What I did in my VS2008 project to make it work was adding a call to the AddServiceEndpoint member of my ServiceHost object   Here is my code snippet   Uri baseAddress   new Uri  http   localhost 8195 v2 SystemCallbackListener     ServiceHost host   new ServiceHost typeof SystemCallbackListenerImpl   baseAddress    host AddServiceEndpoint typeof CsfServiceReference SystemCallbackListener                           new BasicHttpBinding                            baseAddress   host Open      I didn t modify the app config file  But I guess the service endpoint could also have been added in the  config file

User · Answer

As another clue  that indeed fixed this issue in my case    I m migrating some WCF services from a console application  that configures in code few WCF services  to an Azure WebRole to publish them in Azure  Every time I add a new service VS edits my web config and adds this line    lt serviceHostingEnvironment aspNetCompatibilityEnabled  true  multipleSiteBindingsEnabled  true  gt    Well  with all the advices and answers above I couldn t make it work until I removed all the attributes in the serviceHostingEnvironment element  As you can see I m not a WCF rockstar but I made it to work with the first Service just by configuring it as    lt service name  FirstService  behaviorConfiguration  metadataBehavior  gt                   lt endpoint address                     binding  wsHttpBinding                   bindingConfiguration  WSHttpBinding WcfServicesBinding                   contract  IFirstService    gt                lt  service gt    but when I added the second Service it stoped working and I realized that those attributes where there again   I hope it saves you time

User · Answer

One thing to think about is  Do you have your WCF completely uncoupled from the WindowsService  WS   A WS is painful because you don t have a lot of control or visibility to them  I try to mitigate this by having all of my non-WS stuff in their own classes so they can be tested independently of the host WS  Using this approach might help you eliminate anything that is happening with the WS runtime vs  your service in particular   John is likely correct that it is a  config file problem  WCF will always look for the execution context  config  So if you are hosting your WCF in different execution contexts  that is  test with a console application  and deploy with a WS   you need to make sure you have WCF configuration data moved over to the proper  config file  But the underlying issue to me is that you don t know what the problem is because the WS goo gets in the way  If you haven t refactored to that yet so that you can run your service in any context  that is  unit test or console   then I d sugget doing so  If you spun your service up in a unit test  it would likely fail the same way that you are seeing with the WS which is much easier to debug rather than attempting to do so with the yucky WS plumbing

User · Answer

I ran Visual Studio in Administrator mode and it worked for me    Also  ensure that the app config file which you are using for writing WCF configuration must be in the project where  ServiceHost  class is used  and not in actual WCF service project

User · Answer

I just ran into this issue and checked all of the above answers to make sure I wasn t missing anything obvious  Well  I had a semi-obvious issue  My casing of my classname in code and the classname I used in the configuration file didn t match   For example  if the class name is CalculatorService and the configuration file refers to Calculatorservice     you will get this error

User · Answer

I just had this problem and resolved it by adding the namespace to the service name  e g     lt service name  TechResponse  gt    became    lt service name  SvcClient TechResponse  gt    I ve also seen it resolved with a Web config instead of an App config

User · Answer

To prepare the configration for WCF is hard  and sometimes a service type definition go unnoticed   I wrote only the namespace in the service tag  so I got the same error    lt service name  ServiceNameSpace  gt    Do not forget  the service tag needs a fully-qualified service class name    lt service name  ServiceNameSpace ServiceClass  gt    For the other folks who are like me

User · Answer

The endpoint should also have the namespace     lt endpoint address  uri  binding  wsHttpBinding  contract  Namespace Interface    gt

User · Answer

Just copy the App config file from the service project to the console host application and paste here and then delete it from the service project

User · Answer

This error will occur if the configuration file of the hosting application of your WCF service does not have the proper configuration    Remember this comment from configuration       When deploying the service library project  the content of the config   file must be added to the host s app config file  System Configuration   does not support config files for libraries    If you have a WCF Service hosted in IIS  during runtime via VS NET it will read the app config of the service library project  but read the host s web config once deployed  If web config does not have the identical  lt system serviceModel gt  configuration you will receive this error  Make sure to copy over the configuration from app config once it has been perfected

User · Answer

One crucial thing to remember for those working with a Console application to host the WCF service is that the Web config file in the WCF project is completely ignored  If your system serviceModel configuration is there  then you need to move that section of config to the App config of your Console project   This is in addition to the answers concerning ensuring the namespace is specified in the right places

User · Answer

Today i ran into same issue  posting here my mistake and correction of it so that it may help someone   While Re-structuring code  I had actually changed Service class and IService names and changed ServiceHost to point to this new Service class name  as shown in code snippet  but in my host applications App Config file i was still using old Service class name  refer config section s name field in below snippet   Here is the code snippet    ServiceHost myServiceHost   new ServiceHost typeof NewServiceClassName       and in App config file under section services i was referring to old serviceclass name   changing it to New ServiceClassName fixed issue for me      lt service name  ProjectName OldServiceClassName  gt            lt endpoint address    binding  basicHttpBinding  contract  ProjectName IService  gt             lt identity gt               lt dns value  localhost   gt             lt  identity gt           lt  endpoint gt           lt endpoint address  mex  binding  mexHttpBinding  contract  IMetadataExchange   gt           lt host gt             lt baseAddresses gt               lt add baseAddress     gt             lt  baseAddresses gt           lt  host gt         lt  service gt

User · Answer

I got a more detailed exception when I added it programmatically - AddServiceEndpoint   string baseAddress    http       Environment MachineName     8000 Service   ServiceHost host   new ServiceHost typeof Service   new Uri baseAddress       host AddServiceEndpoint typeof MyNamespace IService                           new BasicHttpBinding    baseAddress   host Open

User · Answer

My problem was when I renamed my default Service1 class for  svc file to a more meaningful name  which caused web config behaviorConfiguration and endpoint to correspond to old naming convention  Try to fix your web config

User · Answer

I had this error in a Windows Service when my WCF Service Library that I created was not connected for hosting  but was connected for connection  I was missing an endpoint   I wanted both connection and hosting in my Windows Service so that I could serve up the WCF Service to other connections  as well as have the main process of my Windows Service use it as well to do various tasks on a timer schedule    The fix was that I rightlcicked my App config file and chose Edit WCF Configuration  Then  I did the steps for Create Service so that I could connect to my WCF Service  Now I had two endpoints in my App config  not just one  One endpoint was for the connection to the WCF Service Library  and another was for the hosting of it

[.net] Service has zero application (non-infrastructure) endpoints

Examples related to .net

Examples related to wcf

Examples related to exception-handling

Examples related to wcf-configuration

Examples related to wcf-endpoint