http://support.microsoft.com/default.aspx?scid=kb;en-us;Q260650 On the above URI, MS admit it's their fault. Clear your client's cache, and it's solved. Please see the article. HTH Lee Goddard http://support.microsoft.com/default.aspx?scid=kb;en-us;Q260650
Responses to this message: