I get this message in my ULS logs frequently. What does it mean, and why is it sometimes run by owstimer.exe and other times by w3wp.exe?

I'm facing the same issue here (hundreds of messages per second). Did you find anything about it?

Hello, I am also seeing this logged a lot. I have not seen this run under the w3wp.exe service though. Fizunk, are you using a log parser? Also, I managed to get rid of them today but I'm not sure exactly which process took care of it. I'll list them below and if either of you are still having the problem then maybe you can determine which one did the trick. 1. First I ran stsadm -o updatefarmcredentials & reset IIS 2. Second I ran stsadm -o updateaccountpasswords & reset IIS 3. Finally I restarted the timer service. For some reason my logs no longer include these messae now. I don't know what those messages mean, or if they are gone for good. So far they have stayed gone for about 3 hrs. I was trying to fix the error listed in this post while performing the above steps. http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3256140&SiteID=17&mode=1

The errors did not stay gone for good. They stayed gone for about 9 hrs and then came back. The next day I changed the account on the Windows SharePoint Services Administration service and then the errors went away again. That night they came back again, at thesame time as the previous night (10:20 pm). What ever is causing this is triggered at 10:20 on my system, but I'm not exactly sure what that is. The closest thing I can find is the user profile incremental crawl which is supposed to start at 10.

Any luck with getting rid of these for good? Living the SharePoint dream...

I also have this issue, I do not receive the messages as frequently yet they are still enough to be concerned about. If I find a solution I'll post it back here.

Hi, After Digging Web, i finally found what's going on!... By myself When server is running out of memory, SharePoint try to free up some memory by releasing unused Templates. Then someone at Microsoft probably used a logging leveltoo highfor these messages :) Solution > Free memory Bad Hungry SharePoint :(who cares?

Are there any other workarounds for this? I know that this is supposedly addressed in the April 2009 Cumulative Update (which was released just after SP2), but installing the CU in my environment is not an option (business indicates only SP will be installed to avoid repeated testing of applications). I tried this, but it doesn't seem to work: stsadm -o setlogginglevel -category timer -tracelevel High Is this error coming from a different category? TIA!Brian McCullough

Hi, we are seeing the same sort of activity on our new servers and are suspicious it "might" be being caused or triggered by our backup software and now trying to isolate the issue further, what are backup tools are you using? We are using Commvault.

Hi all, we solved this with our Backup software team. The trigger was the backup software and would expect it to be same regardless of vendor. Our vendor (Commvault) is certified for Named Pipes (installing the SQL Client Tools on the SP server) and changing the communication method for the backups to use this appears to have resolved the issue.