Proxy Agent Signature Verification Failed - Troubleshooting Guide

Proxy Agent Signature Verification Failed

KB ID: 116006
Issue:
The error message "Proxy Agent Signature Verification Failed" is encountered, typically when the target machine has a BDRSuite Integration Service (BIS) agent installed, which has been pushed by a different backup server or BDRSuite Client. This error arises due to a mismatch in the Unique Identification Number (UUID) used for communication between the BDRSuite Backup Server or BDRSuite Client and the BIS agent on the target host. Each BIS agent possesses a unique UUID, and when there is a UUID mismatch, subsequent backups fail with the "Proxy Agent Signature Verification Failed" error.
Solution:
Before proceeding with the solutions, ensure the following:
1. The target host is not added to another BDRSuite server or BDRSuite client.
2. The VIS agent is not being used by another BDRSuite server or BDRSuite client.
If the target host is already added to another BDRSuite server or BDRSuite client, you have two options:
Option 1: Continue using the existing BDRSuite server or BDRSuite client:
a) Remove the host entry from the BDRSuite server or BDRSuite client user interface.
b) Uninstall the VIS agent from the target host using these steps:
  1. Go to the Control Panel.
  2. Select "Programs and Features" and click "Programs."
  3. Locate "BDRSuiteIntegrationService" and click "Uninstall."
Option 2: If you still want to configure backups from the current BDR server or BDRSuite client:
a) Remove the host entry from the BDR server or BDRSuite client user interface.
b) Uninstall the VIS agent from the target host using the steps mentioned above.
c) Once these steps are completed, re-add the target host to the backup server or BDRSuite client and configure the backups.
By following these steps, you can resolve the "Proxy Agent Signature Verification Failed" error and ensure that backups are configured correctly with matching UUIDs between the VIS agent and the BDR server or BDRSuite client.
    • Related Articles

    • Backup Proxy Has Been Stopped

      KB ID: 115122 Cause: 1. If the machine in which VMware Proxy agent is installed is rebooted/powered off. 2. If the service for the Proxy agent is stopped in the remote machine. 3. If the status of the proxy service cannot be checked because of any ...
    • AppAware Verification Failed - Alerts

      KB ID: 104058 Description: This Knowledge Base article addresses the AppAware alerts related to error code 104058. These alerts indicate issues with application-aware processing during backup operations. Each alert is associated with a specific ...
    • Proceed Ack Failed

      KB ID: 115096 Cause: The reported error, "Proceed Ack Failed," occurs during backup configuration when there is a network drop, improper network connectivity, network timeout, or if the agent doesn't receive the initial handshake acknowledgment from ...
    • Incompatibility of 32-bit Windows System as VMware Backup Proxy

      KB ID: 117054 Issue: When attempting to add a 32-bit architecture Windows machine as a Proxy agent (specifically for VMware Proxy), the user interface (UI) displays the message "Backup Proxy for VMware is not supported for this Windows System." ...
    • Resolving Agent Installation Failure: Port 42005 Already in Use

      KB ID: 117014 Issue: The error message "Agent installation in the target host is failed since 42005 port is already in use" is encountered during agent installation on the target host. Cause: This error occurs when the VIS Agent Port (port 42005) is ...