Content Library fails to Synchronize: "An error occurred: java.lang.RuntimeException: Category Application is reserved and can't be used"

Products

• VMware vCenter Server

Issue/Introduction

When initiating synchronization from Subscribed Library, it fails with “RuntimeFault.summary".

 

Content Library logs (cls.log) contains entries similar

[YYYY-MM-DDTHH:MM:SS] | ERROR    | <opID> | cls-simple-activity-22    | SimpleActivityWorker           | Exception will not be handled by activity VcspUpdateActivity (handle=UUID for a handle, entityId=UUID for an object): java.lang.RuntimeException: Category <STALE TAG> is reserved and can't be used
java.lang.RuntimeException: java.lang.RuntimeException: Category <STALE TAG> is reserved and can't be used
 at com.vmware.cl.tagging.TaggingServiceImpl.findCategoryByName(TaggingServiceImpl.java:296) ~[cls-main-1.0.0.jar:?]
 ...

Environment

VMware vSphere 7.x
VMware vSphere 8.x

Cause

The primary checks that needs to be performed in order to successfully replicate a content library between Publisher and Subscriber are as follow:

• Make sure if anything change in content library like, roles, tags are appropriate.
• Verify if recently edited tag is valid.

Resolution

Resolution:

• Remove stale tag from Content Library. 

Procedure:

1. Navigate to Menu > Content Libraries.
2. Right-click a content library and select the action that you want to perform.

• To edit the content library description, select Edit notes.
• To change the name of the content library, select Rename.
• To assign a tag to the content library, select Tags > Assign Tag.
• To remove a tag from the content library, select Tags > Remove Tag.
• To delete the content library itself, select DELETE.

Please refer for more:- https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/vsphere-virtual-machine-administration-guide-7-0.html

Note: If trying to find the tags in a vCenter via the PowerShell command get-tag fails with an error: "internal server" and the get-vmhost command works then restart the vmware-vpxd service to fix this issue.