Microsoft Environment Viewer could not connect to the following virtual machine because computer name of the VM is not available: ...

Microsoft Environment Viewer could not connect to the following virtual machine because computer name of the VM is not available: {0}. Possible reasons are: 
1. Hyper-V guest components are not installed on the VM.
2. Hyper-V guest components are not running.
3. The OS for the virtual machine is not supported OS.
4. The OS is still starting.
5. Remote desktop is not enabled on the VM.
6. A Network connection to the VM is not available.

Microsoft Document Explorer 2008 Redist for Microsoft Visual Studio 2008. This redist contains the tools required to view ... Microsoft Document Explorer cannot be shown because no valid help collection has been specified. If Microsoft Document Explorer ... Microsoft Environment Viewer could not connect to the environment because it could not find an active or stored environment ... Microsoft Environment Viewer could not connect to the environment because it could not find an active or stored snapshot ... Microsoft Environment Viewer could not connect to the following virtual machine because computer name of the VM is not available: ... Microsoft Environment Viewer could not connect to the following virtual machine because information of the machine is not ... Microsoft Environment Viewer could not connect to the following virtual machine because IP address of the VM is not yet available: ... Microsoft Environment Viewer could not connect to the following virtual machine because it is not connected to an external ... Microsoft Environment Viewer could not connect to the following virtual machine because network isolation configuration is ...