Failed to perform fix-up operation on migrated VM. A specified parameter was not correct: fileType

Products

• VMware HCX

Issue/Introduction

HCX OS Assisted Migration (OSAM) for a machine fails at fix-up with the following error message "Failed to perform fix-up operation on migrated VM. A specified parameter was not correct: fileType".

• HCX Connector/Manager log shows the following in /common/logs/admin/app.log:
  
  

  2026-##-## 16:54:30.175 UTC [OsAssistedMigrationService_SvcThread-32, Ent: HybridityAdmin, , TxId: <Tx-UUID>] INFO  c.v.v.h.s.m.jobs.LinuxFixupJob- getFixupDiskInfoFromDatabase: from database - fixupDiskInfo: {"fixupDiskPath":"Service","datastoreId":"datastore-######"}  migrationId: <UUID>
  2026-##-## 16:54:30.176 UTC [OsAssistedMigrationService_SvcThread-32, Ent: HybridityAdmin, , TxId: <Tx-UUID>] INFO  c.v.v.h.s.m.jobs.LinuxFixupJob- doDetachFixupDiskFromSDR(): fixupDiskInfo = {"fixupDiskPath":"Service","datastoreId":"datastore-#####"} migrationId: <UUID>
  ...
  2026-##-## 16:55:01.410 UTC [OsAssistedMigrationService_SvcThread-30, Ent: HybridityAdmin, , TxId: <Tx-UUID>] ERROR c.v.v.h.s.m.h.OsAssistedMigrationUtil- Task Failed. {"fault":{"@xsi:type":"InvalidArgument","invalidProperty":"fileType"},"localizedMessage":"A specified parameter was not correct: fileType"}

Environment

VMware HCX 4.11.4 and older

Cause

The HCX Service Mesh name for OS Assisted Migration contains one or more spaces in the name. 

Resolution

• Delete and recreate the Service Mesh with a name that contains no spaces.
• The permanent fix will be provided in a future version of HCX.
  
  
• Verification:
  
  Retrying the OSAM migration, the app.log will now provide a "fixupDiskPath" where before these messages were never logged.
  
  

  2026-##-## 10:08:03.709 UTC [OsAssistedMigrationService_SvcThread-1720, Ent: HybridityAdmin, , TxId: <Tx-UUID>] INFO  c.v.v.h.s.m.jobs.LinuxFixupJob- getFixupDiskInfoFromDatabase: from database - fixupDiskInfo: {"fixupDiskPath":"<ServiceMesh Name>/<ServiceMesh Name>-SRG-I1_1.vmdk","datastoreId":"datastore-#####"}  migrationId: <UUID>
  2026-##-## 10:08:03.709 UTC [OsAssistedMigrationService_SvcThread-1720, Ent: HybridityAdmin, , TxId: <Tx-UUID>] DEBUG c.v.v.h.s.m.jobs.LinuxFixupJob- doPrepare() from database fixupDiskInfo = {"fixupDiskPath":"<ServiceMesh Name>/<ServiceMesh Name>-SRG-I1_1.vmdk","datastoreId":"datastore-#####"}  migrationId: <UUID>

  
  For the new VM which is instantiated, there will be a FixupDisk.vmdk Copy file task which completes successfully: