Signalr: Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

[last-Programmer]

We have upgraded Microsoft Azure Service Bus to version 3.0 and it seems to be that signal is breaking with the following error message

Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.TypeLoadException: Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[TypeLoadException: Could not load type 'Microsoft.ServiceBus.Messaging.MessageClientEntity' from assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.]
Microsoft.AspNet.SignalR.ServiceBus.ServiceBusConnection..ctor(ServiceBusScaleoutConfiguration configuration, TraceSource traceSource) +0
Microsoft.AspNet.SignalR.ServiceBus.ServiceBusMessageBus..ctor(IDependencyResolver resolver, ServiceBusScaleoutConfiguration configuration) +227
Microsoft.AspNet.SignalR.DependencyResolverExtensions.UseServiceBus(IDependencyResolver resolver, ServiceBusScaleoutConfiguration configuration) +64
Sgc.Web.Code.Generic.SignalROWinStartup.Configuration(IAppBuilder app) +279

[tvanfosson]

I had a similar issue, seems to be resolved in 3.0.2

[last-Programmer]

I upgraded the azure servicebus to version 3.0.2 and the problem remains.

[nmehlei]

We noticed this as well and are already using the latest versions on NuGet.

[gregheidorn]

Just tried 3.0.0 and 3.0.3 and got this issue. Downgraded back to 2.7.6 until further notice.

[profnimrod]

I have also stuck with 2.7.6 because of the same problem reported above with 3.0.x.

[slashdotdash]

Encountered the same exception as above; resolved by downgrading WindowsAzure.ServiceBus to version 2.7.6

[kunjan13]

Encountered the same exception as above; in version 3.0.3.
Reverting back till we have any updates on issue

[ghost]

3.0.4 has the same issue. Reverted to 2.7.6.

[sondreb]

Here is a forum thread with the same issue, for reference: http://forums.asp.net/t/2065443.aspx

Please give us an update on when this is planned to be fixed?

[noocyte]

As far as I can see from the code the problem is that the Servicebus Scaleout code is using Begin/End async pattern; this has been removed from Service Bus SDK version 3 (it looks like). So in essence the service bus scaleout code has to be re-written to use async/await pattern.

I have re-written it so it compiles (https://github.com/proactima/SignalR), but not super happy about the implementation. However, as long as the processing is running in a threadpool thread it does not have to be async at all.

[iamshotgun]

we upgraded to version 3.0.7, still the same error. we went back to 2.7.6.

[dersia]

Any news here? Just had to rollback to 2.7.6

[MaDeRkAn]

We have same issue.

[ucswift]

+1, just verified with 3.0.9

[kjartanvalur]

+1 verified with 3.0.9 and the newly released 3.1.1

[francescocristallo]

Any news on this problem? It's now 5 months, I`m stuck with an old release of Service bus SDK cause of this. The problem persist with 3.1.1 release as well

[MaDeRkAn]

@LightCrystal Service Bus is used by SignalR, Therefore I don't think sb team will change something for this. It looks like versioning issue and it's normal if u go 2 to 3. We should wait signalr team to fix it. And they focused on 3.0. So I don't think we will have minor update. If someone digs this issue and starts a branch I would like to help.

[kunjan13]

is this issue solved in 3.1.4?

[evilpilaf]

I'm also having this problem, it's incredible that after all this time no one from microsoft is responding to this issue and we're left with an old and obsolete version of the service bus libraries.

[erichexter]

@davidfowl @DamianEdwards Guys, can you help us get some communication of this issue?

[paulirwin]

It has been almost 8 months and this issue remains. Can we get an update on this?

[erichexter]

I talked with the head program manager and they are planning on testing
this out after the asp.net core 1 goes into release candidate. Don't know
the dates but they have a plan for how they intended to test this out , and
have given a verbal commitment to get it done.

On Thursday, May 5, 2016, Paul Irwin [email protected] wrote:

It has been almost 8 months and this issue remains. Can we get an update
on this?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/SignalR/SignalR/issues/3548#issuecomment-217226544

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

[joelclickpoint]

I need a SignalR+AzureServiceBus replacement at this point, anyone have any thoughts on options I can move forward with before I start researching independently?

[MaDeRkAn]

@joelclickpoint You can try Signalr+Redis.

[noocyte]

It looks like the code has been updated already, it's just waiting to get pushed out... Since the current release is almost 1,5 years old it might be time for another release @DamianEdwards ?

[demirag]

This issue is getting annoying.

Lifecycle: Nuget-> upgrade all packages -> downgrade servicebus

Anyone knows if there will be a support at all?

[erichexter]

I believe they are testing the fix now on https://jabbr.net/

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

On Thu, Jun 9, 2016 at 9:46 AM, Yusuf Demirag [email protected]
wrote:

This issue is getting annoying.

Lifecycle: Nuget-> upgrade all packages -> downgrade servicebus

Anyone knows if there will be a support at all?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SignalR/SignalR/issues/3548#issuecomment-224917876,
or mute the thread
https://github.com/notifications/unsubscribe/AAHABO_igUXQeeuAPHYVsVHFo7P9Sl5Dks5qKCdKgaJpZM4F73Gv
.

[markheath]

@erichexter do you have any more information on this? Is the code for the fix available to view anywhere? This is a real problem for us in a project that we are trying to introduce SignalR to and can't easily downgrade to an older servicebus package.

[joelclickpoint]

@erichexter I'd recommend doing what we had to do and just switch to SignalR+Redis, you can spin up an Azure-hosted Redis instance for fairly cheap and the configuration is basically the same:

GlobalHost.DependencyResolver.UseRedis(new RedisScaleoutConfiguration(connString, "appname"));
app.MapSignalR();

[erichexter]

We just built from the pull request it has been in production for months
now. Works just just fine for us.

On Friday, July 1, 2016, joelclickpoint [email protected] wrote:

@erichexter https://github.com/erichexter I'd recommend doing what we
had to do and just switch to SignalR+Redis, you can spin up an Azure-hosted
Redis instance for fairly cheap and the configuration is basically the same:

GlobalHost.DependencyResolver.UseRedis(new
RedisScaleoutConfiguration(connString, "appname"));
app.MapSignalR();

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SignalR/SignalR/issues/3548#issuecomment-229947199,
or mute the thread
https://github.com/notifications/unsubscribe/AAHABMeOM-lc8oo7xfkbKJcwp9IRRHnvks5qRRbGgaJpZM4F73Gv
.

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

[maxal1917]

We switched to Redis. It works.

[markheath]

@erichexter thanks, couldn't see anything in the list of open PRs. Was it this one you used?

[markheath]

I've come up with a fairly simple fix of my own (commit here) which seems to work, by simply creating extension methods to fake the missing APM methods. I'll submit a PR if it passes further testing.

[keithl8041]

I forked and built the version by @markheath but wasn't able to get it working (surely my own fault rather than Marks), so have downgraded to v2.8.2 until this is fixed officially.

[markheath]

@keithl8041 make sure you built from the bug-3548 branch - it's not merged into the dev branch on my fork. Does seem to be working in our initial testing.

[jarlem]

@markheath Did you only build the "Microsoft.AspNet.SignalR.ServiceBus" project and referenced the dll? Or did you build and include the other SignalR projects as well? Did you make a nuget package out of it? ... I can't get it to work by just building and referencing the new dll...

[markheath]

@jarlem yes, it's a bit of a pain to use the updated ServiceBus DLL as you'd also need to bring in the main SignalR dll you built as well due to strong naming. We ended up making our own company NuGet package of just the SignalR.ServiceBus project, which referenced the main NuGet SignalR package. I've also got a little sample application proving it working with two separate web projects communicating through servicebus that I can share once if strip out our servicebus connection string from the code.

[keithl8041]

Mark, please do share that if you can. I was having the same issue when
trying to get it to run.

[markheath]

@keithl8041 try this: https://1drv.ms/u/s!Aoaqn397na7vjakf5oTlQwCG1Rt7VA
Set both web projects as startup projects, and paste in your service bus connection string to both Startup.cs files.

[alexjamesbrown]

as others reported, i couldn't get it to work with anything above 2.7.6

[alexjamesbrown]

Looks like someone needs to change their email password

[iamshotgun]

tried last night, same problem...

[profnimrod]

I'd been waiting for more than a year for this issue to be fixed. Last week I decided to switch over to using Redis Cache for the backplane, and it works fine.

[snekbaev]

Indeed. We decided to use Azure Service Bus as the backplane, at the moment developing the app based on custom aforementioned fix. Hopefully when we go to production it won't cause any surprises :)

[moozzyk]

The problem is that because of the breaking changes in the Service Bus 3.0+ updating SignalR packages to this version in a minor/patch release would either prevent people from updating to the latest version of SignalR or would break them. Servicing releases should not have breaking changes. I have not tried it myself but I saw a package on NuGet which claims it is a Service Bus backplane for SignalR using ServiceBus 3.0.

[snekbaev]

@moozzyk isn't it possible to release a major version then? I believe eventually what matters is the ability to use the latest version of dependencies, which will be minor/patch upgradable themselves, but mainly, get a tested and production ready version from the SignalR team itself.

[moozzyk]

@snekbaev - we are working on the next major release but things will most likely look differently there.

[KeishaW]

Why is a fix for this problem taking so long? I recently encountered the same problem, but this thread was started over a year ago. The use of redis is currently not the best option for my solution, hence I was looking for a fix for the ServiceBus 3.0+ issue.

[KSemenenko]

Hi, I have the same problem, tried different versions but it still does not work. what is the problem? someone fix it?

[bogdangrigg]

We are experiencing the same issues - is there a planned fix?
Is the Azure Service Bus still a supported scale-out option?

[philcarbone]

Hello? Anyone paying attention here?

[moozzyk]

See my comment above: https://github.com/SignalR/SignalR/issues/3548#issuecomment-258205034

[isobarfilippis]

Are you freeking kidding me? Just recompiled SignalR.ServiceBus against WindowsAzure.ServiceBus 3.4.4 and all I had to change is a couple BeginXXX to XXXAsync. It was like 10 minutes and your library is actually broken for 1.5 years. Again are you freeking kidding me?

[itsmaryann]

Thanks for fixing the issue. When will 2.2.2 be released? We are awaiting a fix for a long time now. :)

[moozzyk]

2.2.2-preview1 is now on NuGet

[erichexter]

We just tested this out Microsoft.AspNet.SignalR.ServiceBus" 2.2.2-preview1 and we still get this error when referencing WindowsAzure.ServiceBus 3.1.5 @davidfowl

[BrennanConroy]

You need to use the Microsoft.AspNet.Signalr.ServiceBus3 package, because changing the normal one to use ServiceBus 3 would be a breaking change we had to make a new package name.

[erichexter]

Thanks, missed that in the notes. Wouldn't it make sense to change the major version number of the package? That would allow the breaking change and it would be discoverable.

[ranadheerrannu]

Is this issue still exists ? I am still facing it

[moozzyk]

@ranadheerrannu - You need to use the Microsoft.AspNet.Signalr.ServiceBus3 package with ServiceBus 3.0 (see: https://github.com/SignalR/SignalR/issues/3548#issuecomment-296326048)

[BayerWhite]

Confirmed that using NuGet -package Microsoft.AspNet.SignalR.ServiceBus3 with NuGet -package WindowsAzure.ServiceBus works.

Feel free to remove package Microsoft.AspNet.SignalR.ServiceBus once "ServiceBus3" is installed.

[juniwang]

Microsoft.AspNet.Signalr.ServiceBus3 works well with the latest stable WindowsAzure.ServiceBus 4.1.6. And you guys need to update the related documents as well like https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus. Everyone would encounter this problem by following your examples/docs.

[luizs81]

For God sake, someone should update the documentation: https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus

I wasted kinda long time trying to find the problem on my code/configuration.

[kotpal]

Please update the documentation at https://docs.microsoft.com/en-us/aspnet/signalr/overview/performance/scaleout-with-windows-azure-service-bus. The package Microsoft.AspNet.Signalr.ServiceBus doesn't work and only Microsoft.AspNet.Signalr.ServiceBus3 should be used.

[davidfowl]

/cc @rachelappel

[kotpal]

Thanks, @davidfowl . For those of us not yet ready to move to ASP.NET Core, it is also good to have a no-jQuery SignalR ES6 module which we can use in Angular and other modern JavaScript framework.

[davidfowl]

For those of us not yet ready to move to ASP.NET Core, it is also good to have a no-jQuery SignalR ES6 module which we can use in Angular and other modern JavaScript framework.

We have no plans to do that work.

[kotpal]

I guess the previous plans - https://twitter.com/davidfowl/status/781391761327304704 - didn't pan out then.

[davidfowl]

ASP.NET Core SignalR's js client doesn't support jQuery. We have no plans to go back and rewrite the ASP.NET SignalR js client.