It is a known bug in SQL Server versions prior to SP4. Just apply SP4 and works fine.  (sorry, can't find the Microsoft Document where it is explained)  Hope this...