vIDM 3.3.7 binary download fails in Aria Suite Lifecycle with LCMMYVMWARE60024 checksum error
search cancel

vIDM 3.3.7 binary download fails in Aria Suite Lifecycle with LCMMYVMWARE60024 checksum error

book

Article ID: 314835

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • The binary download fails in the Aria Suite Lifecycle UI with:

Error Code: LCMMYVMWARE60024 LCMMYVMWARE60024 Error occurred while downloading product binaries from MyVMware account : <MyVMware account> Please check the logs for more detailsDownloaded file checksum did NOT match for file 'vIDMConnector_Bundle.zip' of 'vidm-3.3.7'.

  • The /var/log/vrlcm/vmware_vrlcm.log logfile contains an error similar to:

INFO [pool-3-thread-24] c.v.v.l.d.s.h.SourceMappingUtil - -- Version : 3.3.7
ERROR [pool-3-thread-24] c.v.v.l.d.s.h.SourceMappingUtil - -- The checksum of the zip file seems to be incorrect.
INFO [pool-3-thread-24] c.v.v.l.d.s.h.SourceMappingUtil - -- Extract directory /data/tempextract/<id>/ for source file '/data/myvmware/vidm/3.3.7/install/vIDMConnector_Bundle.zip' is deleted.
ERROR [pool-3-thread-24] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- Downloaded file checksum did NOT match for file 'vIDMConnector_Bundle.zip' of 'vidm-3.3.7'.
ERROR [pool-3-thread-24] c.v.v.l.p.c.m.t.MyVmwareDownloadTask - -- Failed :: Download VMware Aria Product Binaries com.vmware.vrealize.lcm.common.exception.userinput.myvmware.MyVmwareChecksumMismatchException: Downloaded file checksum did NOT match for file 'vIDMConnector_Bundle.zip' of 'vidm-3.3.7'.


Environment

VMware Aria Suite Lifecycle 8.x

Cause

The issue occurs due to changes in the checksums of the vidm connector bundle download files.

Resolution

For Aria Suite lifecycle version 8.10 the issue is resolved in Aria Suite lifecycle 8.10 product support pack 18.

For Aria Suite lifecycle version 8.12 the issue is resolved in Aria Suite lifecycle 8.12 patch 2.

For Aria Suite lifecycle version 8.14 the issue is resolved in Aria Suite lifecycle 8.14 patch 1.


Workaround:
There is no workaround available.