nopSolutions/nopCommerce · error · NopException

System role could not be deleted

Error message

System role could not be deleted

What it means

Thrown by DeleteCustomerRoleAsync as a NopException when customerRole.IsSystemRole is true. System roles (Registered, Guests, Administrators, etc.) underpin authorization and cannot be removed; the guard prevents breaking role-based access control.

Source

Thrown at src/Libraries/Nop.Services/Customers/CustomerService.cs:1239

        var mapping = await _customerCustomerRoleMappingRepository.Table
            .SingleOrDefaultAsync(ccrm => ccrm.CustomerId == customer.Id && ccrm.CustomerRoleId == role.Id);

        if (mapping != null)
            await _customerCustomerRoleMappingRepository.DeleteAsync(mapping);
    }

    /// <summary>
    /// Delete a customer role
    /// </summary>
    /// <param name="customerRole">Customer role</param>
    /// <returns>A task that represents the asynchronous operation</returns>
    public virtual async Task DeleteCustomerRoleAsync(CustomerRole customerRole)
    {
        ArgumentNullException.ThrowIfNull(customerRole);

        if (customerRole.IsSystemRole)
            throw new NopException("System role could not be deleted");

        await _customerRoleRepository.DeleteAsync(customerRole);
    }

    /// <summary>
    /// Gets a customer role
    /// </summary>
    /// <param name="customerRoleId">Customer role identifier</param>
    /// <returns>
    /// A task that represents the asynchronous operation
    /// The task result contains the customer role
    /// </returns>
    public virtual async Task<CustomerRole> GetCustomerRoleByIdAsync(int customerRoleId)
    {
        var allRolesById = await GetAllCustomerRolesDictionaryAsync();

        return allRolesById.TryGetValue(customerRoleId, out var role) ? role : null;
    }

View on GitHub (pinned to 64bdf2ff08)

Solutions

1. Exclude system roles from delete actions: filter the list by IsSystemRole == false.
2. In the role-management UI, hide or disable the delete control for system roles.
3. If a role must effectively retire, deactivate it (Active=false) rather than delete.

Example fix

// before
await _customerService.DeleteCustomerRoleAsync(role);

// after
if (role.IsSystemRole)
    return; // or notify: system roles cannot be deleted
await _customerService.DeleteCustomerRoleAsync(role);

if (role.IsSystemRole) return; // protected
await _customerService.DeleteCustomerRoleAsync(role);

static bool IsDeletableRole(CustomerRole r) => r is not null && !r.IsSystemRole;

When it happens

Trigger: Calling DeleteCustomerRoleAsync on a role whose IsSystemRole flag is true (the seed/system roles).

Common situations: A role-management admin screen that lists all roles without hiding system ones; an automated cleanup that purges 'unused' roles by misclassifying them; a refactor that removed the IsSystemRole UI filter.

Related errors

• System customer account ({customer.SystemName}) could not be
• 'Registered' role could not be loaded
• Email cannot be null
• Account.EmailUsernameErrors.NewEmailIsNotValid
• Account.EmailUsernameErrors.EmailTooLong

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