[Windows 7 doesn't support WebSocket.dll] "simple" sample result in a RelayException

Question

[Windows 7 doesn't support WebSocket.dll] "simple" sample result in a RelayException

pmhsfelix opened this issue 8 years ago · comments

I'm trying out the "simple" sample and when I run the server I get a RelayException with an inner exception stating The remote server returned an error: (500) Internal Server Error. All the four parameters (namespace, endpoint path, policy name and policy key seem to be ok - if I change any of them the error is and appropriate for the change.

dlstucki · Answer 1 · Tue Dec 06 2016 02:52:23 GMT+0800 (China Standard Time)

Will you include the full output of RelayException.ToString()? (Ideally that would have a TrackingId, Timestamp, and include the address, i.e. "sb://YOURNAMESPACE.servicebus.windows.net/YOURENDPOINT").

Pedro Felix · Answer 2 · Tue Dec 06 2016 03:15:27 GMT+0800 (China Standard Time)

InternalServerError. TrackingId:076fd61e-e290-4ce8-8943-1092806c95f0_G26, SystemTracker:sb://pmhsfelix.servicebus.windows.net/hybrid0, Timestamp:12/5/2016 7:14:20 PM

dlstucki · Answer 3 · Tue Dec 06 2016 04:18:41 GMT+0800 (China Standard Time)

That TrackingId is associated with this exception in the cloud side traces:

ActivityId = 076fd61e-e290-4ce8-8943-1092806c95f0
System.Net.WebSockets.WebSocketException (0x80004005): The ValidateWebSocketHeaders operation was called on an incoming WebSocket request without required 'Sec-WebSocket-Version' header.

Since the "simple" sample just uses HybridConnectionListener I'm curious what version of Microsoft.Azure.Relay.dll is being used. If you make sure that the latest nuget package is being used by your projects (Microsoft.Azure.Relay 0.1.2-preview) and run with that do you still get an internal server error? (Verify that when you select the "Microsoft.Azure.Relay" entry under "References" in Solution Explorer it shows a path like: "*\simple\packages\Microsoft.Azure.Relay.0.1.2-preview\lib\net45\Microsoft.Azure.Relay.dll").

Pedro Felix · Answer 4 · Tue Dec 06 2016 06:14:41 GMT+0800 (China Standard Time)

I didn't managed to build the "simple" sample directly due to the problem reported in #31. I removed the DLL that was being loaded directly from a "strange" path and installed Microsoft.Azure.Relay 0.1.2-preview.

Here is the content of my packages.config

<packages>
  <package id="Microsoft.Azure.Relay" version="0.1.2-preview" targetFramework="net452" />
</packages>

dlstucki · Answer 5 · Tue Dec 06 2016 06:34:52 GMT+0800 (China Standard Time)

You still get the InternalServerError exception with the latest 0.1.2-preview package?
Does the exception occur when trying to run the Server.exe?
What Operating System are you running this on?
Have you made any code or project changes at all that might affect the behavior?
Is the sample running as a 32 or 64 bit process?
Would it be possible for you to reproduce the issue with a debugger attached, stop at the very first first-chance exception after calling listener.OpenAsync(), and get a memory dump of the process? (In VS go to the Debug Menu -> Save Dump As...) I can give you a hybrid connection and keyname/keyvalue pair if you'd like. Contact me at dstucki (at) microsoft.com if you want me to do this.

Pedro Felix · Answer 6 · Tue Dec 06 2016 07:10:09 GMT+0800 (China Standard Time)

You still get the InternalServerError exception with the latest 0.1.2-preview package?

Yes

Does the exception occur when trying to run the Server.exe?

Yes

What Operating System are you running this on?

Windows 7 Professional SP1

Have you made any code or project changes at all that might affect the behavior?

No

Is the sample running as a 32 or 64 bit process?

Build is set to "Any CPU"

Would it be possible for you to reproduce the issue with a debugger attached, stop at the very first first-chance exception after calling listener.OpenAsync(), and get a memory dump of the process? (In VS go to the Debug Menu -> Save Dump As...) I can give you a hybrid connection and keyname/keyvalue pair if you'd like. Contact me at dstucki (at) microsoft.com if you want me to do this.

I've the memory dump and it's ~160MB. What's the best way to send it to you?

dlstucki · Answer 7 · Tue Dec 06 2016 07:17:19 GMT+0800 (China Standard Time)

This is most likely a Windows 7 compatibility issue then. I need to do some investigation into this. I don't think I need the memory dump at this time unless it should happen to work on Windows 7 for me.

dlstucki · Answer 8 · Tue Dec 06 2016 09:21:03 GMT+0800 (China Standard Time)

At this point we don't really support Windows 7. We're building on top of the .NET 4.5 System.Net.WebSockets.ClientWebSocket which also doesn't support Windows 7 (websocket.dll support from the OS is not there).

However, you may be able to get something working on your own by doing something like this example branch/commit:
Branch: https://github.com/dstuckims/azure-relay-dotnet/tree/PossibleWorkAroundForWindows7
Commit: https://github.com/dstuckims/azure-relay-dotnet/commit/ab4628939d6aba0c5904005e839ec62e04b2647f

I took the ManagedWebSocket class from .NET Core (they actually only use this implementation on *nix) and hacked it to build with .NET 4.5 (and simply removed the .NET Core build for the mean time, I wasn't trying to make it cross-compile for all platforms). This hasn't been tested but you may be able to take this example branch/commit, build your own copy of Microsoft.Azure.Relay.dll and get it to work on Windows 7 (you'll probably want to change the signing key and turn off delay signing on the library you build since it's not coming from Microsoft build labs). This is very unofficial at this point but I'm sharing it in case it might help.

dlstucki · Answer 9 · Wed Dec 07 2016 05:50:43 GMT+0800 (China Standard Time)

I have now tried the approach I mentioned above with the changes in that private branch of mine.

I built a new Microsoft.Azure.Relay.dll with those changes in https://github.com/dstuckims/azure-relay-dotnet/commit/ab4628939d6aba0c5904005e839ec62e04b2647f.
Updated the Simple sample to reference that newly built Microsoft.Azure.Relay.dll
Skipped verification on the Windows 7 machine by adding this registry entry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification\Microsoft.Azure.Relay,31BF3856AD364E35]
(or you could run "sn.exe -Vr Microsoft.Azure.Relay.dll", but I didn't have sn.exe on that machine at the time).

Then the "simple" sample server.exe and client.exe worked on Windows 7.

jburnsman · Answer 10 · Mon Sep 11 2017 03:38:48 GMT+0800 (China Standard Time)

Just wanted to confirm I used the method described for updating Microsoft.Azure.Relay.dll, and it successfully worked for using Relay on Windows 7. Thanks

jburnsman · Answer 11 · Mon Oct 16 2017 10:57:04 GMT+0800 (China Standard Time)

Could this modification in ab46289 be ported to the 1.0.0 release of Azure.Relay? I'd like to use this on Win7 and would prefer using the 1.0.0 version instead of a pre-release version. I have tried myself but have not had any luck getting a clean build yet. Thanks very much

dlstucki · Answer 12 · Thu Jan 09 2020 03:06:50 GMT+0800 (China Standard Time)

Windows 7 support will end on January 14, 2020

Closing as won't fix.

osexpert · Answer 13 · Wed Sep 09 2020 05:37:07 GMT+0800 (China Standard Time)

Beating a dead horse? But 2.0.1 works fine on Windows 7 as long as using the netstandard2.0 assembly (as it is using managed websockets I assume) while net451 assembly does not work (as it is using native websockets I assume, and you get platform not supported).

Geovanny Alzate Sandoval · Answer 14 · Thu Nov 05 2020 07:21:39 GMT+0800 (China Standard Time)

@jburnsman do you have that dll? I haven't been able to build that branch