Article ID: 3517, created on Dec 24, 2007, last review on May 1, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.0
  • Virtuozzo for Windows 3.5.1 SP1


MSMQ is supposed to be run on several VEs on the same node. It is installed successfully on all nodes, however even it can be started on one VE it fails to start on others.

“Insufficient resources”
error is displayed at this moment.


 It is important to ensure that all the [clustered] MSMQ resources have adequate kernel memory address space for mapping messages.  Each resource has its own instance of the Message Queuing driver (Mqac.sys) which maps files to a 4MB range of the System View Space memory pool  (desktop heap for drivers). As the default pool size is 16MB, this allows for 3 MSMQ services (3x4MB=12MB) and 4MB left over for other (non-MSMQ) device drivers - this 4MB remainder may not be enough. Even worse, running a fourth service would mean MSMQ would try and allocate itself all of the memory pool, leaving none for other services to make use of. The results of this are, obviously, unpredictable and you may see "Insufficient Resources" reported.

Although, it usually relates to clusters, the situation is the same - several instances of MSMQ including the driver are running on the same node.


The solution is to configure the following value in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\SystemViewSize

should be calculated using the following formula:

SystemViewSize = (16 + (maximum of VEs with MSMQ x 4))


Please see original Microsoft articles:

1348db476c8a5844ffbef8d503db9c15 28d0f7cc091e3b9304fa556c03f9a940 965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF