Problem PTWIN under WCF

Problem PTWIN under WCF

Old forum URL: forums.lhotka.net/forums/t/5936.aspx


cangfriend posted on Thursday, December 04, 2008

Normal 0 7.8 pt 0 2 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:表格內文; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}

Hello all , i'm new guy, i Have a problem in PTWIN under WCF,


www\WcfHost CONFIG FILE IN IIS

 

       <services>

      <service name="Csla.Server.Hosts.WcfPortal" behaviorConfiguration="returnFaults">

        <endpoint name="WcfDataPortal" contract="Csla.Server.Hosts.IWcfPortal" binding="mexHttpBinding" address="mex" />

              </service>

         </services>

         <behaviors>

              <serviceBehaviors>

                   <behavior name="returnFaults">

          <serviceMetadata httpGetEnabled="true"/>

                   </behavior>

              </serviceBehaviors>

         </behaviors>

     </system.serviceModel>



I can ask http://sfcserver03:8080/WcfHost/WcfPortal.svc usder  IE.


PTWIN CONFIG FILE

  <system.serviceModel>

 

    <client>

      <endpoint name="WcfDataPortal"

                address="http://sfcserver03:8080/WcfHost/WcfPortal.svc"

                binding="mexHttpBinding"

                contract="Csla.Server.Hosts.IWcfPortal" />

    </client>

 

  </system.serviceModel>


MESSAGE

There was no endpoint listening at http://sfcserver03:8080/WcfHost/WcfPortal.svc that could accept the message. This is often caused by an incourrect address or soap action......................


RockfordLhotka replied on Thursday, December 04, 2008

I doubt the mexHttpBinding will work for the data portal. That binding is designed to transfer metadata about the service, not to actually invoke the service.

You should be using wsHttpBinding or maybe basicHttpBinding.

Copyright (c) Marimer LLC