I had this issue too and it was solved with SQL 2005 Service Pack 1 so I guess it's a bug. As stated before...