This can occur if VMM has orphaned records in the database showing snapshots that no longer exist.
To resolve this issue, remove the orphaned objects from the database by following the steps below.
1. Stop the System Center Virtual Machine Manager service on the VMM 2012 server.
2. Back up the Virtual Manager database.
3. Open SQL Management Studio and run the following script on the VMM database:
BEGIN TRANSACTION T1DECLARE custom_cursor CURSOR FORSELECT VHDId, VDriveId fromdbo.tbl_WLC_VDrive WHERE [VHDId] NOT IN(SELECT VHDId from dbo.tbl_WLC_VHD WHERE VHDID IS NOT NULL)DECLARE @VHDId uniqueidentifierDECLARE @VDriveId uniqueidentifierOPEN custom_cursorFETCH NEXT FROM custom_cursor INTO @VHDId, @VDriveIdWHILE(@@fetch_status = 0)BEGINif(@VHDId is NOT NULL)DELETE FROM dbo.tbl_WLC_VDriveWHERE VDriveId = @VDriveIdFETCH NEXT FROM custom_cursor INTO @VHDId, @VDriveIdENDCLOSE custom_cursorDEALLOCATE custom_cursorCOMMIT TRANSACTION T1
4. Start the System Center Virtual Machine Manager service again and refresh problem VMs. The VMs should return to a proper reporting state.
This resolution can also be used for 801 errors when perfoming a Physical to Virtual conversion (P2V). Information on that solution can be found here: