Geek Answers Handbook

WCF - there was no listening for endpoints in net.tcp: //..../Querier.svc that could receive a message

WCF There was no endpoint listening in net.tcp: // myserver: 9000 / SearchQueryService / Querier.svc that could receive this message.

I have net.tcp protocol enabled in IIS application

Windows Firewall Disabled

The net.tcp binding is installed on port 9000 for the entire IIS application.

My web.config is very standard:

<system.serviceModel> <diagnostics> <messageLogging logMalformedMessages="true" logMessagesAtServiceLevel="false" logMessagesAtTransportLevel="true" /> </diagnostics> <services> <service behaviorConfiguration="SearchQueryServiceBehavior" name="Search.Querier.WCF.Querier"> <endpoint address="mex" binding="mexHttpBinding" name="mexHttpEndpoint" contract="IMetadataExchange" /> <endpoint binding="netTcpBinding" bindingConfiguration="" name="netTcpEndpoint" contract="Search.Querier.WCF.IQuerier" /> </service> </services> <behaviors> <serviceBehaviors> <behavior name="SearchQueryServiceBehavior"> <serviceMetadata httpGetEnabled="true"/> <serviceDebug includeExceptionDetailInFaults="false"/> </behavior> </serviceBehaviors> </behaviors> </system.serviceModel>

And this setting works on one server, but not on another ... What could be the problem?

Both servers, working and not working, work with IIS7. The only difference is that the working box is Vista64 Sp2, and not the working box is W2k864.

+7
wcf wcf-client wcf-security
source share
3 answers

I think you are missing net.tcp in the "Enable Protocols" list in the advanced site settings.

+4
source share

Do you have .net 3.5 installed on a w2k864 machine? After installing it, did you run aspnet_iisreg?

Check your asp.net settings in IIS and make sure it is configured to use 2.0

Can you provide more information?

Also try using your ip rather than the host name. e.g. 192.168.1.100 instead of myserver

0
source share

When you go to the service ( http: //myserver/SearchQueryService/Querier.svc ), do you get error messages?

I also noticed that your client calls the net.tcp endpoint on port 9000. Does this IIS configuration match net.tcp? In the default configuration, your service call should point to net.tcp: //myserver/SearchQueryService/Querier.svc

0
source share

More articles:


All Articles