nopSolutions/nopCommerce · critical · Exception

No default store could be loaded

Error message

No default store could be loaded

What it means

Thrown by the installer when seeding default store-scoped entities (admin user, etc.). It loads the first Store record to obtain storeId for cross-references. If no Store row exists, there is no default store context and installation cannot continue. This means the store-seeding step (which creates the default Store) either did not run or failed.

Source

Thrown at src/Libraries/Nop.Services/Installation/InstallRequiredData.cs:2253

        var crVendors = new CustomerRole
        {
            Name = "Vendors",
            Active = true,
            IsSystemRole = true,
            SystemName = NopCustomerDefaults.VendorsRoleName
        };
        var customerRoles = new List<CustomerRole>
            {
                crAdministrators,
                crRegistered,
                crGuests,
                crVendors
            };

        await _dataProvider.BulkInsertEntitiesAsync(customerRoles);

        //default store 
        var defaultStore = await Table<Store>().FirstOrDefaultAsync() ?? throw new Exception("No default store could be loaded");

        var storeId = defaultStore.Id;

        //admin user
        var adminUser = new Customer
        {
            CustomerGuid = Guid.NewGuid(),
            Email = _installationSettings.AdminEmail,
            Username = _installationSettings.AdminEmail,
            Active = true,
            CreatedOnUtc = DateTime.UtcNow,
            LastActivityDateUtc = DateTime.UtcNow,
            RegisteredInStoreId = storeId
        };

        var defaultAdminUserAddress = await _dataProvider.InsertEntityAsync(
            new Address
            {

View on GitHub (pinned to 64bdf2ff08)

Solutions

1. Run the installer in its default order so the default Store is inserted first.
2. Reset the database to a clean state and reinstall.
3. Verify the Stores table contains the default store row before invoking this installer step.
4. Ensure no migration or script deleted the default Store out from under the installer.

Example fix

// before
var defaultStore = await Table<Store>().FirstOrDefaultAsync()
    ?? throw new Exception("No default store could be loaded");

// after - guard with actionable message
var defaultStore = await Table<Store>().FirstOrDefaultAsync()
    ?? throw new InvalidOperationException("Default Store not seeded; run the store installation step first.");

// Confirm a default store exists before referencing storeId
if (!await Table<Store>().AnyAsync())
    throw new InvalidOperationException("Default Store not seeded; run store installation first.");

static async Task<bool> HasDefaultStoreAsync(IRepository<Store> repo)
    => await repo.Table.AnyAsync();

try { await InstallStoreScopedEntitiesAsync(); }
catch (Exception ex) when (ex.Message == "No default store could be loaded")
{ /* seed the default Store, then retry */ }

When it happens

Trigger: Running installation before the default Store is inserted; a custom install order that delays Store seeding; a migration that removed all Store rows.

Common situations: Partial reinstall against a half-cleaned database; test database where Stores were truncated; installer interrupted mid-run leaving inconsistent state.

Related errors

• Default email account cannot be loaded
• Topic template cannot be loaded
• "{tName}" template could not be loaded
• "{tcName}" tax category could not be loaded
• "{cName}" category could not be loaded

AI-assisted analysis of nopSolutions/nopCommerce@64bdf2ff08 (2026-08-13). Data as JSON: /api/errors/f23aded1dc90d23c. Report an issue: GitHub.