The only database problem you may have is a deadlock situation at some point. You can turn on trace 1222 on the instance to check what objects and sessions are involved in the deadlock. In a query window:

dbcc traceon(1222,-1)

GO

Remember the setting is volatile and will be turned off in case the instance is restarted. For persistence you can add traceflag -T1222 as a startup parameter. This kind of trace is supposed to help you understanding the context in which the deadlock occurs, it is not supposed to remain active all the time. Once you've found what you were looking for, it is better to deactivate it. (dbcc traceoff(1222) or removing the traceflag)

Other error messages are more related to Sharepoint. Maybe you should post these messages on a sharepoint forum, you'd get probably better feedback there. If you can find any 'Divide by zero' event returned by Office Server Search, it may be related to a PDF iFilter problem[/url]. Just a guess, I'm not a sharepoint specialist.

HTH David B.