Y
Yash
I have hosted my service on IIS 5.1 on Win XP. I have configured it as
follows:
.
.
.
<wsHttpBinding>
<binding name="WSHttp0">
<security mode="Transport">
<transport clientCredentialType="None" />
</security>
</binding>
</wsHttpBinding>
</bindings>
<services>
<service
behaviorConfiguration="WcfServiceLibrary.Service1Behavior"
name="WcfServiceLibrary.MyService">
<endpoint address="mex" binding="mexHttpBinding"
contract="IMetadataExchange" />
<endpoint address="" binding="wsHttpBinding"
name="WSEP" bindingName="WSHttp0"
contract="WCFContractsLib.IContract1" />
</services>
The client app has the exact same binding configuration. The client's
endpoint is configured as:
<endpoint address="https://lap442/WCF/MyService.svc"
binding="wsHttpBinding" bindingConfiguration="WSHttp0"
contract="WCFContractsLib.IContract1"
name="WSEP" />
When I access the service in IE, using this URL
https://lap442/WCF/MyService.svc
I get a descriptive page which means the service is working fine.
When I inspect the IIS logs, it shows:
15:11:35 127.0.0.1 GET /WCF/MyService.svc 200
When I access the service through a client app, I get an error in the
client that says:
"There was no endpoint listening at https://lap442/WCF/MyService.svc"
The Exception is:
"There was no endpoint listening at https://lap442/WCF/MyService.svc
that could accept the message. This is often caused by an incorrect
address or SOAP action. See InnerException, if present, for more
details."}
The inner exception is:
{"The remote server returned an error: (404) Not Found."}
When I inspect the IIS logs, it shows:
15:26:06 127.0.0.1 POST /WCF/MyService.svc 404
What could be the reason behind such an error. What changes do I need
to make in the config.
Thanks,
Yash
follows:
.
.
.
<wsHttpBinding>
<binding name="WSHttp0">
<security mode="Transport">
<transport clientCredentialType="None" />
</security>
</binding>
</wsHttpBinding>
</bindings>
<services>
<service
behaviorConfiguration="WcfServiceLibrary.Service1Behavior"
name="WcfServiceLibrary.MyService">
<endpoint address="mex" binding="mexHttpBinding"
contract="IMetadataExchange" />
<endpoint address="" binding="wsHttpBinding"
name="WSEP" bindingName="WSHttp0"
contract="WCFContractsLib.IContract1" />
</services>
The client app has the exact same binding configuration. The client's
endpoint is configured as:
<endpoint address="https://lap442/WCF/MyService.svc"
binding="wsHttpBinding" bindingConfiguration="WSHttp0"
contract="WCFContractsLib.IContract1"
name="WSEP" />
When I access the service in IE, using this URL
https://lap442/WCF/MyService.svc
I get a descriptive page which means the service is working fine.
When I inspect the IIS logs, it shows:
15:11:35 127.0.0.1 GET /WCF/MyService.svc 200
When I access the service through a client app, I get an error in the
client that says:
"There was no endpoint listening at https://lap442/WCF/MyService.svc"
The Exception is:
"There was no endpoint listening at https://lap442/WCF/MyService.svc
that could accept the message. This is often caused by an incorrect
address or SOAP action. See InnerException, if present, for more
details."}
The inner exception is:
{"The remote server returned an error: (404) Not Found."}
When I inspect the IIS logs, it shows:
15:26:06 127.0.0.1 POST /WCF/MyService.svc 404
What could be the reason behind such an error. What changes do I need
to make in the config.
Thanks,
Yash