January 31, 2009
12:21 am

This post discuss an issue revolves around the amount of maximum PagedPool memory available on the server following the Windows Server 2003 Service Pack 2 install and the subsequent reboot.  In the cases we’ve seen, the systems have been generating the infamous Event ID 333. As you can see, the error messages clearly point to some sort of resource issue.  However, since no Event 2020 (which indicates a depletion of PagedPool memory) has been generated, nothing immediately indicates that we have a PagedPool issue.

Full Article

Loading

Contextual Related Posts:

No followup yet

Leave a Response

Comment Preview
« SBS 2008: Why my computer status not shows online in console?Workaround to run Live Mesh Beta client and Live Framework CTP client together »
Feed Icon

Subscribe via RSS or email: