Search the VMware Knowledge Base (KB)
View by Article ID

vMotion of a virtual machine fails with the error: PBM error occurred during PreMigrateCheckCallback (2118551)

  • 19 Ratings
Language Editions

Symptoms

  • vMotion of a virtual machine fails with the error:
A general system error occurred: PBM error occurred during PreMigrateCheckCallback: No connection could be made because the target machine actively refused it.
  • No migration logs for vMotion task found in the source and destination host.
  • In the C:\ProgramData\VMware\vCenterServer\logs\vmware-vpx\vpxd.log file, you see entries similar to:
<YYYY-MM-DD>T<TIME> warning vpxd[11728] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x000000002c3835b8, h:22928, <TCP '0.0.0.0:0'>, <TCP '[::1]:8190'>>, e: system:10061(No connection could be made because the target machine actively refused it)
<YYYY-MM-DD>T<TIME> error vpxd[11728] [Originator@6876 sub=HttpConnectionPool-009013] [ConnectComplete] Connect failed to <cs p:000000003ab423c0, TCP:localhost:8190>; cnx: (null), error: class Vmacore::SystemException(No connection could be made because the target machine actively refused it)
<YYYY-MM-DD>T<TIME> info vpxd[11764] [Originator@6876 sub=pbm opID=task-internal-2-1473431e-c0] PBMCallback: PbmFunctionTracer::~PbmFunctionTracer: Leaving PbmServiceAccess::Connect
<YYYY-MM-DD>T<TIME> error vpxd[11764] [Originator@6876 sub=pbm opID=task-internal-2-1473431e-c0] [Vpxd::StorageCommon::ServiceClientAdapter::ConnectLocked] Failed to login to service: class Vmacore::SystemException(No connection could be made because the target machine actively refused it)
<YYYY-MM-DD>T<TIME> info vpxd[11764] [Originator@6876 sub=pbm opID=task-internal-2-1473431e-c0] PBMCallback: PbmFunctionTracer::~PbmFunctionTracer: Leaving PbmService::GetPbmProfileManager
<YYYY-MM-DD>T<TIME> error vpxd[11764] [Originator@6876 sub=pbm opID=task-internal-2-1473431e-c0] PBMCallback: PbmService::HandleExternalFaultMessage: PBM error occurred during QueryAllAssociatedProfiles: No connection could be made because the target machine actively refused it

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

Purpose

To resolve the PBM error occurred during PreMigrateCheckCallback error when attempting to vMotion a virtual machine, ensure that the Profile-Driven Storage service is running.

Cause

This issue occurs when the Profile-Driven Storage service is not running.

Resolution

To resolve the issue, ensure that the Profile-Driven Storage service is running. For more information, see Stopping, starting, or restarting VMware vCenter Server Appliance 6.x services (2109887)

Additional Information

For more information, see Preconfigured vSphere Alarms.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 19 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 19 Ratings
Actions
KB: