VMware Converter - P2V of a physical server with multiple disks fails

I had the opportunity to work on a issue recently where the system administrator was trying to convert a physical server to a VM and the conversion was failing at the initial task of collecting the source machine details.

The default logs did not provide any information and therefore I went ahead and enabled verbose logging. Following this I was able to see the following in the logs.

2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] Mapping a recognized volume \\?\Volume{132d9331-1f9f-441f-a37d-1283440beccb}\ with ID \WindowsBitmapDriverVolumeId=[44-4D-49-4F-3A-49-44-3A-31-93-2D-13-9F-1F-1F-44-A3-7D-12-83-44-0B-EC-CB]
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [PopulateVolumeProperties] volume \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\  corresponds to \Device\HarddiskDmVolumes\Ampsv01960pjtDg0\Volume31 device name.
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [,0] error [Windisk_CheckNonFixedMediaDevice] Failed to retrieve media type for \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\: Incorrect function (1)
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [GetDriveLetterOrMountPoint] Mount point for volume \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\ is V:\TlogTW2\
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [,0] Info[Windisk_GetVolumeDeviceNumber]: IOCTL_GET_STORAGE_DEVICE_NUMBER for volume \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\ is not supported .... Trying NT method.
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [,0] Error[Windisk_GetVolumeDeviceNumber]:Failed to get \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\ Volume's disk number
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [,0] Info[Windisk_GetVolumePartitionInfo]:Number of disk extents is 6. Volume \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\ is a dynamic volume. No meaningful partition information can be associated with it
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [,0] Info[Windisk_GetVolumePartitionInfo]:Number of disk extents is 6. Volume \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\ is a dynamic volume. No meaningful partition information can be associated with it
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [PopulateVolumeProperties] Unable to get \\?\Volume{0b323bcd-7f6f-4473-9acf-7699b247f96e}\ volume's active flag info.
2013-08-06T13:48:32.561+02:00 [04248 verbose 'Default'] [GetVolumeProperties] finished.

Checking the system revealed that it had nearly 120+ disks mounted from the SAN. Checking the VMware community did not show any maximums for the number of disks that can be connected to the source server that is being converted.
Anyways, we unmapped the SAN disks and then initiated the conversions which went ahead smoothly. This solution was acceptable to the user, luckily.

If anybody has any information on what is the maximum number of disks supported by VMware converter, please share the information.