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

Cloning a virtual machine fails with the error: A general system error occurred: PBM error occurred during PreCloneCheckCallback (2118557)

  • 13 Ratings

Symptoms

  • Cloning a virtual machine or deploying a virtual machine from a template fails with the error:

    A general system error occurred: PBM error occurred during PreCloneCheckCallback: vmodl.fault.systemerror
  • In the C:\ProgramData\VMware\vCenterServer\logs\vmware-vpx\vpxd.log file, you see entries similar to:

    Note: In vCenter Server Appliance, this log is located at /var/log/vmware/vpxd/vpxd.log file.

    <YYYY-MM-DD>T<TIME> warning vpxd[7F22254CB700] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00007f223e0fff00, h:21, <TCP '0.0.0.0:0'>, <TCP '127.0.0.1:8190'>>, e: system:111(Connection refused)
    <YYYY-MM-DD>T<TIME> warning vpxd[7F222503A700] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00007f223f354be0, h:21, <TCP '0.0.0.0:0'>, <TCP '10.27.45.75:8190'>>, e: system:111(Connection refused)
    <YYYY-MM-DD>T<TIME> error vpxd[7F222503A700] [Originator@6876 sub=HttpConnectionPool-000057] [ConnectComplete] Connect failed to <cs p:00007f221d44ffa0, TCP:localhost:8190>; cnx: (null), error: N7Vmacore15SystemExceptionE(Connection refused)
    <YYYY-MM-DD>T<TIME> info vpxd[7F2224BD8700] [Originator@6876 sub=pbm opID=FE46CD39-0000065A-e1-5] PBMCallback: HasUserDefinedPolicies: PBM error occurred during QueryProfile: Connection refused
    <YYYY-MM-DD>T<TIME> info vpxd[7F2224BD8700] [Originator@6876 sub=pbm opID=FE46CD39-0000065A-e1-5] PBMCallback: ~PbmFunctionTracer: Leaving HasUserDefinedPolicies
    <YYYY-MM-DD>T<TIME> error vpxd[7F2224BD8700] [Originator@6876 sub=pbm opID=FE46CD39-0000065A-e1-5] PBMCallback: HandleInternalFaultMessage: PBM error occurred during PreCloneCheckCallback: vmodl.fault.SystemError
    <YYYY-MM-DD>T<TIME> info vpxd[7F2224BD8700] [Originator@6876 sub=pbm opID=FE46CD39-0000065A-e1-5] PBMCallback: ~PbmFunctionTracer: Leaving PreCloneCheckCallback
    <YYYY-MM-DD>T<TIME> error vpxd[7F2224BD8700] [Originator@6876 sub=VmProv opID=FE46CD39-0000065A-e1-5] [CallbackManager] Got exception while invoking precheck on PbmCallBack: vmodl.fault.SystemError
    -->
    --> [backtrace begin] product: VMware VirtualCenter, version: 6.0.0, build: build-2559267, tag: vpxd
    --> backtrace[00] libvmacore.so[0x003C0094]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)
    --> backtrace[01] libvmacore.so[0x001EDBA3]: Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
    --> backtrace[02] libvmacore.so[0x001988AD]: Vmacore::Throwable::Throwable(std::string const&)
    --> backtrace[03] vpxd[0x00BD070E]: Vmomi::Fault::SystemError::Exception::Exception(std::string const&)
    --> backtrace[04] vpxd[0x01799FAA]: PbmService::HandleInternalFaultMessage(Vmacore::Exception*, std::string const&, Vpx::Vmprov::Context*) const
    --> backtrace[05] vpxd[0x01792D63]
    --> backtrace[06] vpxd[0x01CDD99B]
    --> backtrace[07] vpxd[0x01D47F16]
    --> backtrace[08] vpxd[0x01D5E00D]

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

Cause

This error occurs when the Profile-Driven Storage service is not running or is not accepting connections.

Note: This service is also called Policy Based Management(PBM).

Resolution

To resolve the issue, ensure that the Profile-Driven Storage service is running.

For vCenter Server Appliance:

  1. Run this command to check the status of the service:

    service vmware-sps status

  2. Run this command to start the vmware-sps service:

    service vmware-sps start

  3. Run this command to restart the vmware-sps service:

    service vmware-sps restart
Note: For more information on starting or restarting a vCenter Server Appliance 6.x service, see Stopping, starting, or restarting VMware vCenter Server Appliance 6.x services (2109887).

For vCenter Server:

  1. Log in as an administrator to the server that is running vCenter Server.
  2. Click Start > Run, type services.msc and Click Ok.
  3. From the list of services, check the status of the Profile-Driven Storage service.

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

  • 13 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.
  • 13 Ratings
Actions
KB: