All About Distributed apps

  • Comments
  • Please provide an example client config to that would use this service.  This would complete the picture for those of us trying to learn WCF.

  • Hi,

    I'm developing WCF application.

    During  which I'm getting error "The remote server returned an unexpected response: (400) Bad Request." even after  increasing the request quota size in the configuration file at the client side to "2147483647"

    Can you please help me out to resolve the issue.



  • <configuration>



         <add name="Microsoft.Transactions.Bridge" value="4" />

         <add name="GatewayTracing" value="4" />

         <add name="Microsoft.Transactions.Wsat" value="4" />


       <trace autoflush="true" indentsize="4">


           <add name="MSTB Trace File"


                initializeData="MSDTC\msdtc.trace.log" />





  • hi,

    can you explain the importance in detail and where exactly I should add this Tag in Web.config file?


  • PingBack from

  • Have you seen the case when there is no error description for the RPC test failure?  This is what I am getting:


        DTCping 1.9 Report for DEVDB01  


    RPC server is ready

    ++++++++++++Validating Remote Computer Name++++++++++++

    07-29, 16:39:50.683-->Start DTC connection test

    Name Resolution:


    07-29, 16:39:50.730-->Start RPC test (DEVDB01-->DEVWEB01)

    RPC test failed

  • Dan, I didn't see RPC failure without error code, Can you please let me know what is the operating system and service pack you have on these machines?

  • Vinay, 1722 error means "The RPC server is unavailable", Please check you are able to ping remote machine and able to telnet to port 135.



    Delay activity has issues when the workflow is exposed as web service. The time out

    duration of 0 works just great. If we put the time duration as 1 second or greater,

    the web service just hangs.



    By Default WebService workflows use the ManualWorkflowSchedulerService without

    active timers. So when the delay is hit, the workflow yields the thread back to the

    scheduler, and when the delay expires, nobody is around to call RunWorkflow. If you

    look in the web.config for the service you should see the entry for the scheduler

    service and you can add in the UseActiveTimers=true which will cause the workflow

    to resume when the delay expires.

    Have the entry in web.config as follows and it fixes the issue:

    <add type="System.Workflow.Runtime.Hosting.ManualWorkflowSchedulerService,

    System.Workflow.Runtime, Version=, Culture=neutral,

    PublicKeyToken=31bf3856ad364e35" useActiveTimers="true"/>

  • We may get 400 Bad request for different reasons, it may or may not be related to reader quotas, Please enable WCF tracing, Tracing will show why server throwing 400 error

Page 5 of 5 (70 items) 12345