Especially in the Windows environment, the above error message will occur regardless of TCP. Net or HTTP. The solution is to modify the config file of both the server and client.
1. Modify the config file of the server
1. Copy the content of the <bindings>... </bindings> section in the config configuration file of the client to the <system. servicemodule> </system. servicemodule> section.
2. Modify the Verification Section in each <binding> </binding>. You do not need anything else in the Verification Section. If some configuration content already exists, delete it.
<Security mode = "NONE"> </Security>
3. Add bindingconfiguration = "connection name" to the configuration of each <endpoint> segment in the <services> segment, for example:
<Endpoint address = "service" binding = "nettcpbinding" bindingconfiguration = "tcpbinding" Contract = "servercoreservice. idatabaseservice" name = "tcpbinding"/>
2. Modify the config configuration of the ClientParts
Click 2nd and 3rd on the server.