Adding a new virtual server to an existing on-demand load balancer in a deployment fails
search cancel

Adding a new virtual server to an existing on-demand load balancer in a deployment fails


Article ID: 342463


Updated On:


VMware Aria Suite


  • Reconfiguring an existing load balancer while adding a new load balancer causes a duplicate ports error.
  • In the catalina.out log file, you see entries similar to:

    Error making REST call: [[LoadBalancer] There are duplicate ports


VMware vRealize Automation 7.2.x
VMware vRealize Automation 6.x
VMware vRealize Automation Desktop 6.2
VMware vRealize Automation Desktop 6.2.x
VMware vRealize Automation 7.1.x
VMware vRealize Automation 7.3.x
VMware vRealize Automation 7.4.x
VMware vRealize Automation 7.x
VMware vRealize Automation 7.0.x
VMware vRealize Automation 6.2
VMware vRealize Automation 6.2.x


This issue occurs due to a problem with validating existing values.


This issue is resolved in VMware vRealize Automation 7.4, available at VMware Downloads.

To work around this issue, perform these steps (depending on if the environment was upgraded to 7.3 or is new):

For upgraded deployments:

To resolve this issue, reconfigure the load balancer and edit a setting on any of the Virtual Servers, which corrects the issue of the default setting storage from previous versions.

The workaround can be performed preventatively on load balancers upgraded from previous versions or as a corrective measure on load balancers that have experienced the failure.

For all deployments:

For upgraded load balancers and load balancers deployed in 7.3, do not edit a virtual server and add a virtual server in the same request. Performing the edit action and the add action in separate requests will prevent the issue.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box in the Actions box.