Article ID: 115874, created on Apr 1, 2013, last review on Apr 25, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.6
  • Virtuozzo containers for Windows 4.5
  • Virtuozzo containers for Windows 4.0


It is not possible to start a container due to a license limitation, even though you have the proper license:
Error invoking external utility.  License limit was reached , cannot continue operation.

It is not possible to see a list of running containers from the license:
C:\Users\Administrator>vzlicview | findstr ct_total
However, it should display the running containers:
C:\Users\Administrator>vzlicview | findstr ct_total
So, for the license monitor, it looks like the license limit has been reached.


There are problems with one of the containers; the container cannot be started and hangs in the starting state. "vzlicmon" is started after container startup is initiated, so if there is any issue with starting containers, "vzlicmon" might get stuck as well. 


In this case, it is required to identify faulting container or containers.
  1. Run the script to identify which container is the problem container:
    C:\> echo exit >exit.txt
    C:\> for /f %i in ('vzlist -Ho ctid') do vzctl enter %i <exit.txt
    The script will attempt to enter and exit each running container. If it gets stuck on a container, this is the problem container ID.
  2. Restart or stop this container and re-run the script.
  3. Repeat until the script does not get stuck on any container.
  4. Reboot the Hardware Node.

6c20476fe6c3408461ce38cbcab6d03b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 28d0f7cc091e3b9304fa556c03f9a940 d09cb2230ee0cfa720ed0f2a3cc39452

Email subscription for changes to this article
Save as PDF