Skip to main content

Orleans error: Orleans.Storage.BadProviderConfigException: No storage providers found loading grain type

Next step in my journey into Orleans land, was using ‘Declarative Persistence’. Sometimes you want the state inside your actors(grains in Orleans terminology) being persisted in some kind of permanent storage, so that it can survive a silo shutdown. Orleans provides a simple declarative model that makes this possible.

Unfortunately while following the related tutorial, I got the following error message:

[2016-10-04 07:19:17.848 GMT    11      ERROR   103104  Catalog 127.0.0.1:11111]        !!!!!!!!!! No storage providers found loading grain type Grains1.Manager

No storage providers found loading grain type Grains1.Manager

Exception = Orleans.Storage.BadProviderConfigException: No storage providers found loading grain type Grains1.Manager

   at Orleans.Runtime.Catalog.SetupStorageProvider(ActivationData data)

   at Orleans.Runtime.Catalog.CreateGrainInstance(String grainTypeName, ActivationData data, String genericArguments)

   at Orleans.Runtime.Catalog.SetupActivationInstance(ActivationData result, String grainType, String genericInterface)

   at Orleans.Runtime.Catalog.GetOrCreateActivation(ActivationAddress address, Boolean newPlacement, String grainType, String genericArguments, Dictionary`2 requestContextData, Task& activatedPromise)

   at Orleans.Runtime.Dispatcher.ReceiveMessage(Message message)

[2016-10-04 07:19:17.853 GMT    11      ERROR   101540  Dispatcher      127.0.0.1:11111]        !!!!!!!!!! Error creating activation for Grains1.Manager. Message NewPlacement Request S127.0.0.1:11111:213261543*cli/893aa39f@4423baaf->S127.0.0.1:11111:213261543*grn/913DAEDD/af761896@76d92c9c #4: global::GrainInterfaces1.IManager:AsEmployee()

Exc level 0: Orleans.Storage.BadProviderConfigException: No storage providers found loading grain type Grains1.Manager

   at Orleans.Runtime.Catalog.SetupStorageProvider(ActivationData data)

   at Orleans.Runtime.Catalog.CreateGrainInstance(String grainTypeName, ActivationData data, String genericArguments)

   at Orleans.Runtime.Catalog.SetupActivationInstance(ActivationData result, String grainType, String genericInterface)

   at Orleans.Runtime.Catalog.GetOrCreateActivation(ActivationAddress address, Boolean newPlacement, String grainType, String genericArguments, Dictionary`2 requestContextData, Task& activatedPromise)

   at Orleans.Runtime.Dispatcher.ReceiveMessage(Message message)

What I was missing were the following lines inside my orleansconfiguration.xml:

<OrleansConfiguration xmlns="urn:orleans">
  <Globals>
    <SeedNode Address="localhost" Port="11111" />
    <StorageProviders>
      <Provider Name="AzureStore" Type="Orleans.Storage.AzureTableStorage" DataConnectionString="UseDevelopmentStorage=true"/>
    </StorageProviders>
  </Globals>
  <Defaults>
    <Networking Address="localhost" Port="11111" />
    <ProxyingGateway Address="localhost" Port="30000" />
  </Defaults>
</OrleansConfiguration>

On my grains I had the following attribute added:

[StorageProvider(ProviderName = "AzureStore")]
public class Employee : Grain<EmployeeState>, IEmployee
{

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more