To fix common connection errors in WcfStorm, you must reconcile configuration mismatches between the tool’s test client and your host Windows Communication Foundation (WCF) service. Because WcfStorm serves as an external client, it frequently encounters transport protocol, security, or metadata mismatches if it is not explicitly configured to mimic your application’s app.config or web.config file.
The primary strategies for resolving the most frequent connection errors in WcfStorm are detailed below.
1. “The provided URI scheme ‘https’ is invalid; expected ‘http’”
This error occurs when you point WcfStorm to an HTTPS endpoint, but the internal client proxy generated by WcfStorm defaults to an unsecure HTTP transport binding.
The Fix: You must feed your service’s exact client configuration directly into WcfStorm. Step-by-step:
Open Visual Studio and create a temporary service reference to your hosted WCF service.
Visual Studio will generate a perfectly matched app.config or output.config file.
In WcfStorm, right-click your service name and select Edit Config or Discover Config.
Paste or upload the client binding section (specifically the Transport) generated by Visual Studio.
2. “EndpointNotFoundException” or “TCP Error 10061: Connection Refused”
This means WcfStorm cannot find a listening socket at the specified address, or the host machine actively blocked the attempt.
The Fix: Ensure your service is up and verify network paths.
Check the URL: If testing a service hosted on a remote server, do not use localhost in your WcfStorm address field; swap it for the actual host machine name or explicit IP address.
Firewall Ports: If you are using custom ports for net.tcp (e.g., port 808) or standard HTTP/HTTPS, verify that the host machine’s firewall allows inbound rules for that specific port.
IIS Setup: If hosted in IIS, ensure that WCF HTTP Activation is enabled via the Windows “Turn Windows features on or off” menu.
3. “The socket connection was aborted” / “An existing connection was forcibly closed”
Leave a Reply