Lawrence Avery
asked on
WCF Service - connecting by net.tcp
I receive the following calling my WCF Service using the net.tcp protocol on IIS7(WAS)
[The message could not be dispatched because the service at the endpoint address 'net.tcp://localhost:9090/ Appointmen tServiceII SHost/Appo intmentSer viceIISHos t.svc' is unavailable for the protocol of the address.
I enabled the protocol on the website and the application. I enable Non-HTTP activation.
web.config
[The message could not be dispatched because the service at the endpoint address 'net.tcp://localhost:9090/
I enabled the protocol on the website and the application. I enable Non-HTTP activation.
web.config
Did you enable net.tcp on the site (not your application, but the whole site)?
ASKER
Yes enabled protocol ( http,net.tcp) on the Default Website. I also edited permission of application by giving permissions to the IIS_IUSR and Network Service accounts.
I received the same message below:
The message could not be dispatched because the service at the endpoint address 'net.tcp://localhost:9090/ Appointmen tServiceII SHost/Appo intmentSer viceIISHos t.svc' is unavailable for the protocol of the address.
I received the same message below:
The message could not be dispatched because the service at the endpoint address 'net.tcp://localhost:9090/
ASKER
I think I got further; I am receiving this message now:
There was no endpoint listening at net.tcp://localhost:9090/A ppointment ServiceHos tIISHost/A ppointment ServiceIIS Host.svc that could accept the message. This is often caused by an incorrect address or SOAP action.
There was no endpoint listening at net.tcp://localhost:9090/A
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
See above comment.