I had this issue as well on 3 different production servers, debugging the upgrade script pointed me out that there was a user database with logical name "master". Further investigation...
I just starting using SQL Server 2008 and with it the auditing feature. I come across the same problem you are having but possible it is different after all.