Monday, February 2, 2009

Not enough quota available to process this command

Presently unresolved thread for tracking a recurring error on one of the work XPS's.

The error is is not accessible. Not enough quota is available to process this command.

Once this is received, the only thing that can be done is close all programs and reboot the machine.

It is somewhat interesting that this is an XPS that has more memory than the others.
The hardware and software configuration is otherwise identical to the others, and no dissimilar programs are being run (Labview, Word, PDF Reader).

The interwub doesn't have a consensus to the problem, but the disparate postings and answers may all point to a common solution if I could just figure it out.

Nobody has fingered this as a virus issue.

First off is M$'s patronizing KB article:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/1495.mspx?mfr=true

Also here:
http://msdn.microsoft.com/en-us/library/ms820778.aspx

This thread:
http://74.125.95.132/search?q=cache:tBeocXxTxcEJ:forums.ni.com/ni/board/message%3Fboard.id%3D170%26thread.id%3D258595+Not+enough+quota+is+available+to+process+this+command&hl=en&ct=clnk&cd=7&gl=us

points to two interesting process monitoring options aside from good old Taskmon, including this one which seems well loved but looks useless:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

These guys trying to troubleshoot their software:
http://forum.sysinternals.com/forum_posts.asp?TID=4975

Have traced it to Access Control List problems? See these two:
http://groups.google.de/group/microsoft.public.win32.programmer.kernel/browse_thread/thread/a024fb3948d5943d/ba4e698efab83ada?lnk=st&q=%22Not+enough+quota+is+available+to+process+this+command%22&rnum=9&hl=de#ba4e698efab83ada
http://support.microsoft.com/kb/185292/en-us

These guys are trying to do simple file copies in Vista and having the problem, and traced it to something to do with offline file sync?
http://social.technet.microsoft.com/Forums/en-US/itprovistaapps/thread/c6c79225-dd97-41ce-aeb2-b3f46f235872/

Perhaps most promising for my configuration, this guy blamed it on Dell Control Utility:
http://discussions.virtualdr.com/archive/index.php/t-129176.html