Configuration Wizard fails during Services configuration after upgrade to SolarWinds Platform 2026.2.3 - SWIS error "An item with the key 'Local.Orion.Cloud.Azure.StorageAccount' already exists"

9/28/2026 3:21 AM

9/28/2026 6:57 AM

After the upgrade, the Configuration Wizard stops at 85.4% during the Services configuration step. Running the wizard again produces the same result. The web console does not load.

The Configuration Wizard shows the following failed tasks:

Verifying that the SolarWinds® Orion Module Engine is available    FAILED
Verifying that the SWIS container storage is available              FAILED
Initializing OSH Installation ID                                    FAILED

The error details show:

Services configuration failed: • PlatformBridge.Info.GetOrCreateOshInstallationId failed, check fault information. Could not invoke PlatformBridge.Info.GetOrCreateOshInstallationId verb - SWIS schema is incomplete due to loading errors. • A task was canceled. • Connection to SolarWinds Information Service did not succeed. Last error: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

The SWIS log shows a schema merge error at startup:
C:\ProgramData\SolarWinds\Logs\InformationServiceV3\Orion.InformationService.log

YYYY-MM-DD HH:MM:SS,mmm [N] ERROR SolarWinds.InformationService.Core.SchemaLoader - (null) (null) Error merging schemas files. Returning empty Schema. System.ArgumentException: An item with the key 'Local.Orion.Cloud.Azure.StorageAccount' already exists at SolarWinds.Data.Entity.SchemaModel.SchemaElementDictionary`1.InsertItem(Int32 index, T item) at SolarWinds.Data.Entity.SchemaModel.SchemaMerger.Merge(Schema schema1, Schema schema2) at SolarWinds.Data.Entity.SchemaModel.SchemaFactory.MergeSchemas(IEnumerable`1 schemas, IEnumerable`1 schemaDocs) at SolarWinds.InformationService.Core.SchemaLoader.LoadSchemas(IEnumerable`1 schemaFiles, ISchemaLoaderErrorReporter errorReporter) YYYY-MM-DD HH:MM:SS,mmm [N] INFO SolarWinds.InformationService.Core.SchemaLoader - (null) (null) Loaded schema files with 1 errors

Because the schema is empty, other SWIS components fail after the merge error:

ERROR SolarWinds.Data.Providers.Orion.DynamicServicesHost - (null) (null) Failed EndInit for SolarWinds.Data.Providers.Orion.Containers.StorageUpdateService.StorageUpdateServicePlugin SolarWinds.Data.Entity.FaultySchemaException: Could perform query SELECT TOP 1 AccountID FROM Orion.Accounts - SWIS schema is incomplete due to loading errors. SolarWinds.Data.Entity.FaultySchemaException: Could not create System.Subscription entity type - SWIS schema is incomplete due to loading errors.

The StorageUpdateServicePlugin and FaultySchemaException errors are side effects of the empty schema, not the cause.

The Schemas folder contains both of the following file pairs:

• CloudAzureBlobStorageSchema.xml and CloudAzureBlobStorageSchema.Local.xml

• CloudAzureStorageAccountSchema.xml and CloudAzureStorageAccountSchema.Local.xml

Both pairs define Orion.Cloud.Azure.StorageAccount and Orion.Cloud.Azure.StorageAccountStatistics, along with their Local.* versions.

This issue has been seen when upgrading from 2026.1.x to 2026.2.3 with the offline installer. Other upgrade paths to 2026.2.x may also be affected.

Hybrid Cloud Observability

In 2026.2, Azure monitoring changed from "Blob Storage" to "Storage Account", and the SWIS schema for these entities moved to CloudAzureStorageAccountSchema.xml and CloudAzureStorageAccountSchema.Local.xml.

After the upgrade, the older CloudAzureBlobStorageSchema.xml and CloudAzureBlobStorageSchema.Local.xml files can remain in the Schemas folder. SWIS loads every schema file in that folder. Since both file pairs define the same entities, the schema merge fails with a duplicate key error and SWIS starts with an empty schema. Any service or Configuration Wizard task that depends on SWIS then fails.

SolarWinds Engineering is investigating this issue. Monitor this article or the release notes for product fixes and enhancements.

Workaround

Use the following steps on each SolarWinds Platform server where both file pairs are present. This can include the Main Polling Engine, Additional Polling Engines, Additional Web Servers, and HA standby servers.

1. Take a backup or snapshot of the server and the SolarWinds database.

2. Open SolarWinds Platform Service Manager and click Shutdown Everything.

3. Go to the Schemas folder. The default location is C:\Program Files\SolarWinds\Orion\Schemas. If SolarWinds is installed on a different drive or folder, use <InstallPath>\SolarWinds\Orion\Schemas.

4. Confirm that both file pairs are present. You can run the following command in PowerShell:

     Get-ChildItem "<InstallPath>\SolarWinds\Orion\Schemas" -Filter "CloudAzure*Storage*" | Select-Object Name, Length, LastWriteTime

   Continue only if CloudAzureBlobStorageSchema* and CloudAzureStorageAccountSchema* files are both listed.

5. Create a backup folder outside the Schemas folder, for example C:\SWBackup\Schemas.

6. Move the following files from the Schemas folder to the backup folder:

   • CloudAzureBlobStorageSchema.xml

   • CloudAzureBlobStorageSchema.Local.xml

      

   • Any matching CloudAzureBlobStorageSchema*.resx files, if present

     Do not move or delete the CloudAzureStorageAccountSchema* files or any other schema files, such as CloudSchema.xml and CloudSchema.Local.xml.

7. In Windows Services, start only SolarWinds Information Service V3.

8. Open C:\ProgramData\SolarWinds\Logs\InformationServiceV3\Orion.InformationService.log and check the most recent startup:

   • You should see Loaded schema files with 0 errors.

   • You should not see Error merging schemas files or already exists.

9. Run the Configuration Wizard again.