Search

Jun 22, 2010

wsdl-service-soap-address location having machine name not domain name

After fixing “Domain name replaced with machine name in WCF Service”, you can find solution in my previous post.

I found same issue but somewhere else, when you look into wsdl at the end where all services are listed there still machine name exists.

image

And hence any of the client will have following error.

There was no endpoint listening at http://domainname/ServiceName.svc that could accept the message. This is often caused by an incorrect address or SOAP action.

That is because it still uses computer name in soap address not domain name. Lets fix this issue too. We have to simply change endpoint address nothing more.

<services>
<service behaviorConfiguration="serviceBehaviour" name="Demo.Service.MultiEndPointsService">
<endpoint address="http://192.168.1.2/Demo.Service/MultiEndPointsService.svc/basic" binding="basicHttpBinding" bindingConfiguration="basicBinding"
contract="Demo.Service.MultiEndPointsService" />
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="serviceBehaviour">
<serviceMetadata httpGetEnabled="true" httpGetUrl="http://192.168.1.2/Demo.Service/MultiEndPointsService.svc/basic"/>
<serviceDebug includeExceptionDetailInFaults="false" />
</behavior>
</serviceBehaviors>
</behaviors>

Now let’s how wsdl looks like.

image

We are good to go!

8 comments:

ARSH said...

Client throws exception: The caller was not authenticated by the service.

Anonymous said...

Thanks so much,
It's Working well!!

Anonymous said...

Thanks. It works.

Marcelo L Braga said...

Just work if i put the "/basic" after the .svc
Only with address.svc didnt work.

Anonymous said...

New at this, is the update in the web service config file or the client config file?

Anonymous said...

you are the best! thank you!

Piero Alberto said...

I love you man!!!

Piero Alberto said...

I love you man!!!