Apparently the latch on the door to the IT area is broken again, because a user got in the other day. She was whining about how slow SharePoint is, but instead of firing a USB missile at her, I opened up the log files and took a peek.

Wow, there's a lot of information there. Someday I'll have to actually read some of it, but for now there were umpteen thousand entries that look something like this:

11/18/2008 15:25:17.04  OWSTIMER.EXE (0x0888)                    0x08B4 Windows SharePoint Services    General                        0 Medium   Preserving template record with size 4020, use count 4, key ct-1033-0x010100c568db52d9d0a14d9b2fdcc96666e9f2007948130ec3db064584e219954237af39 

Eventually, OWSTIMER got tired and stopped logging these things, and SharePoint response went back to normal (insert punchline here). I Go-ogled the message and read every single hit -- lots of people complaining but not one useful response. Ok, there was one that said it occurs when memory is low, but neither my SharePoint or Sql servers has ever committed even half the memory they have. And yes, there was a suggestion that I throttle back how much I log, but I'm more interested in why I'm getting the entry (since it seems to slow down users' response) than I am in saving disk space.

I'm wondering if anybody has ever actually solved this problem. Let me know, but don't expect a quick response. I have to run to the hardware store and buy a new door latch.