Today we had an issue where was not possible to do any Storage tasks from one of our vCenters.

Adding a Virtual Disk to a VM, we get some issues and trying to vStorage(migrate VM between Datastores) VMs get this issue:

“Relocate virtual machine “VM Name” A general system error occurred: PBM error occurred during PreMigrate-CheckCallback: No connection could be made because the target machine actively refused it Invoking prechecks.”

Troubleshooting vCenter logs (C:\ProgramData\VMware\vCenterServer\logs\vmware-vpx\vpxd.log) , found this entries regarding this issue:

“Date – Time: warning vpxd

[06004] [Originator@6876 sub=Default] Failed to connect socket; , >, e: system:10061(No connection could be made because the target machine actively refused it)
Date – Time: warning vpxd[06004] [Originator@6876 sub=Default] Failed to connect socket; , >, e: system:10061(No connection could be made because the target machine actively refused it)
Date – Time: error vpxd[06004] [Originator@6876 sub=HttpConnectionPool-000555] [ConnectComplete] Connect failed to ; cnx: (null), error: class Vmacore::SystemException(No connection could be made because the target machine actively refused it)
Date – Time: info vpxd[05856] [Originator@6876 sub=pbm opID=CF6EDCDB-00000456-a8-9b] PBMCallback: PbmFunctionTracer::~PbmFunctionTracer: Leaving PbmServiceAccess::Connect
Date – Time: error vpxd[05856] [Originator@6876 sub=pbm opID=CF6EDCDB-00000456-a8-9b] [Vpxd::StorageCommon::ServiceClientAdapter::ConnectLocked] Failed to login to service: class Vmacore::SystemException(No connection could be made because the target machine actively refused it)
Date – Time: info vpxd[05856] [Originator@6876 sub=pbm opID=CF6EDCDB-00000456-a8-9b] PBMCallback: PbmFunctionTracer::~PbmFunctionTracer: Leaving PbmService::GetPbmProfileManager
Date – Time: error vpxd[05856] [Originator@6876 sub=pbm opID=CF6EDCDB-00000456-a8-9b] PBMCallback: PbmService::HandleInternalFaultMessage: PBM error occurred during PreMigrateCheckCallback: No connection could be made because the target machine actively refused it
Date – Time: info vpxd[06336] [Originator@6876 sub=vpxLro opID=opId-afe130be-2324-491c-ac81-ca5141e17245-c1-d0] [VpxLRO] — BEGIN task-internal-35372 — ServiceInstance — vim.ServiceInstance.GetServerClock — 5252c7a2-71fc-247e-a663-e364a80da2c5(52c55130-d25c-8bf1-6457-dcf56b771aa4)
Date – Time: info vpxd[06336] [Originator@6876 sub=vpxLro opID=opId-afe130be-2324-491c-ac81-ca5141e17245-c1-d0] [VpxLRO] — FINISH task-internal-35372
Date – Time: info vpxd[05856] [Originator@6876 sub=pbm opID=CF6EDCDB-00000456-a8-9b] PBMCallback: PbmFunctionTracer::~PbmFunctionTracer: Leaving PbmCallBack::PreMigrateCheckCallback
Date – Time: error vpxd[05856] [Originator@6876 sub=VmProv opID=CF6EDCDB-00000456-a8-9b] [CallbackManager] Got exception while invoking precheck on PbmCallBack: vmodl.fault.SystemError”

Checking the logs and troubleshooting the issue, found that this is related to the vCenter service “Profile-Driven Storage”

Next step is to check this service in the vCenter(Windows version):

As we can see for some reason the service is stop. Not only that one, but others tu(not related to this issue). After a reboot to apply Windows updates, some of the services did not started(this is something very often in the vCenter Windows version).

Just start the service and try again the vStorage and any Storage tasks and you don’t see the issue anymore.

You can find here the VMware KB 2118551 related to this issue.

Hope this can help you fixing this issue.

Note: Share this article, if you think is worth sharing.