Geek Answers Handbook

What are the causes of a ServiceActivationException?

I have a service hosted in an Azure environment. I use this service using a console application. in doing so I get the “Requested Service”, http://xxxx-d.yyyy.be/Services/zzzzInService.svc 'cannot be activated. See server trace trace logs for more information. "

Can someone help me find what I am missing?

A service is defined as follows:

<service name="xxxx.AppServer.Host.Services.yyyyy.zzzzPlugInService" behaviorConfiguration="MetadataBehavior" xdt:Locator="XPath(//service[@name='xxxx.AppServer.Host.Services.yyyy.zzzzPlugInService'])" xdt:Transform="Replace"> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="basicHttpBinding" contract="xxxx.Shared.IntegrationServices.yyyy.IzzzzPlugInService"> <identity> <dns value="localhost"/> </identity> </endpoint> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="basicHttpsBinding" contract="xxxx.Shared.IntegrationServices.yyyy.IzzzzPlugInService"> <identity> <dns value="localhost"/> </identity> </endpoint> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>

when I use the link http://xxxx-d.yyyy.be/Services/zzzzInService.svc in the browser, I get these messages -

The binding in system.serviceModel / bindings / basicHttpBinding does not have a binding configured with the name "basicHttpBinding". This value is not valid for bindingConfiguration.

a source:

 <endpoint address="" binding="basicHttpBinding" bindingConfiguration="basicHttpBinding" contract="xxxx.Shared.IntegrationServices.zzzzz.IzzzzPlugInService">
+4
source share
3 answers

The error indicates that you do not have a binding configuration for "basicHttpBinding" named "basicHttpBinding". Since you have not published the full configuration, and the error message states that I will assume that this is so.

The configuration below (under <system.serviceModel> ) has two binding definitions in <basicHttpBinding> , one for each binding configuration that you have in your endpoint declarations. You should also have something similar in your configuration.

 <services> <service name="xxxx.AppServer.Host.Services.yyyyy.zzzzPlugInService" behaviorConfiguration="MetadataBehavior" xdt:Locator="XPath(//service[@name='xxxx.AppServer.Host.Services.yyyy.zzzzPlugInService'])" xdt:Transform="Replace"> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="basicHttpBinding" contract="xxxx.Shared.IntegrationServices.yyyy.IzzzzPlugInService"> <identity> <dns value="localhost"/> </identity> </endpoint> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="basicHttpsBinding" contract="xxxx.Shared.IntegrationServices.yyyy.IzzzzPlugInService"> <identity> <dns value="localhost"/> </identity> </endpoint> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/> </service> </services> <bindings> <basicHttpBinding> <binding name="basicHttpBinding" /> <binding name="basicHttpsBinding"> <security mode="Transport" /> </binding> </basicHttpBinding> </bindings>
+2
source

I got this exception when debugging from Visual Studio 2013. I restarted Visual Studio and it worked. I think Visual Studio was holding onto some bad things from a previous debugging session.

0
source

One of the other reasons may be if you have duplicates or overload methods in the svc.cs file

0
source

More articles:


All Articles