Change to compatibility level of the destination master database to the appropriate level (i.e. 90 for 2005, 100 for 2008).

Probably the destination has been upgraded, and in this situation...

Dear Igor,

I had the same issue and I solved it using your suggestion to alter db ownership.

Thanks.