The fact that Refresh_11/29/2025 SUCCESS and Refresh_12/06/2025 FAILURE indicates:
DRM was functioning correctly before.
The failure is not due to installation corruption but likely due to catalog data or repository state changes between those dates not a systemic failure.
The NullPointerException (getAllComponents() is null) means the comparison report object is empty during refresh.
This usually happens when:
The catalog downloaded on 12/06 was incomplete or corrupted.
The repository being refreshed has no valid components to compare (e.g., empty or misconfigured repository).
Permissions or storage path issues prevented DRM from writing catalog data.
Recommended troubleshooting steps
From User Guide below: Page 19–20 (Configure Catalog Settings) and Page 25–26 (Refresh Repository):
Thanks for your quick reply. Wev'e tried every step from the troubleshooting guide but nothing worked. Out of spite i've made a new repo, again, and this time the refresh/export worked.
It happend a lot, is there any guidelines about why we have to create a new repo everytime to fix the failed refresh ?
DELL-Erman O
Moderator
•
2984 Posts
•
14874 Points
0
0
Posted December 16th, 2025 14:38
Hi, it may related with repo metadata and catalog schema structure changes. I think to reduce stale metadata remove unused repos periodically.
DELL-Erman O
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!