WebRole with WCF Service got in "Busy" state after adding StandardEndpoint in web.config

I recently worked on
an incident in which the Windows Azure application had 1 web role and one WCF
role. Initially the basics application with no specific changes worked well on
compute emulator and on Windows Azure. After when we added the following configuration
in the web.config the application for stuck “Busy” on Azure:




                                  <standardEndpoint name=""
helpEnabled="true" automaticFormatSelectionEnabled="true" />




After little more investigation
inside the Windows Azure VM, I found that the reason for this issue is that the cloud VM's machine.config is
missing the following section:

<sectionGroup name="system.serviceModel"
System.ServiceModel, Version=, Culture=neutral,
   <section name="standardEndpoints"
System.ServiceModel, Version=, Culture=neutral,

After I added
above part in the machine.config, the role started without any further problem.


Comments (0)

Skip to main content