Failed to parse catalog - 4.4.0 (Build 75)

Question

Hello,

Since around 24-48 hours ago our catalogs have been failing to update and parse the catalog file:

RunningProcessing repository information.Attempting to connect to repository.Catalog downloaded successfully.Failed to parse catalog. Please delete and retry again. If issues persists, contact support.Task Failed. Completed With Errors.

There has been no environmental change to our OMEnt instances. We are not using DRM or an external source and is being retrieved directly from 'downloads.dell.com/catalog/catalog.gz'. I have tried to store the catalog.xml file locally at an NFS location also and the same error is returned.

Older paths to 'dl.dell.com' catalogs continue to work.

OMEnt version is 4.4.0 (Build 75), there have been no changes over the last 48 hours to this environment. We cannot upgrade to 4.6 yet to 'test'.

I recall something similar happened in 2025 due to a server side issue during catalog promotion. Is this something similar? Is there a location I can test with that is an older/archived catalog version to verify?

thank you.

StevenK_AU · Accepted Answer

@StevenK_AU​ Further comments from Dell Support:'...we’ve re-released the 26.05.07 catalog with the activation rules, that was affecting Broadcom NICs. You should be okay from this release onwards. However, as, and when you can, do still plan for an upgrade to OME 4.5.1 and newer.' Should be OK going forward based on this commentary from Dell.

StevenK_AU · Answer

to add to this, if I were to point to a different catalog such as the ESXi catalog (https://downloads.dell.com//catalog/ESXi_Catalog.xml.gz) this validates and parses the .xml file successfully

SToraskar · Answer

I am also facing same issue with OMEnt version is 3.10.2 (Build 13). Tried download the catalogs from downloads.dell.com/catalog/catalog.gz and use network path to add, download status is completed but result with "Unavailable"

peetteroctv · Answer

same issue here using https://downloads.dell.com/catalog/catalog.xml.gz

AM2026-WCC · Answer

Any update on when Dell is going to correct this issue?

JBaker79 · Answer

contacted support and was told to Upgrade to the latest version of OME, Still not working!  hopefully Dell fixes this soon.

DELL-Young E · Answer

Hello JBaker79, may we ask what version you upgraded to? Also could you kindly send your service tag by DM? https://www.dell.com/community/en/direct-messaging Respectfully,

josse888 · Answer

I am also facing same issue with OMEnt version is 3.10.2 (Build 13). Tried download the catalogs from downloads.dell.com/catalog/catalog.gz and use network path to add, download status is completed but result with "Unavailable"

Catalog name: catalog1

Download status: Completed

Repository Type: HTTPS

Repository Location: xxxxxxxxxxxxxxxxxxxxxxx4rFP6KsTDaoM/download/catalog.gz

Catalog File: catalog.xml
Created Date: <empty>

catalog1

Bundles	Unavailable
Version	Unavailable
Created Date	Unavailable
Last Checked	May 6, 2026 10:52:22 PM
Next Check	Unavailable
Associated Baselines

both update using "Latest component versions on Dell.com" and "network path" are fail.

Could Dell fix this catalog.gz issue for OMEnt version is 3.10.2 (Build 13)?

JBaker79 · Answer

@DELL-Young E​ This is the error we're getting:   Processing repository information. Attempting to connect to repository. Catalog downloaded successfully. Failed to parse catalog.   So it downloads the repository but it cannot parse it. Has there been any changes to the catalog recently?

PatchAndPray · Answer

@DELL-Young E​ and @JBaker79  We are having the exact same issue and there has been no environmental change to our OMEnt instance.Confirmed no Firewall restrictions to downloads.dell.com on port 443.OMEnt version: 3.10.2 (Build 13)Dell Online: downloads.dell.com/catalog/catalog.gz RunningProcessing repository information.Attempting to connect to repository.Catalog downloaded successfully.Failed to parse catalog. Please delete and retry again. If issues persists, contact support.Task Failed. Completed With Errors. @DELL-Young E​ - This is not a version issue as others have reported having the same issue after upgrading and we can confirm pointing to a different repository (downloads.dell.com/catalog/ESXi_Catalog.xml.gz) works fine.Could Dell please investigate and resolve this issue?

DELL-Young E · Answer

Hello, may I ask if you have tried version 4.6 at all? Respectfully,

StevenK_AU · Answer

@DELL-Young E​ per the commentary in the original request I cannot upgrade to 4.6 to just 'test'. There is also commentary in this thread where Dell suggested upgrade to the latest version and the issue still persisted. When checking debug logs the working esxi catalog seems to successfully validate with the .sign file and parses successfully. The standard catalog regardless of method (dell online catalog, http, https, nfs) will fail, provide an 'extract failed' message, and then have a fips_mode error associated with it: [DEBUG] 2026-05-07 09:14:11.557 [Catalina-utility-3] HttpsParameterFactoryHelper - configurationDAO is empty checking FIPS mode enabled by file system[DEBUG] 2026-05-07 09:14:11.558 [Catalina-utility-3] FIPSModeUtils - Can not get FIPS mode from file. Using Default values. Exception:java.io.FileNotFoundException: /var/etc/sysconfig/fips_mode (No such file or directory)

josse888 · Answer

@DELL-Young E​, Tested this issue with OME Version 4.5.0 (Build 34), it is working fine to add new catalog using 'Latest component versions on Dell.com'.I cannot just migrate/upgrade from OMEnt version is 3.10.2 (Build 13) to OME Version 4.5.0 (Build 34) as we need to test/PoC/certified for Version 4.5 or 4.6 first.Could Dell please investigate and resolve this issue for 3.10.2 (Build 13) as we need time to upgrade?Thanks in advance.

DELL-Young E · Answer

Hello, our recommendation is to update to OME 4.5.1 or 4.6.0 at the earliest as older versions of OME carries an older library of the Dell Update Catalog (DUC) which can't parse the newly added attributes for DUPs that require a cold reboot. OME 4.5.x and newer carry a newer DUC library that can parse this. We will have a KB article published very soon which explains this in further detail.

Respectfully,

StevenK_AU · Answer

That came a bit out of nowhere. Not all environments can blindly update their hardware management software at the drop of a hat. Is there any consideration to revert this and give a period for updates to be scheduled and performed?

Or could a separate catalogue location be provided for 4.4 and lower as an interim solution?

Would using DRM get around this recommendation?

Dell OpenManage Enterprise

Failed to parse catalog - 4.4.0 (Build 75)

catalog1

Was this post helpful?