Last post Nov 24, 2017 09:39 AM by maryor
Nov 20, 2017 04:45 PM|maryor|LINK
I built a SignalR host in a Console application. You need to start this 'server' as Administrator, but this works great.
Now I moved the same logic to a Windows Service project. Everything seems to work fine, but I'm unable to connect from a (WinForms) client. The service starts, it starts the same SignalR web app and it looks fine.
I configured it on:
and when browsing with Chrome to this address, I get the message as below. That's the same message when I get when the Console app is running.
Protocol error: Unknown transport.
My service is started under the LocalSystem account. I already tried to set the interactive with desktop flag. It seems the SignalR host is running, because otherwise you get an other error message (not found). When I start then my Console application,
it fails, because the port is in use. Everything seems to be okay, but I'm not able to connect with a client.
Anyone an idea? What's the difference between a Console app or Windows Service as host?
Thanks in advance!
Nov 21, 2017 07:49 AM|Eric Du|LINK
About this error message, if the client doesn't support the transports that SignalR uses, it will occur. For more details, please check the following tutorial:
About how to host SignalR in Windows Service, please check Self-Hosting SignalR in a Windows Service:
Nov 24, 2017 09:39 AM|maryor|LINK
Thank you for your answer! Unfortunetaly it doesn't work. I tried already the approach described in the blogpost. For me it seems that the SignalR server is running fine, but it doesn't allow connections. It's running, the same behaviour in the browser as
the Consol variant and it's holding the port..
I was hoping that anyone knows what the difference is between those two implementations... but thank you for your support.