VMware vRealize Orchestrator fails to run any workflow to vCenter Server with error Java Runtime Exception: vim.fault.InvalidLogin
search cancel

VMware vRealize Orchestrator fails to run any workflow to vCenter Server with error Java Runtime Exception: vim.fault.InvalidLogin

book

Article ID: 345987

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

To address the workflow failures caused due to the problems related to the vCenter Plug-in to perform tasks on the vCenter using VRO workflows.


Symptoms:

When running a VRO workflow to perform a task on the vCenter, we are getting a Java Runtime Exception: (vim.fault.InvalidLogin) {faultCause =null, faultMessage = null} followed by the Workflow specific error such as (Workflow: Remove old snapshots- no user interaction /Check host and VC time (item14)#2).


Environment

VMware vRealize Orchestrator 8.x

Cause

This error can occur when the authentication token saved in VRO has expired, typically due to a change in the credentials of the user used to configure vCenter in VRO.

Resolution

We need to re-run the vCenter Workflow:

  1. Log in to the vRealize Orchestrator Client as an administrator.
  2. Navigate to Library > Workflows and enter the vCenter and configuration tags in the workflow search box.
  3. Locate the Update a vCenter Server instance workflow and click Run.

If you are familiar with the above workflow, kindly run the workflow with the appropriate inputs. Else, if you need assistance with the steps, kindly follow the below steps:

  1. Retain the default location of the SDK to use to connect to your vCenter Server instance.
  2. Select whether you want to ignore certificate warnings for the vCenter Server instances that you want to add.
  3. By choosing to ignore certificate warnings, the certificate of the vCenter Server instance is silently accepted, and it is then added to the trusted store.
  4. Select the method for managing user access on the vCenter Server system, on the "Set connection properties" tab.
    1. Share a unique session:
      • If vRealize Orchestrator and vCenter Server have different PSCs for authentication, follow these steps.
      • Enter valid user credentials in the User name and Password text boxes to establish a single connection to the vCenter Server host.
      • The user must have privileges to manage vCenter Server extensions and custom-defined privileges.
      • vRealize Orchestrator uses these credentials to monitor the VirtualCenter Web service and run system workflows.
    2. Session per user:
      • Select if vRealize Orchestrator and your vCenter Server use the same PSC as an authentication provider.
      • Creates a session to vCenter Server.
      • Note: This action might rapidly use CPU, memory, and bandwidth. You must specify the user domain name only when you select to use a shared session.
        • Note: Fill this text box if Session per user is selected.

image.png

 


Additional Information

Impact/Risks:

All workflows utilizing the vCenter plug-in or vCenter workflows will fail unless resolved.