VMware vRealize Orchestrator 5.1 login to vCenter Server fails with the error: Unexpected status code: 400
search cancel

VMware vRealize Orchestrator 5.1 login to vCenter Server fails with the error: Unexpected status code: 400

book

Article ID: 328259

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
    • You cannot configure the vRealize Orchestrator (formerly known as vCenter Orchestrator) Plug-In for vCenter Server to authenticate with vCenter Server via Single Sign-On (SSO), even though the ID and password combination is a member of the vCenter Server Administrators group and is an SSO Admin.
    • You cannot expand the vCenter Server inventory when you log in to the vRealize Orchestrator client.
    • In the Orchestrator log, you see messages similar to:

      at java.lang.Thread.run(Thread.java:662)
      2012-10-24 14:59:11.107-0400 ERROR [VimSession] login()-->
      com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 400
      at com.vmware.vim.vmomi.client.common.Response$Status.getStatus(Response.java:59)
      at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:126)
      at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send
      (HttpProtocolBindingImpl.java:98)
      at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$
      CallExecutor.sendCall(MethodInvocationHandlerImpl.java:526)
      at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$
      CallExecutor.executeCall(MethodInvocationHandlerImpl.java:507)
      at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall
      (MethodInvocationHandlerImpl.java:295)
      at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeFetch
      (MethodInvocationHandlerImpl.java:287)
      at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke
      (MethodInvocationHandlerImpl.java:165)
      at $Proxy291.getContent(Unknown Source)


    Cause

    The most likely cause of this issue is when vCenter Server has been installed using an HTTP port other than 80. Versions of Orchestrator earlier than 5.1.1 are hard coded to use port 80 for HTTP.

    This can also be caused by an issue in the vRealize Orchestrator Plug-In for vCenter Server.

    Resolution

    This issue is resolved in vRealize Orchestrator (formerly known as vCenter Orchestrator) 5.1.1, available at VMware Downloads.

    The vRealize Orchestrator Plug-In for vCenter Server in 5.1.0 builds 455 and later may also address this issue. For more information, contact VMware Technical Support.

    If vCenter Server was installed to use an HTTP port other than 80, you must either upgrade the Orchestrator Plug-In for vCenter Server to 5.1.1 or install or upgrade to vRealize Orchestrator 5.1.1.

    To configure the vRealize Orchestrator Plug-In for vCenter Server to use a custom port for HTTP:

    1. In the vRealize Orchestrator 5.1.1 configuration interface, create a vCenter Server plug-in connection in the existing config screen, and set it to per user with no user ID or password. The plug-in is shown as green.
    2. Click Startup Options and select Restart the vRealize Orchestrator configuration server. This forces you to log in to the vRealize Orchestrator configuration page again.
    3. Click Startup Options and click Restart Service.
    4. Open the Orchestrator client. This can be installed locally or via the Orchestrator start page (located at http://IP_of_vRealize_Orchestrator).
    5. Click Workflows. On 5.1.1, this is the blue icon when in the Run mode.
    6. Expand the Library > vCenter > Configuration folder.
    7. Right-click the workflow named Add a vCenter Server Instance and click Start workflow.
    8. Enter the IP or FQDN, the default SSL port, and the default for the other entries on the first page.
    9. Click Next.
    10. On the Set the Connection properties page, you see this message:

      Do you want to use a session per user method to manage user access to the vCenter Server system? If you select No, Orchestrator will create only one connection to vCenter Server (the method is share a unique session)

    11. Click No.
    12. Enter the HTTP port of the vCenter Server instance.
    13. Enter a valid username/password combination.

      Note: This account must be in the vRealize Orchestrator administrators group as defined in the vRealize Orchestrator admin Authentication page, and also an administrator of the target vCenter Server instance.

    14. Click Submit.
    15. After the workflow runs successfully, you see two connections in the vRealize Orchestrator configuration page for the vCenter Server plug-in. You may delete the first or original connection. Alternately, you may use the Update a vCenter Server instance workflow.


    Additional Information



    O login do VMware vRealize Orchestrator 5.1 no vCenter Server falha com o erro: Unexpected status code: 400
    El inicio de sesiĆ³n de VMware vRealize Orchestrator 5.1 en vCenter Server arroja el siguiente error: Unexpected status code: 400