I found this on a newsgroup for a response to the same error:

Actually I found a post somewhere that suggested uninstalling the

workstation components, repairing the .NET 2.0 framework, and...