Article ID: 121451, created on May 3, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows 6.0
  • Virtuozzo containers for Windows 4.6
  • Virtual Automation

Symptoms

  1. RDP or telnet connection to the container cannot be established, or RDP connects, but only blue background of Windows appears

  2. vzctl enter fails:

    C:\>vzctl enter 101
    ERROR: Windows API function call 'CreateProcess' failed, code 0x8 cmd.exe
    Environment is not changed.
    Command 'enter' is successfully finished
    

    or

    C:> vzctl enter 101
    VZExec: Returned with code -1073741502
    Command 'enter' is successfully finished
    

    or

    C:> vzctl enter 101
    ERROR: Windows API function call 'CreateProcess' failed, code 0x5 cmd.exe
    Environment is not changed.
    Command 'enter' is successfully finished
    
  3. 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.

Cause

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

alttext

Resolution

  1. 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
    
  2. 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:

  1. Restart the affected container to release memory resources inside the container;

    C:\> vzctl restart 101
    
  2. Increase the memory limit for the container;

    C:\> vzctl set 101 --vprvmem 1024
    

Additional resources

If this article didn't help you we suggest to check general RDP troubleshooting article for more hints.

Search Words

blue

System files not zero-sized, cannot create link

code 0x5 cmd.exe

RDP to container does not work

ERROR: Windows API function call 'CreateProcess' failed, code 0x8 cmd.exe

CreateProcess

Returned with code -1073741502

rdp

remote desktop

6c20476fe6c3408461ce38cbcab6d03b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 6f8e3eda12803cf88a9587e9782c9ed6 319940068c5fa20655215d590b7be29b

Email subscription for changes to this article
Save as PDF