Exporting SRM recovery plan report fails with the error: "argument type mismatch"
search cancel

Exporting SRM recovery plan report fails with the error: "argument type mismatch"

book

Article ID: 344425

calendar_today

Updated On:

Products

VMware Live Recovery VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • The following error message is recorded in Web Client logs located at:
 
VCSA
/var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log 

Windows vCenter:
C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs\vsphere_client_virgo.log 

[2017-09-29T18:51:51.400Z] [ERROR] data-service-pool-1148248 70078283 100537 200169
com.vmware.vise.data.query.impl.ServicePropertyProviderAdapter Error when fetching property {historyReportData} from property provider {class com.vmware.srm.client.planservice.reporting.RecoveryPlanHistoryReportProvider}
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.vmware.vise.data.query.impl.ServicePropertyProviderAdapter.invokeMethod(ServicePropertyProviderAdapter.java:285)
at com.vmware.vise.data.query.impl.ServicePropertyProviderAdapter.getProperties(ServicePropertyProviderAdapter.java:127)
at com.vmware.vise.data.query.impl.DataManager.getDataFromPropertyProvider(DataManager.java:1403)
at com.vmware.vise.data.query.impl.DataManager.getResultFromPropertyProvider(DataManager.java:1375)
at com.vmware.vise.data.query.impl.DataManager.access$000(DataManager.java:79)
at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:884)
at com.vmware.vise.data.query.impl.DataManager$1.call(DataManager.java:880)
at com.vmware.vise.util.concurrent.ExecutorUtil$3.call(ExecutorUtil.java:630)
at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingCallable.call(ExecutorUtil.java:984)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)


Environment

VMware vSphere Web Client 6.0.x
VMware vCenter Site Recovery Manager 6.0.x
VMware vSphere Web Client 6.5.x
VMware vCenter Site Recovery Manager 6.5.x

Cause

This issue is caused by Web Client cache.

Resolution

To resolve this issue, clean the serenity DB to clear the user cache, tomcat cache, plugin info etc.

Important: Ensure to have a valid snapshot of all the PSCs and vCenter Servers within the same SSO domain prior to performing the steps.

Note: In the case of vCenters running in Enhanced Linked Mode (federated SSO domain), the steps for clearing Web Client cache(s) have to be performed on both.
  1. ​Stop the Web Client service
service-control --stop vsphere-client
  1. Clear the user cache:
mkdir /serenity-backup/users && mv /storage/vsphere-client/SerenityDB/serenity/* /serenity-backup/users
  1. Clean tomcat cache in /usr/lib/vmware-vsphere-client/server/work/. This directory is to be completely emptied.
mkdir /serenity-backup/tomcat && mv /usr/lib/vmware-vsphere-client/server/work/* /serenity-backup/tomcat
  1. Plugin info from the vc-packages: /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
Only the relevant SRM plugins are to be (re)moved. The solution (SRM) needs to be re-registered afterwards.
  1. CmCatalog info: /etc/vmware/vsphere-client/cmCatalog
Only the relevant SRM plugins are to be (re)moved.
  1. Pickup folders: /usr/lib/vmware-virgo/server/pickup/
Only the relevant SRM plugins are to be (re)moved.
  1. Start the Web Client service
service-control --start vsphere-client
  1. Confirm Web Client functionality and consolidate the snapshots.