"Operation failed with error ERROR_INVALID_PARAMETER (87)" & "Failed to get vecs users and permissions" while upgrading from vCSA 6.5U2d to 6.7U1

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:
Upgrading from vCenter Server Appliance 6.5 Update 2d to 6.7  Update 1, you may experience these symptoms:

• External PSC to Embedded PSC convergence fails
• In the %temp%\vcsaCliInstaller-<date-time>-<id>\workflow_<id>\converge\converge_mgmt.log file, you see entries similar to:

2018-10-18T16:45:03.92Z INFO converge Store all vecs certificates.
2018-10-18T16:45:03.386Z ERROR converge Failed to get vecs users and permissions. Error: {
    "detail": [
        {
            "translatable": "An error occurred while invoking external command : '%(0)s'",
            "args": [
                "Command: ['/usr/lib/vmware-vmafd/bin/vecs-cli', 'entry', 'getcert', '--store', 'APPLMGMT_PASSWORD', '--alias', 'location_password_default', '--output', '/root/velma/old_certs/APPLMGMT_PASSWORD.crt']\nStderr: Error: No certificates were found for entry [location_password_default] of type [Secret Key].\nvecs-cli failed. Error 87: Operation failed with error ERROR_INVALID_PARAMETER (87) \n"
            ],
            "localized": "An error occurred while invoking external command : 'Command: ['/usr/lib/vmware-vmafd/bin/vecs-cli', 'entry', 'getcert', '--store', 'APPLMGMT_PASSWORD', '--alias', 'location_password_default', '--output', '/root/velma/old_certs/APPLMGMT_PASSWORD.crt']\nStderr: Error: No certificates were found for entry [location_password_default] of type [Secret Key].\nvecs-cli failed. Error 87: Operation failed with error ERROR_INVALID_PARAMETER (87) \n'",
            "id": "install.ciscommon.command.errinvoke"
        }
    ],
    "componentKey": null,
    "problemId": null,
    "resolution": null
}

Environment

VMware vCenter Server Appliance 6.7.x
VMware vCenter Server Appliance 6.5.x

Cause

This issue occurs when a backup schedule is defined.

Resolution

This issue is resolved in vCenter Server 6.7 U2, click here to download.

Workaround:
Workaround for this issue:

1. Log into the vCenter Server Appliance Management Interface https://vcenter-fqdn:5480
2. Navigate to the Backup view.
3. Search the Backup Schedule and click Delete to delete the current backup schedule.
4. Attempt the convergence process again.
5. Once the convergence is complete, re-create the backup schedule. For more information on creating a backup schedule, see Schedule a File-Based Backup.