C#

There can be many possible causes for this issue to occur, but here is one which we had encountered recently when application code was re-vamped and built with different class structures/names but still hosting environment was pointing to the old config file.

Resolution:

1. First, check applications config file thoroughly, mainly section <system.ServiceModel>
2. Check the current service class name used for hosting the service and verify with the configuration file in the below tag,

<service name="ProjectName.OldServiceClassName">  // if you are referring still to old service class name then this issue will occur; change this                                                                                                                  to new service class name
       <endpoint address="" binding="basicHttpBinding" contract="ProjectName.IService">
           <identity>
                <dns value="localhost"/>
           </identity>
      </endpoint>
     <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
     <host>
          <baseAddresses>
               <add baseAddress=""/>
         </baseAddresses>
     </host>
</service>

Here is my StackOverflow post on same,

https://stackoverflow.com/questions/2328840/service-has-zero-application-non-infrastructure-endpoints/53396938#53396938