This is a registry conflict issue. Microsoft has published a notice to resolve the issue: http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B314060