Tag Category Creation and Tag Operations Fail with SystemError: "Invalid fault"

Products

• VMware vCenter Server
• VMware vCenter Server 6.0

Issue/Introduction

When attempting to create, edit, or delete tags or tag categories in the vSphere Client, the following error may occur:

• UI Error:

(vmodl.fault.SystemError) { faultCause = null, faultMessage = null, reason = Invalid fault }

• /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log:

[ERROR] http-bio-5090-exec-16 70000214 100104 200001 com.vmware.vsphere.client.tagging.impl.TagMutationProvider  
An error occurred while creating tags  
java.util.concurrent.ExecutionException: (vmodl.fault.SystemError) { faultCause = null, faultMessage = null, reason = Invalid fault }
[ERROR] http-bio-9090-exec-1 70003421 100253 200210 com.vmware.vsphere.client.tagging.impl.TagMutationProvider  
An error occurred while creating tags java.util.concurrent.ExecutionException

• /var/log/vmware/vmdird/vmdird-syslog.log:

err vmdird t@140070115845888: UpdateServerObject: InternalModifyEntry failed. Error code: 53, Error string: Server in read-only mode

Cause

This issue occurs when the vmdir service (VMware Directory Service) is in read-only mode or if the vmdir database is full. In either case, the service is unable to process updates to directory objects, which are required for tag operations such as creating, editing, or deleting tags and tag categories.

Resolution

Note: Take a snapshot of the vCenter Server Appliance or PSC before proceeding.

1. Establish SSH Connection:

• Log in to the PSC or VCSA via SSH using an account with appropriate privileges.

2. Increase Maximum VMDIR Database Size:

• Execute the following command to increase the maximum allowable size of the VMDIR database to 2048 MB:
  /opt/likewise/bin/lwregshell add_value "[HKEY_THIS_MACHINE\Services\vmdir\Parameters]" "MaximumDbSizeMb" REG_DWORD 2048
  
  
• Verify the updated value using the following command:
  /opt/likewise/bin/lwregshell list_values "[HKEY_THIS_MACHINE\Services\vmdir\Parameters]" | grep MaximumDbSizeMb
  
  
• Confirm that the output is similar to the following, indicating the successful update:
  + "MaximumDbSizeMb" REG_DWORD 0x00000800 (2048)

3. Set VMDIR State to NORMAL:

• Reset the VMDIR service state to "NORMAL" using the following command:
  /usr/lib/vmware-vmafd/bin/dir-cli state set --state NORMAL --login administrator --server-name localhost

4. Restart the VMDIR Service:

• Restart the VMDIR service using the following commands:
  service-control --stop vmdird
  service-control --start vmdird

5. Verify Functionality:

• After the VMDIR service has restarted and its state is confirmed as "NORMAL," attempt to create tag categories and perform tag operations to verify that the issue has been resolved.

Note: If the vmdir state does not stay in NORMAL and flips back to 'Read-Only' please contact Broadcom support for further assistance.