That's the error that I remember seeing on my c-worker's machine after we fizxed the service pack issue. Check out the following KB to fix the latest problem.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q255900