Baking Clouds Ltd

Baking Clouds provide tailored IT consultancy services to small and medium-sized companies; we cover all aspects of IT without any hidden costs.

Usage meter 3.6.1 Hourly Collection Errors Detected

After deploying VMware vCloud Usage Meter 3.6.1 “collection return error” events notifications were received every hour for vCenter Appliance 6.0 while vCenter Appliance 6.5 completes successfully.

vCenter Appliance 6.0 collection was completing successfully with vCloud Usage Meter 3.5 but upgrade of Usage meter is needed to support latest VMware products version.

2018-05-07 14:05:27,324 ERROR [Collector vclab.local] vc.VCenterCollector: com.vmware.pbm.RuntimeFaultFaultMsg: 
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:135)
	at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238)
	at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:189)
	at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:276)
	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:104)
	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77)
	at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147)
	at com.sun.proxy.$Proxy79.pbmQueryProfile(Unknown Source)
	at com.vmware.cloud.usgmtr.collect.vc.VCenterConnector.accessStoragePolicyServer(VCenterConnector.scala:177)
	at com.vmware.cloud.usgmtr.collect.vc.VCenterConnector.logIn(VCenterConnector.scala:126)
	at com.vmware.cloud.usgmtr.collect.vc.VCenterConnector.logIn(VCenterConnector.scala:101)
	at com.vmware.cloud.usgmtr.collect.vc.VCenterCollector$.com$vmware$cloud$usgmtr$collect$vc$VCenterCollector$processVC(VCenterCollector.scala:85)
	at com.vmware.cloud.usgmtr.collect.vc.VCenterCollector$anonfun$1$anonfun$apply$1.apply(VCenterCollector.scala:47)
	at com.vmware.cloud.usgmtr.collect.vc.VCenterCollector$anonfun$1$anonfun$apply$1.apply(VCenterCollector.scala:36)
	at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
	at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Workaround

To work around this issue, do the following:

  1. Login in to the vSphere Web Client.
  2. Navigate to Administration > Roles
  3. Click the Create role button.
  4. Type a name for the new role.
  5. Select the following permission: Profile-driven storage > Profile-driven storage view
  6. Assign the new role to the account used for vCloud Usage Meter
Usage meter 3.6.1 Hourly Collection Errors Detected
Scroll to top