Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
When you attempt to send or receive a Microsoft Message Queuing message, you may receive a 0xc00e0027 error. You may also receive the following error messages:
There are insufficient resources to perform the operation.
Event ID: 2085 Date: 2003/01/07 Time: 20:36:14 User: N/A Computer: Computername Description: Unable to create message file C:\WINNT\System32\msmq\STORAGE\l0000009.mq. There is insufficient disk space or memory.
This error may occur if the MQAC.SYS driver cannot allocate kernel memory. However, there are many potential causes for this error.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this error, follow these steps:
In Windows Registry, click Start, and then click Run.
Another related error that may appear in the log is:
Wed Feb 05 17:49:21 2003: QM Error: session/120, HR: 0xc000009a
The total paged pool usage is represented by the number of paged pool pages. In this example, it is represented as 0x8183. By default, the Message Queuing paged pool threshold is calculated at 80 percent of the total paged pool usage. In this example, it is calculated as 0x8180. In this example, the paged pool usage exceeds the Message Queuing paged pool threshold so Message Queuing will report 0xc00e009a and 0xc00e0027 errors.This causes allocation failure with an error code of 0xc000009a (
) to occur.
The paged pool size is less than expected. The threshold, which is based on paged pool size, is calculated at startup. There are two known causes of low paged pool size:
The /3GB switch exists in the boot.ini, which enables 3-gigabyte address support for applications. This reduces the paged pool size. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
Terminal Server requires a large number of system pages, which can reduce the paged pool size. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
247904 How to configure the Paged Address Pool and System Page Table Entry memory areas