I'm sure I would have posted the fix here if I had one at the time. Sorry, I don't remember what server I was getting this on so I can't...

DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed. [SQLSTATE 42000]...

Yes, SP2. Fat-fingered.:alien:

I fell into the same trap the other day with the "Network access: Do not allow storage of credentials or .NET Passports for network authentication = Enabled" registry setting, and...

You guys are not going to believe this, but I was on a support call with Microsoft the other day (yes, back to more issues with my Win2008 cluster and...

Using SSMS, open the script in a query window with a connection to the instance you're having the problem with. It will only affect the instance you're connected to,...

That's the same error I was able to resolve by manually running that update script. Check that other thread again.

Thanks,

Dale

Take a look at this other thread and see if the steps outlined in the referenced blog apply to your troubles here.

http://www.sqlservercentral.com/Forums/Topic763709-146-1.aspx

http://paradisj.blogspot.com/2008/08/sql-server-2005-database-mail-in.html

Dale

I had a similar problem with SQL2005 Standard DBMail on a Windows 2008 cluster after applying SP3.

You might need to manually rerun the script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\install\sysdbupg.sql".

Adjust the path...

I also had a problem with DBMail that logged the message "Mail configuration information could not be read from the database" into the DBMail error log.

This was corrected by running...

I had the exact same issue on the same setup (SQL2005-SE with SP3 and cu5 (9.00.4230)) on a Windows 2008 cluster, all 64-bit. The following link describes a number...