Network Management

Empty city container cannot be added to regional group after group renaming in SolarWinds Platform

When you rename legacy groups (for example, Arxada, TROY, ET) to new regional groups (APAC, EMEA, AMER), one or more city-level containers may appear in Manage Groups but cannot be added to the new regional group because the container is empty and has no member definitions. This article explains how to fix the issue using the web console and, if required, an advanced SQL method.

First published date

1/23/2026 4:14 PM

Last published date

1/23/2026 4:37 PM

Overview

After updating your logical grouping model from project-based groups (for example, Arxada, TROY, ET) to region-based groups (APAC, EMEA, AMER), you might want to reorganize existing city containers so that data is grouped by region instead of just by project or city.

In this scenario:

New regional groups (APAC, EMEA, AMER) are created in SolarWinds.
Existing city groups (for example, ET - Modesto CA) should appear as child groups under the appropriate regional group (for example, AMER).
Other city groups can be added to the regional groups and correctly display nodes.
One specific city container appears in Manage Groups, but:
- It is empty (no member definitions).
- It cannot be added as a child of the regional group.
- When accessed, it may take 20–30 seconds to load and then shows as empty.

The requirement is to:

Update group naming from Arxada / TROY / ET to APAC / EMEA / AMER.
Reorganize data so it is grouped by region (APAC, EMEA, AMER) rather than only by project or city.
Ensure no changes are made to existing workflows, matrices, alerts, or other configurations—only naming and grouping of the data.

This article describes the root cause (an empty, broken container) and provides two resolutions:

A web console–based fix (recommended).
An advanced SQL-based fix (use with caution).

Product section

Network Performance Monitor

Cause

The affected city container exists in the Containers table with a valid ContainerID, but:

It has no member definitions in the ContainerMemberDefinitions table.
It may be incorrectly nested under another parent or left in a partially configured state.
Because it has no member definitions, the container is effectively empty and cannot behave like other city groups that use a dynamic query to populate nodes.

When you attempt to add this empty container under a regional group (for example, AMER), the platform cannot resolve its membership, which prevents the container from being added correctly and may cause long timeouts when the group is accessed.

Resolution

To fix this issue, first try to recreate the affected city container in the SolarWinds Web Console (recommended). If the UI method is not possible, use the SQL-based method to add a proper member definition and attach the city container to the regional group.

Resolution 1 – Fix the city container using the web console (recommended)

This method does not require database changes and is the preferred approach.

Step 1: Delete the broken city container

In the SolarWinds Web Console, go to Settings > All Settings > Manage Groups.
Locate the affected city container (for example, ET - Modesto CA).
Select the group and click Delete.
Confirm the deletion.

This removes the broken container definition. It does not delete any monitored nodes; only the logical group definition is removed.

Step 2: Recreate the city container as a dynamic group

In Manage Groups, click Add New Group.
In the Group Name field, enter the city group name, for example:
ET - Modesto CA
For Group Type, select Dynamic Query.
In the Dynamic Query builder, configure a filter that populates the group based on city and, if required, project or another custom property.

Example – filter by city only:
```
filter:/Orion.Nodes[CustomProperties.City='Modesto CA']
```
Example – filter by city and project:
```
filter:/Orion.Nodes[CustomProperties.City='Modesto CA' AND CustomProperties.Project='ET']
```
Click Preview (if available) to confirm that the expected nodes are returned.
Click Submit to create the group.

Step 3: Add the city container to the regional group

Go to Settings > All Settings > Manage Groups.
Locate and click the regional group (for example, AMER).
Click Add/Remove Objects.
In the object selection window, expand All Groups.
Locate the recreated city container (for example, ET - Modesto CA) and select it.
Click Submit to add it as a child group.

Step 4: Verify group membership

Browse to the regional group (for example, AMER) in the web console.
Confirm that the city container appears in the list of child groups.
Click the city group and verify that the expected nodes are listed.
- Allow 1–2 minutes for polling and group recalculation if nodes do not appear immediately.
Confirm that alerts, reports, and matrices that rely on these groups still function as expected. Only the naming and grouping should have changed.

Resolution 2 – Advanced SQL fix for empty containers (use with caution)

Warning: These steps directly modify data in the SolarWindsOrion database. Work with a database administrator (DBA), and make sure you have a recent, tested backup of the database. Do not run these queries without appropriate change control.

This method is useful if you cannot delete and recreate the group in the UI or if the container is in a locked or inconsistent state.

Step 1: Back up the database or relevant tables

Work with your DBA to create a full backup of the SolarWindsOrion database.

Optionally, you can back up specific tables before making changes:

-- Example: back up container-related tables
SELECT * INTO Containers_Backup FROM Containers;
SELECT * INTO ContainerMemberDefinitions_Backup FROM ContainerMemberDefinitions;

Step 2: Add a member definition for the empty container

In the queries below, replace the following placeholders with values from your environment:

<CityContainerID> – the ContainerID of the affected city container (for example, 25)
<CityName> – the City custom property value (for example, Modesto CA)
<ProjectValue> – optional Project custom property value (for example, ET)

Run the following script against the SolarWindsOrion database:

-- Disclaimer: Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind.
-- SolarWinds further disclaims all warranties including, without limitation,
-- any implied warranties of merchantability or of fitness for a particular purpose.
-- The risk arising out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation, production,
-- or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits,
-- business interruption, loss of business information, or other pecuniary loss)
-- arising out of the use of or inability to use the scripts or documentation.

-- Add a dynamic member definition for the city container
INSERT INTO ContainerMemberDefinitions 
    (ContainerID, Name, Entity, Definition, Expression)
VALUES 
    (
        <CityContainerID>, 
        'City group - <CityName>', 
        'Orion.Nodes', 
        'filter:/Orion.Nodes[CustomProperties.City='' <CityName> '']',
        'Nodes.CustomProperties.City = ''<CityName>'''
    );

-- If filtering by project is required, adjust Definition and Expression, for example:
-- Definition:
-- 'filter:/Orion.Nodes[CustomProperties.City='' <CityName> '' AND CustomProperties.Project='' <ProjectValue> '']'
-- Expression:
-- 'Nodes.CustomProperties.City = ''<CityName>'' AND Nodes.CustomProperties.Project = ''<ProjectValue>'''

Step 3: Add the city container to the regional group

In the queries below, replace:

<AmerContainerID> – the ContainerID of your regional group (for example, AMER = 76)
<CityContainerID> – the same ID used above
<CoreServerHost> – the hostname of your SolarWinds Platform server used in SWIS URIs

Then run:

-- Disclaimer: Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind.
-- SolarWinds further disclaims all warranties including, without limitation,
-- any implied warranties of merchantability or of fitness for a particular purpose.
-- The risk arising out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation, production,
-- or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits,
-- business interruption, loss of business information, or other pecuniary loss)
-- arising out of the use of or inability to use the scripts or documentation.

-- Add the city container as a child group under the regional (for example, AMER) group
INSERT INTO ContainerMemberDefinitions 
    (ContainerID, Name, Entity, FromClause, Expression, Definition)
VALUES 
    (
        <AmerContainerID>,
        'Orion.Groups.ContainerID=<CityContainerID>',
        'Orion.Groups',
        'Orion.Groups Groups',
        'Groups.Uri=''swis://<CoreServerHost>/Orion/Orion.Groups/ContainerID=<CityContainerID>''',
        'swis://<CoreServerHost>/Orion/Orion.Groups/ContainerID=<CityContainerID>'
    );

Step 4: Restart SolarWinds services

After updating the database, restart the following services on the SolarWinds Platform server (from an elevated PowerShell session):

Restart-Service OrionModuleEngine
Restart-Service SWInfoServiceSvcV3

Step 5: Validate the fix

Wait at least 5 minutes for polling and group recalculation to complete.
Refresh the browser or clear the cache (for example, Ctrl+F5).
In the web console, go to Settings > All Settings > Manage Groups.
Open the regional group (for example, AMER) and verify that the city container appears in the child group list.
Click the city container and confirm that it now shows the expected nodes.
Validate that existing alerts, reports, and matrices that rely on these groups still function as expected.

Rollback (if needed)

If the SQL-based fix causes issues, either restore from the full database backup or manually remove the rows that were added.

Example rollback for the specific changes above:

-- Disclaimer: Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind.
-- SolarWinds further disclaims all warranties including, without limitation,
-- any implied warranties of merchantability or of fitness for a particular purpose.
-- The risk arising out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation, production,
-- or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits,
-- business interruption, loss of business information, or other pecuniary loss)
-- arising out of the use of or inability to use the scripts or documentation.

-- Remove the member definitions for the city container
DELETE FROM ContainerMemberDefinitions 
WHERE ContainerID = <CityContainerID>;

-- Remove the city container from the regional (for example, AMER) group
DELETE FROM ContainerMemberDefinitions 
WHERE ContainerID = <AmerContainerID>
  AND Definition LIKE '%ContainerID=<CityContainerID>%';

After rollback, restart the same SolarWinds services and re-test.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.