Click here to Skip to main content
15,846,145 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I can navigate to http://localhost:8731 but I get the 503 error when trying to hit
http://localhost:8731/Design_Time_Addresses/RackleyService.DataConnection/AcordConnection/

HTML
<configuration>
  <configsections>
  </configsections>
    <system.servicemodel>
    <diagnostics>
      <messagelogging logmalformedmessages="true" logmessagesattransportlevel="true" />
    </diagnostics>
    <bindings>
      <basichttpbinding>
	  <binding name="RackleyServiceBinding" maxbuffersize="2147483647">
		maxReceivedMessageSize="2147483647" />
      </binding></basichttpbinding>
    </bindings>
    <client />
    <servicehostingenvironment multiplesitebindingsenabled="true">

    </servicehostingenvironment>
    <behaviors>
      <servicebehaviors>
        <behavior name="RackleyServiceBehavior">
          <servicemetadata httpgetenabled="true" />
			<servicedebug includeexceptiondetailinfaults="true" />
			<datacontractserializer maxitemsinobjectgraph="2147483647" />
        </behavior>
      </servicebehaviors>
      <endpointbehaviors>
        <behavior name="CrossDomainBehavior">
          <webhttp />
        </behavior>
      </endpointbehaviors>
    </behaviors>
    <services>
      <service behaviorconfiguration="RackleyServiceBehavior" name="RackleyService.DataConnection.AcordConnection">
        <endpoint address="Design_Time_Addresses/RackleyService.DataConnection/AcordConnection/">
          binding="basicHttpBinding" bindingConfiguration="RackleyServiceBinding" 
		  name="AcordConnection" contract="RackleyService.DataConnection.IAcordConnection">
          <identity>
            <dns value="localhost" />
          </identity>
        </endpoint>
        <endpoint address="mex" binding="mexHttpBinding" name="AcordMex">
          contract="IMetadataExchange" />
        <endpoint address="" behaviorconfiguration="CrossDomainBehavior">
          binding="webHttpBinding" name="CrossDomain" contract="RackleyService.DataConnection.ICrossDomainService">
          <identity>
            <dns value="localhost" />
          </identity>
        </endpoint>
        <host>
          <baseAddresses>
            <add baseaddress="http://localhost:8731/" />
          </baseAddresses>
        </host>
      </endpoint></service>
    </services>
  </system.servicemodel>
  <startup>
    <supportedruntime version="v4.0" sku=".NETFramework,Version=v4.0" />
  </startup>
  <system.net>
    <defaultproxy>
      <proxy bypassonlocal="False" usesystemdefault="True" />
    </defaultproxy>
  </system.net>
</configuration>
Posted
Updated 31-Jan-12 16:35pm
v5
Comments
ZurdoDev 31-Jan-12 15:12pm    
Service unavailable may mean the app pool has an issue. Try browsing the site from within IIS and see what happens and then check the event viewer. For example, if you also have a .Net 2.0 app in your .Net 4.0 app pool that can cause this issue.
sjones_30 6-Feb-12 13:14pm    
I am hosting the the WCF service in a windows service. I checked my local IIS and there was not an entry for the WCF service in the app pool. Should there be?

1 solution

Sounds like you might need to configure your crossdomain.xml file a little more to allow request through

http://msdn.microsoft.com/en-us/library/cc197955(VS.95).aspx[^]
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900