Many people seem to have the same error in their log files:
“Invalid object name ‘AR_CacheCounters’.”
It’s not clear where it’s coming from, or how to solve it. I’ve searched some hours looking for a solution, but I could only find some indications it could have something to do with search. I finally just tried (it’s not a live environment yet) killing the search service and restarting it again, and that seemed to have done the trick.
So this is not a guaranteed solution, but you can try the next steps:
stsadm -o execadmsvcjobs
stsadm -o osearch -action start (just to be sure it’s started)
stsadm -o osearch -action stop
It’ll ask you if you really want to lose your index, answer “y” (in the dutch version it states [j/n], but answering ‘j’ doesn’t work).
Now start the service via central administration again and make sure you reattach your SSP to the indexer service, because it will get detached when you stop it. After I’ve done this, the errors seemed to have disappeared from log. I’ll update this post when I’m sure it’s the solution or if it didn’t really fix it.
Update 2009/12/10: didn’t seem to do the trick after all, the errors happily returned to the log files over night.