The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Question

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

SunnySharma-4215 0

i have wcf service hosted in app service in azure created a client and test it works fine for me . now Scenerio is when i try to scale up the instance count to 2 in azure and restart and retest it i got this error "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state." now when i switch back to 1 instance and restart and retest again work fine so my problem is i have heavy loads to process for that i want to scale this wcf to 2 but when i do that i got this error on clinet side expection User's image

this error occurs when i scale my application from one instance to two instances. it works fine when i have only one instance. I'm using TransportwithMessageCredentials as mode of Secuirty..

SunnySharma-4215 0

Hi @Ryan Hill thank you for reply. the wcf application we have on azure app service here am creating a demo service of same wcf we have on azure and trying to scale it but it gives us this error User's image

we are using wsHttpBinding and this config settings this is our test model


<system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior name="WCFServiceBehaviour">
          <!-- To avoid disclosing metadata information, set the values below to false before deployment -->
          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/>
		 <serviceThrottling maxConcurrentCalls="500"  maxConcurrentInstances ="100" maxConcurrentSessions ="200"/>
          <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
          <serviceDebug includeExceptionDetailInFaults="false"/>
			<serviceCredentials>
				<clientCertificate>
					<authentication certificateValidationMode="None" revocationMode="NoCheck" />
				</clientCertificate>
				<userNameAuthentication userNamePasswordValidationMode="Custom" customUserNamePasswordValidatorType="WcfService1.CustomValidator,WcfService1"/>
			</serviceCredentials>
        </behavior>
      </serviceBehaviors>
    </behaviors>
	  <services>
		  <service behaviorConfiguration="WCFServiceBehaviour" name="WcfService1.Service1">
			  <endpoint address="" binding="wsHttpBinding" bindingConfiguration="wsHttpBindingWithTransportSecurity" contract="WcfService1.IService1"/>
			  <endpoint address="mex"
				  binding="mexHttpsBinding"
				  contract="IMetadataExchange" />
			  <host>
				  <baseAddresses>
					  <add baseAddress="https://wcfservice.azurewebsites.net/"/>
				  </baseAddresses>
			  </host>
		  </service>
	  </services>
	  <bindings>
		  <wsHttpBinding>
			  <binding name="wsHttpBindingWithTransportSecurity" >
				  <security mode="TransportWithMessageCredential">
					  <message clientCredentialType="UserName" />
				  </security>
			  </binding>
		  </wsHttpBinding>
	  </bindings>
    <!--<protocolMapping>
        <add binding="basicHttpsBinding" scheme="https" />
    </protocolMapping>-->    
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
  </system.serviceModel>

If i set security context to false on both client and server it works fine but there is secuirty compromise we need to do and also we need to update more than xxxx clients for Proxy update. we want something that don't include proxy updates. The error above resolved when we use Establishedsecuirtycontext to false it works but we don't want that we want to scale with default true value but it gives use error that am showing you everytime.

1 answer

Your answer

Answer 1

Ryan Hill 30,281 Microsoft Employee Moderator

Bear in mind there wasn't enough information provided to complete help resolve your issue. However, based on what you've provided, there could be several reasons why your WCF service wound up in a faulted state when scaling up to multiple instances. Remember, when scaling out your WCF service has to be configured to run simultaneously.

One possible cause is your service isn't initially designed to run to on multiple instances. This exposes your service to conflicts between instances, race conditions, and other synchronization issues. To resolve, look at implementing synchronization mechanisms such as a distributed cache and/or ensuring it's completely stateless.

Another possible reason could be a configuration issue. This could be using a binding that is not compatible or better suited with multiple instances. Bindings that are better suited are NetTcpBinding, NetHttpBinding, WSHttpBinding, and BasicHttpBinding.

There may also be an inner exception that was logged that led up to the faulted state; feel free to share any log snippets should the above suggestions not be helpful.

SunnySharma-4215 0

Hi @Ryan Hill thank you for reply. the wcf application we have on azure app service here am creating a demo service of same wcf we have on azure and trying to scale it but it gives us this error User's image

we are using wsHttpBinding and this config settings this is our test model


<system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior name="WCFServiceBehaviour">
          <!-- To avoid disclosing metadata information, set the values below to false before deployment -->
          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/>
		 <serviceThrottling maxConcurrentCalls="500"  maxConcurrentInstances ="100" maxConcurrentSessions ="200"/>
          <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
          <serviceDebug includeExceptionDetailInFaults="false"/>
			<serviceCredentials>
				<clientCertificate>
					<authentication certificateValidationMode="None" revocationMode="NoCheck" />
				</clientCertificate>
				<userNameAuthentication userNamePasswordValidationMode="Custom" customUserNamePasswordValidatorType="WcfService1.CustomValidator,WcfService1"/>
			</serviceCredentials>
        </behavior>
      </serviceBehaviors>
    </behaviors>
	  <services>
		  <service behaviorConfiguration="WCFServiceBehaviour" name="WcfService1.Service1">
			  <endpoint address="" binding="wsHttpBinding" bindingConfiguration="wsHttpBindingWithTransportSecurity" contract="WcfService1.IService1"/>
			  <endpoint address="mex"
				  binding="mexHttpsBinding"
				  contract="IMetadataExchange" />
			  <host>
				  <baseAddresses>
					  <add baseAddress="https://wcfservice.azurewebsites.net/"/>
				  </baseAddresses>
			  </host>
		  </service>
	  </services>
	  <bindings>
		  <wsHttpBinding>
			  <binding name="wsHttpBindingWithTransportSecurity" >
				  <security mode="TransportWithMessageCredential">
					  <message clientCredentialType="UserName" />
				  </security>
			  </binding>
		  </wsHttpBinding>
	  </bindings>
    <!--<protocolMapping>
        <add binding="basicHttpsBinding" scheme="https" />
    </protocolMapping>-->    
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
  </system.serviceModel>

If i set security context to false on both client and server it works fine but there is secuirty compromise we need to do and also we need to update more than xxxx clients for Proxy update. we want something that don't include proxy updates. The error above resolved when we use Establishedsecuirtycontext to false it works but we don't want that we want to scale with default true value but it gives use error that am showing you everytime.

Share via

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

1 answer

Your answer