• I just had this problem on one of my test servers. Simply restarted it and it went away, which you would expect with the problem being in tempdb, unless there was corruption in model database (and/or systemresource database on 2005 and 2008?).