"Unable to process the request due to bad parameter 'orgId' -> 'null'." error when configuring replications in Cloud Director Availability 4.x
search cancel

"Unable to process the request due to bad parameter 'orgId' -> 'null'." error when configuring replications in Cloud Director Availability 4.x

book

Article ID: 315004

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:

  • Configuring new replications via the Cloud Director Availability plug-in in Cloud Director fail with the error:
Unable to process the request due to bad parameter 'orgId' -> 'null'.
  • In the /opt/vmware/h4/cloud/log/cloud.log file on the Cloud Replication Management Appliance, you see entries similar to:
2021-02-01 07:59:20.252 ERROR - [UI-9fff3ca6-####-####-####-########f26-z5] [https-jsse-nio-8443-exec-2] c.v.h.c.c.error.ExceptionAdvisorBase   : A GET request from System@SITENAME [IP_ADDRESS] to /inventory/vapps?offset=0&limit=20&site=SITENAME failed.

com.vmware.h4.api.error.exceptions.BadUserInput: Unable to process the request due to bad parameter 'orgId' -> 'null'.
    at com.vmware.h4.cloud.vcloud.inventory.LocalVcloudInventoryService.listApps(LocalVcloudInventoryService.java:236)
    at com.vmware.h4.cloud.controller.InventoryController.browseVapps(InventoryController.java:103)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
    at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
    at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105)
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:878)
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:792)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Director Availability 4.x

Cause

This issue can occur when the Cloud Director Availability plug-in for Cloud Director has not been updated when upgrading to a new version of Cloud Director Availability.

Resolution

To resolve this issue, repair the Cloud Director connection in Cloud Director Availability to push the latest plug-in.

For information on how to do this, see the Post-Upgrade Configuration in the Cloud section of the Cloud Director Availability documentation.