"Error: ID DummySubscription of resource type [com.vmware.content.library.Subscriptions] not found in VMware vCenter Server".

Products

• VMware vCenter Server

Issue/Introduction

• Subscribed Content Library fails to synchronize with a publisher.
• The "Publish" button may be greyed out or synchronization tasks fail immediately.
• On the subscriber vCenter shows the following error on /var/log/vmware/content-library/cls.log:

DEBUG q-452067:h5ui-getProperties:urn:vapi:com.vmware.content.Library:89f75fe5-f844-###:f0fa7528-####:ContentLibrarySpecificCapabilitiesPropertyProviderAdapter:2199288-4no34-h5:70456787 | tomcat-http-42 | ApiMethodSkeleton              | Method com.vmware.cont    |ent.library.subscriptions.get threw an exception
com.vmware.vapi.std.errors.NotFound: NotFound (com.vmware.vapi.std.errors.not_found) => {
 messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
 id = com.vmware.vdcs.cls-main.validate_id_not_found,
 defaultMessage = ID DummySubscription of resource type [com.vmware.content.library.Subscriptions] not found.,
 args = [DummySubscription, com.vmware.content.library.Subscriptions],

Environment

vCenter 8.x

Cause

This issue occurs when the Content Library metadata becomes orphaned or references a non-existent subscription ID. This is most common after a vCenter Server has been recreated, restored from a backup that predates the library creation, or when there is a mismatch between the vCenter database (VCDB) and the Content Library service's internal state. The service attempts to look up a subscription record named "DummySubscription" which does not exist in the current database.

Resolution

To resolve this issue, the stale metadata must be purged by recreating the subscribed library.

1. Delete the affected library at Subscriber end:
   • Log in to the vSphere Client.
   • Navigate to Content Libraries.
   • Right-click the affected Subscribed Library and select Delete. (Note: This only deletes the metadata and local copies, the source templates remain safe on the publisher).
2. Generate a New Subscription URL:
   • Log in to the Publisher vCenter Server.
   • Navigate to the Published Content Library.
   • Copy the Subscription URL.
3. Recreate the Subscribed Library:
   • Log in to the Subscriber vCenter Server.
   • Create a new Subscribed Content Library using the fresh URL from the publisher.
4. Restart Content Library Service:
   • To ensure all stale cache is cleared, restart the service via SSH as root:
     

     service-control --restart vmware-content-library

5. Verify Sync:
   • Initiate a manual synchronization 

If the issue persists after following the steps mentioned, please contact Broadcom Technical Support for further assistance.

Reference: Creating and managing Broadcom cases

Additional Information

The Subscriber vCenter would show a similar error on /var/log/vmware/content-library/cls.log

ContentLibrarySpecificCapabilitiesPropertyProviderAdapter:7048910-4o66a-h5:##### | tomcat-http-37 | ApiMethodSkeleton | Method implementation threw a VMODL2 error com.vmware.vapi.std.errors.NotFound: NotFound (com.vmware.vapi.std.errors.not_found) => { messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => { id = com.vmware.vdcs.cls-main.validate_id_not_found, defaultMessage = ID DummySubscription of resource type [com.vmware.content.library.Subscriptions] not found., args = [DummySubscription, com.vmware.content.library.Subscriptions], params = , localized = }], data = , errorType = NOT_FOUND }