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

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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more