Well this was posted in the SQL 2005 forum so if that KB does apply then this post is in the wrong forum as that KB is for SQL 2000 and ultimately resolves the issue by installing a Service Pack for SQL.

I agree the checks are good though.