none
WCF - Conflicting endpoints after .Net 4.5 installation on Windows Server 2008 R2 RRS feed

  • General discussion

  • We recently installed .NET framework 4.5 to our server and it is throwing a server error.  The WCF web service work fine prior to this installation.  We have applied the hot fix, https://support.microsoft.com/kb/2805226, but this hot fix did not resolve the issue. Any information or hot fix related information would greatly be appreciated. Thank you.

    Web Service web config
    --------------------------------------------------------------------------------

    <system.serviceModel>
        <protocolMapping>
          <add scheme="https" binding="basicHttpBinding" />
        </protocolMapping>
        <behaviors>
          <serviceBehaviors>
            <behavior>
              <serviceDebug includeExceptionDetailInFaults="true" />
              <serviceCredentials>
                <clientCertificate>
           <certificate findValue="XXXX" storeLocation="LocalMachine" storeName="My" x509FindType="FindBySerialNumber" />
                </clientCertificate>
              </serviceCredentials>
            </behavior>
          </serviceBehaviors>
        </behaviors>
        <bindings>
          <basicHttpBinding>
            <binding>
              <security mode="Transport">
                <transport clientCredentialType="Certificate" />
              </security>
            </binding>
          </basicHttpBinding>
        </bindings>
        <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
      </system.serviceModel>

    Server Error in '/XXXX/XXXX' Application.
    --------------------------------------------------------------------------------

    A binding instance has already been associated to listen URI 'URL'. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config. 
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

    Exception Details: System.InvalidOperationException: A binding instance has already been associated to listen URI 'URL'. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config. 

    Source Error: 

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

    Stack Trace: 


    [InvalidOperationException: A binding instance has already been associated to listen URI 'URL'. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config. ]
       System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost) +2494
       System.ServiceModel.ServiceHostBase.InitializeRuntime() +68
       System.ServiceModel.ServiceHostBase.OnBeginOpen() +37
       System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) +57
       System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) +388
       System.ServiceModel.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity) +120
       System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity) +647

    [ServiceActivationException: The service '/XXXX/XXXX/XXXX.svc' cannot be activated due to an exception during compilation.  The exception message is: A binding instance has already been associated to listen URI 'URL'. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config. .]
       System.Runtime.AsyncResult.End(IAsyncResult result) +421
       System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +174
       System.ServiceModel.Activation.HostedHttpRequestAsyncResult.ExecuteSynchronous(HttpApplication context, String routeServiceVirtualPath, Boolean flowContext, Boolean ensureWFService) +225
       System.ServiceModel.Activation.HttpModule.ProcessRequest(Object sender, EventArgs e) +341
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +198
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +70


     
    • Edited by tonyvang612 Thursday, August 6, 2015 1:15 PM
    Thursday, August 6, 2015 1:12 PM

All replies