• An offline migration of a virtual machine, vMotion, or Storage vMotion fails with the error:
  
  
• pbm.fault.PBMFault.summary
• A general system error occured: Invalid response code 503: service unavailable
  
  
• In the vpxd.log file, you see entries similar to:
  
  
• YYYY-MM-DD TIME [7F9E4821F700 error 'VmProv' opID=E679B8A1-00009372-4e-93] [CallbackManager] Got exception while invoking precheck on PbmCallBack: Invalid response code: 503 Service Unavailable
  
  --> backtrace[00] rip 00007f9e54bdafa4 Vmacore::System::Stacktrace::CaptureWork(unsigned int)
  mem> YYYY-MM-DD TIME [7F9E4821F700 info 'Default' opID=E679B8A1-00009372-4e-93] [VpxLRO] -- ERROR task-internal-15041259 -- -- VmprovWorkflow: vmodl.fault.SystemError:
  mem> --> Result:
  mem> --> (vmodl.fault.SystemError) {
  mem> --> dynamicType = <unset>,
  mem> --> faultCause = (vmodl.MethodFault) null,
  mem> --> reason = "Invalid response code: 503 Service Unavailable",
  mem> --> msg = "",
  mem> --> }
  mem> --> Args:
  
  
• <YYYY-MM-DD>T<time> [11208 error 'VmProv' opID=62adac7c-56] [CallbackManager] Got exception while invoking precheck on PbmCallBack: pbm.fault.PBMFault
  <YYYY-MM-DD>T<time> [11208 error 'commonvpxLro' opID=62adac7c-56] [VpxLRO] Unexpected Exception: pbm.fault.PBMFault
  <YYYY-MM-DD>T<time> [11208 info 'Default' opID=62adac7c-56] [VpxLRO] -- ERROR task-internal-180505 -- -- VmprovWorkflow: pbm.fault.PBMFault:
  --> (pbm.fault.PBMFault) {
  <YYYY-MM-DD>T<time> [11208 error 'Default' opID=62adac7c] (Log recursion level 2) pbm.fault.PBMFault
  <YYYY-MM-DD>T<time>[11208 error 'commonvpxLro' opID=62adac7c-56] [VpxLRO] Unexpected Exception: pbm.fault.PBMFault
  <YYYY-MM-DD>T<time> [11208 info 'Default' opID=62adac7c] [VpxLRO] -- ERROR task-13745 -- vm-133 -- vim.VirtualMachine.clone: pbm.fault.PBMFault:
  --> (pbm.fault.PBMFault)
  </time></time></time></time></time></time>
  Note: For more information on the location of vCenter Server and vCenter Server Appliance log file locations, see Location of vCenter Server log files (1021804).

• In a Windows vCenter Server 5.5 the C:/ProgramData/VMware/Infrastructure/Profile-Driven Storage/Logs/\java_pid####.hprof consumes a large amount of disk space for the Profile-Driven Storage Service.

• In the wrapper.log file for the Inventory Service or Profile-Driven Storage Service, you see entries similar to:
  
  INFO | jvm 3 | 2015/02/11 11:37:59 | java.lang.OutOfMemoryError: Java heap space
  INFO | jvm 3 | 2015/02/11 11:37:59 | Dumping heap to C:/ProgramData/VMware/Infrastructure/Profile-Driven Storage/Logs/\java_pid####.hprof ...
  
  Or
  
  INFO | jvm 4 | 2015/02/11 13:36:00 | java.lang.OutOfMemoryError: GC overhead limit exceeded
  INFO | jvm 4 | 2015/02/11 13:36:00 | Dumping heap to C:/ProgramData/VMware/Infrastructure/Profile-Driven Storage/Logs/\java_pid####.hprof ...
  
  
• Location of vSphere Profile-Driven Storage log files (2056646)
• Location of vCenter Inventory Service 4.x and 5.x log files (2056632)
  

Note: This Knowledge Base article is applicable only if the wrapper.log file includes the java.lang.OutOfMemoryError error.

1. Log in to vCenter Server Appliance administration interface (VAMI) URL:
   
   https://vCenter_Server_FQDN\IP:5480
   
   
2. Click the Services tab.
3. Change the Inventory Size to Medium or Large, depending on your environment.
   
   Note: The system memory may need to be increased when changing this setting. For more information on environment sizing, see the Configure Inventory Size for the VMware vCenter Server Appliance section of the Configuring Hosts and vCenter Server guide.
   
   
4. Restart the VMware Profile-Driven Storage Service and VMware Inventory Service. For more information, see Stopping, starting, or restarting vCenter Server Appliance services (2054085).