Max's Miscellaneous Musings

This one's popped up occasionally at work, and now at home in my WinXP-trying-to-talk-to-Win7 network:  "Not enough storage space is available to process this command".  I've seen messages like this that have ultimately wound up being related to group membership and Kerberos ticket size.  The fix was a reg hack to the MaxTokenSize DWORD value at HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Paramters - set the value to Decimal 65535.

But this particular error message was new to me.  It also disguised itself somewhat by crying about permissions (which weren't an issue as I'd eliminated this as part of the problem by loosening permissions as much as could be done).  Finally, I found the fix here:  http://brickblog.net/2009/03/04/not-enough-server-storage-is-available-to-process-this-command%E2%80%9D-error-print-this-post-print-this-post.  Unsurprisingly (in hindsight), another reg hack, this one related to the Server service.

I think back to the days when I first started in IT, all those many moons ago.. before we had Google.  How the hell did I ever fix the myriad of bizarro, unusual problems I encountered?  I look back on it now and wonder how the hell I ever fixed anything.  I think I've become Google-dependent.  Incapable of actually thinking for myself anymore, because, hey.. someone else has surely had this problem before!

Anyway.  If you're having the storage space error, try the reghack.