When attempting to create a catalog, error message "There is no master image associated with the machine catalog" is displayed.
The following errors might be found when a trace is captured:

"HostServiceHCL:2:1:Invoke on New-VMCheckpoint took 425ms"
"HostServiceHCL:1:1:Execute:'New-VMCheckpoint' Powershell Invoke returned error: (2206,Microsoft.SystemCenter.VirtualMachineManager.Cmdlets.CheckpointVMCmdlet) Virtual machine MASTERIMAGE cannot be used for any checkpoint actions. For checkpoint actions, a virtual machine must be running, stopped, paused or in a saved state. (Error ID: 2206)

Ensure that the virtual machine is running, stopped, paused or in a saved state, and then try the command again.

To restart the job, run the following command:
PS> Restart-Job -Job (Get-VMMServer masterimage.domain.com | Get-Job | where { $_.ID -eq "{97befe5c-84db-43de-b713-893b3068bdfc}"})

It is recommended the to take a snapshot of the MasterVM prior to attempting to create the catalog. If the hypervisor is Hyper-V and the behavior persists, it is recommended to verify that your Hyper-V Hypervisor is fully patched and, if needed, engage Microsoft for further investigation.

Problem Cause

Machine Creation Services (MCS) is prevented from creating a snapshot due to a specific issue with the Hypervisor and the current state of the MasterVM.