Input string was not in a correct format due to signature() statement in boot.ini

During the Take Control of Source Machine step, the job fails with an error stating "Input string was not in a correct format ".

The exact error message that appears during the Take Control of Source Machine step is as follows:

Failed
Input string was not in a correct format.
Started: 18/01/2006 8:55:03 PM
Completed: 18/01/2006 9:16:32 PM

The above error is likely to occur if the boot.ini of the source machine contains a signature() statement in one or more of its ArcPaths.  Currently, PowerConvert does not support boot.ini files that contain signature() statements.  Generally speaking, Windows only requires the signature() syntax in the boot.ini if one (or more) of the following conditions exists:

• Your server's BIOS or the IDE controller does not support int13 BIOS extensions
• The int13 BIOS extensions are disabled.
• The ending cylinder number for the installation partition is higher than 1024.
• Your SCSI controller's BIOS is disabled and thus int13 BIOS calls cannot be used during the boot process

If the source machine does not fall into any of the above conditions, then the boot.ini should be edited to remove the signature() statement so that the ArcPath is in a typical "multi(X)disk(X)rdisk(X)partition(X)" format. 

Please review TID 7920463 for other potential causes.

Microsoft Knowledge Base article 227704 also has some further information regarding the use of the signature statement in the boot.ini

Once the boot.ini of the source machine has been edited, refresh the server details in the PlateSpinClient and retry the conversion.