RDP or telnet connection to the container cannot be established, or RDP connects, but only blue background of Windows appears
C:\>vzctl enter 101 ERROR: Windows API function call 'CreateProcess' failed, code 0x8 cmd.exe Environment is not changed. Command 'enter' is successfully finished
C:> vzctl enter 101 VZExec: Returned with code -1073741502 Command 'enter' is successfully finished
C:> vzctl enter 101 ERROR: Windows API function call 'CreateProcess' failed, code 0x5 cmd.exe Environment is not changed. Command 'enter' is successfully finished
Programs may not start with following message:
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.
Note: Use the Export Event Log to a file article to export Event Viewer messages from the container without an RDP session.
There is not enough resources to create a process inside of the container, the limit of number of processes and threads was reached or container is lack of memory.
If the memory limit was reached, following error message can be located in container's System Logs
Check the Number of processes and threads allowed:
vzlist 101 -o numproc,numproc.b NPROC NPROC.B 60 60
and increase it if the barrier value was reached:
vzctl set 101 --save --numproc 100
Check the amount of memory consumed and memory limit for affected container:
vzlist 101 -o vprvmem,vprvmem.b
Process consuming memory resources can be detected from the Hardware Node side by opening Task Manager and sorting processes by CTID. Find your container and locate process consuming Memory the most. It will help to find out how memory got completely consumed.
There are two ways that allow you to deal with memory shortage:
Restart the affected container to release memory resources inside the container;
C:\> vzctl restart 101
Increase the memory limit for the container;
C:\> vzctl set 101 --vprvmem 1024
If this article didn't help you we suggest to check general RDP troubleshooting article for more hints.