I've got a WCF Service that actually works fine in your area, on the server as well as on Azure. However am attempting to deploy exactly the same code to RackSpace Sites (Hosting That Is Shared Atmosphere is running .Internet 4.. IIS7 &lifier Home windows Server 2008) and am running within the following error once the service returns an answer:

Message:[System.ServiceModel.ProtocolException] = correctly. The very first 1024 bytes from the res...

InnerException:_innerException = came back a mistake: (500) Internal Server Error."

The truth is, even though fact is a mistake, the technique does effectively get the data and pass it in to the database, Therefore the problem appears to stay in the response back in the WCF Approach to the customer application. Has anybody encounter this before? I understand the trust levels on hosting that is shared may be responsible - but nothing I've attempted has appeared to relieve the errors I am getting.

Here's my configuration on the internet application consuming the WCF Service:

The Binding:

<binding title="BasicHttpBinding_IAccountService" closeTimeout="00:10:00"

      openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"

      allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"

      maxBufferSize="2147483647" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"

      messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"

      useDefaultWebProxy="true">

      <readerQuotas maxDepth="64" maxStringContentLength="2147483647" maxArrayLength="2147483647"

        maxBytesPerRead="4096" maxNameTableCharCount="16384" />

      <security mode="None">

        <transport clientCredentialType="None" proxyCredentialType="None"

          realm="" />

        <message clientCredentialType="UserName" algorithmSuite="Default" />

      </security>

    </binding>

And also the endpoint:

<client>

  <endpoint address="http://sitename.com/Services/AccountService.svc"

    binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IAccountService"

    contract="AccountService.IAccountService" title="BasicHttpBinding_IAccountService" /></client>

This is actually the default binding/endpoint produced when utilizing "Add Service Reference"

The application hosting the WCF Service doesn't use any custom designs, but this is actually the behaviors part of it's Web.Config:

<behaviors>

  <serviceBehaviors>

    <behavior title="">

      <serviceMetadata httpGetEnabled="true" />

      <serviceDebug includeExceptionDetailInFaults="true" />

    </behavior>

  </serviceBehaviors>

</actions>

<serviceHostingEnvironment multipleSiteBindingsEnabled="true"  />