posted on August 29, 2019 by Jeff Davies
Try applying patch as suggested by SQLUSA in this post.
http://support.microsoft.com/kb/942704/en-us