Geek Answers Handbook

WCF Trace Error: Configuration Assessment Context Not Found

I installed a self-service script where I programmatically configure multiple service hosts. For each of these hosts that I open, I see the following error in the trace log:

<TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Warning"> <TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.EvaluationContextNotFound.aspx</TraceIdentifier> <Description>Configuration evaluation context not found.</Description> <AppDomain>myprogram.exe</AppDomain> </TraceRecord>

I read that this is caused by using extensions that are not declared in the configuration file, and I do use a custom behavior extension, but adding it to the .exe configuration file had no effect:

 <system.serviceModel> <extensions> <behaviorExtensions> <add name="myext" type="mytype, myassembly" /> </behaviorExtensions> </extensions> .... </system.serviceModel>

Please note that I do not use this extension anywhere in the configuration file, I add it to the service host programmatically. I even created fictitious behavior that the extension used to check if it would solve the problem, but it is not.

Why do I see this error in my journal?

+7
wcf
source share
3 answers

I had this problem and I found that in the ServiceReferences.clientconfig file I had several custom identifier bindings. I just commented on the extras and everything was fine. (I use Silverlight to call WCF services)

  <customBinding> <binding name="SecureTransportNoCredentialsEndpoint"> <binaryMessageEncoding /> <httpsTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" /> </binding> <!--<binding name="SecureTransportNoCredentialsEndpoint1"> <binaryMessageEncoding /> <httpsTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" /> </binding> <binding name="SecureTransportNoCredentialsEndpoint2"> <binaryMessageEncoding /> <httpsTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" /> </binding> <binding name="SecureTransportNoCredentialsEndpoint11"> <binaryMessageEncoding /> <httpsTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" /> </binding> <binding name="SecureTransportNoCredentialsEndpoint3"> <binaryMessageEncoding /> <httpsTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" /> </binding> <binding name="SecureTransportNoCredentialsEndpoint12"> <binaryMessageEncoding /> <httpsTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" /> </binding>--> </customBinding> </bindings>
+1
source share

In my case, I had a WCF interface with classes that contained the string property "GCM", and then added a new definition for the class "GCM". When I changed the class name to "GCMObj", the error disappeared.

0
source share

My experience is that you have to manually create a service with the service name and other details in the tag.

eg.

  <system.serviceModel> <services> <service name="WCF_NameSpace.Service1" behaviorConfiguration="behave"> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="bind" contract="WCF_Trace_2.IService1"></endpoint> </service> </services>
0
source share

More articles:


All Articles