http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Was it a bunch of DateTime messages? I ran this once as well and that was what was happening. Never did figure out why all those messages got sent tho http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment4http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment4Sat, 24 Oct 2009 01:15:46 GMTThis bit me, too, when I turned on journaling for certain queues. A few weeks later everything suddenly stopped working because the journal also apparently contributes to the 1GB limit. Ugh. http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment3http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment3Fri, 23 Oct 2009 19:54:52 GMTAnother good post: [http://support.microsoft.com/kb/899612](http://support.microsoft.com/kb/899612) An additional interesting thing is that I think at least previous to Windows 2008, MSMQ stored or memory mapped messages in the filesystem, so we had a antivirus on a system that didn't have the right exclusions that just tanked performance. Also you can set quotas for defined inbound queues, but I didn't see how to set them for outbound queues, so I tune the static queue quotas to reserve space under the machinequota limit to accomodate some amount of outbound. http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment2http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment2Fri, 23 Oct 2009 17:28:31 GMTWinXp does not have these MSMQ machine quotas. Win2K3 and up does. Also, I believe you have to be a domain admin to even see the property pages for MSMQ to edit this setting! http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment1http://ayende.com/4262/msmq-insufficient-resources-to-perform-operation#comment1Fri, 23 Oct 2009 10:47:47 GMT