Not sure if the issue is fixed, have come across this KB article:
http://support.microsoft.com/kb/842527