We found an issue with the vASA software and apparently this is a common problem and it has been escalated to the Cisco development team as of the time I wrote this post.
For anyone Googling this, this was the only mention of this problem on these forums.
The Cisco vASA appliance expects to see two .iso files on two different CD-ROM devices.
The first ISO contains the OVF environment information for the virtual machine.
It is stored with in the same datastore folder as the virtual machine and has the filename of "_ovfenv-(VM Name).iso"
The second ISO contains the device image and is called "_deviceImage-0.iso". It also is stored with the virtual machine in the same folder on the datastore.
When the VM is Storage vMotioned from one datastore to another, the .ISO files do not get migrated along with the virtual machine. As a result, this error occurs because the VM can't find that _ovfenv file.
The solution to this problem is to do the following:
1. Backup the running configuration of the vASA somewhere, like to a TFTP server.
2. Deregister the smart license of the vASA.
3. Deploy a new vASA into the environment where it will finally be.
4. Register the smart license of the vASA
5. Restore the configuration from the old vASA.
Going forward, the way how to prevent this issue from happening is to copy the iso files to your local machine first before you storage vMotion the VM, copy them back when it is in its final datastore and then point the first and second CD-ROM devices at the appropriate files.
