Typecode not supported in cluster

[stephenlautier]

We recently updated to Orleans 2.4.2 + update SignalR.Orleans as well, and in certain cases we are getting error such as TypeCode $1903070868 not supported in the cluster

We should only have 1 cluster and all silos are all the same build and we dont use grain versioning either; Seeing slightly the code thats why it seems to be thrown if im correct, however in our case it shouldn't be the case

[Frank-Krick]

I see the same error oin 3.0.0-beta1 during Register as stream producer:

RegisterAsStreamProducer failed due to Orleans.Runtime.OrleansException: TypeCode $1903070868 not supported in the cluster

Btw. is there a way to get access to the Catalog so that I could get more information about the failing grain using GetGrainTypeInfo? Or is there another method to get more information about the grain from the type code?

[stephenlautier]

Not sure if this is the main reason to this, with a case like this should it work correctly?

• App host (project) had a dependency on Orleans e.g. 2.4.2 (and has grains with codegen)
• App depends on a library with Grains with Orleans 2.3.4 (with codegen)

If it should, it seems that when we have a dependency with a Grain (codegen) which the version of Orleans doesn't match ours, we either:

• Get this issue (like the issue posted)
  OR
• Extension not installed on grain e.g.

Extension not installed on grain SignalR.Orleans.Groups.GroupGrain attempting to invoke type Orleans.Streams.OrleansCodeGenStreamConsumerExtensionMethodInvoker from invokable Orleans.Runtime.ActivationData Such as this OrleansContrib/SignalR.Orleans#89

Also it doesn't always 100% not work, sometimes locally it does work and sometimes on the server it doesnt; OR sometimes locally you get everything from fresh and it doesn't work either

[MV10]

I've started getting intermittent Typecode $xxxxx not supported in the cluster on a demo/POC-style project. The project was shelved for about six months, and when I spun it up again I bumped all the Orleans packages up to the latest (as of last month). This is the only discussion I've found of that error message. It sounds as if the thinking here is that something goes wrong after an Orleans update?

How does one work out what the $xxxxx actually refers to?

(Unfortunately I can't post detailed logs -- those are locked away on a highly isolated development VM.)

Edit: This VM has two silos running side-by-side for dev purposes (supporting a UI website and another for the back-end service APIs), and I just noticed someone accidentally configured them with the same silo and gateway ports, which is obviously not going to work. But I'll leave my post here, I'd still like to understand how to interpret $xxxxx, in case someone can explain? (I realize it's a bit off-topic given the mis-configuration, sorry.)

[benjaminpetit]

Check that Microsoft.Orleans.CodeGenerator.MSBuild package is installed on your grain project

[benjaminpetit]

Closing for inactivity