Buy me an espresso

February 15, 2008

15 days later ... more 6398, 6482, 7076s

Overview
They are back! After 15 long days of clear event logs (that's very long for SharePoint) the errors have returned.

While the "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." specific errors are a memory ...

The new kids on the block are "Not enough storage is available to process this command.".

Solution
Installed the .NET 2.0 SP1 (available through Windows Update) and the errors have been gone for 11 days now ... that doesn't mean they won't be back!