Jun 07, 2016 01:17 AM|EricO64|LINK
I built a new project, a Windows Service, which includes a self-host, SignalR (188.8.131.52) server. This server app, as well as a client app, was created with VS 2015, on a Windows 10 box (build 10586.318).
The client I mentioned is a UWP app, which includes a C# SignalR client (184.108.40.206), designed to talk to the Windows Service. I've created several similar apps in the past, with SignalR, and have not encountered this type of problem. My client app will
not connect to my server app. Initially, I tested both apps on my development box, as I usually do with this type of application.
The client fails on the following, with an "An error occurred sending the request" message.
public async void StartConnection()
await hubConn.Start();// hubConn is of type
catch (Exception Ex)
connectError = Ex.Message;
Below is the stack dump.
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
The only major environment change I can think of, is the Windows 10 build version, of my development box. I believe I was on build 10240 previously. I thought that might be a factor, so I tried running my self-host, server app on a Windows 7 box but
the result is the same. I've tried a few different listening ports, above 10000, but same problem. Something which I found strange, if I run
netstat -a, on the box running my self host server, I don't see the port I configured listed.
Anyone else encountering this problem? Thanks