1 Reply Latest reply on Oct 17, 2019 2:20 PM by rmav01

    Bulk Import Fails -- Error processing [RegisterVM]. The machine cannot be found.

    rmav01 Enthusiast

      Hello all,

       

      I am currently migrating a series of machines into a newly created vRealize Automation 7.6 environment, and am seeing the following error on the vSphere agent logs when attempting to bulk import a particular device:

       

      Error processing [RegisterVM], error details:

      System.NullReferenceException: The machine 'vm01' cannot be found.

         at DynamicOps.Vrm.Agent.vSphere.VSphereRegisterMachineRequest.RegisterVirtualMachine()

         at DynamicOps.Vrm.Agent.vSphere.VSphereHypervisorServiceProvider.RegisterMachine(VSphereVirtualMachine machine)

         at DynamicOps.Vrm.Agent.BaseHypervisorAgent`3.RegisterMachine(WorkItem workItem, PropertyBagHelper propertyBagHelper)

         at DynamicOps.Vrm.Agent.BaseHypervisorAgent`3.ProcessWorkitem(WorkItem workItem, String task, PropertyBagHelper propertyBag)

         at DynamicOps.Vrm.Agent.vSphere.VSphereAgentService.ProcessWorkitem(WorkItem workItem, String task, PropertyBagHelper propertyBag)

         at DynamicOps.Vrm.Agent.BaseAgent.ProcessWorkitem(WorkItem workItem)

       

      The odd part about this is that in my bulk import list, this particular machine has a partner node that is on the same vLAN, host, storage, etc., just with a different IP address. The partner imported with no problem, along with the handful of other machines that I imported with the same blueprint.The blueprint itself is generic and one component in length. Event broker is turned off and I'm able to see this particular machine when generating an export of unmanaged machines for this particular endpoint. After the bulk import processes, the job returns as 'completed.' Its in the monitoring logs that I see the error above and the Audit logs that I see it die during the Register Virtual Machine phase.

       

      Has anyone run into this before? I've checked that there is no allocation conflicts from the [vra].[dbo].[StaticIPvAddress] table. I can ping/nslookup the target just fine from the agent machine, and I can logon and see the box with the service account we are leveraging with the agent.