Hello,
I finally suceeded in installing the entire January CTP SDK of Win FX, the run time components, the Vs.NET additions for WWF ,the CTP Of Visual studio .net code named Orcas, Expression (both the designer and the interactive designer).
All are working fine and without any problem. But when i want to view some information regarding the documentation, I keep getting this dialog box error.
---------------------------
Error
---------------------------
A Runtime Error has occurred.
Do you wish to Debug
Line: 103
Error: Could not complete the operation due to error 80041001.
---------------------------
Yes No
---------------------------
Any idea on why this happens and how to resolve the same.
Thanks and regards,
M. Rajesh

Documentation for MSH in WinFX SDK January CTP
lgayosso
Thanks for all the feedback -- we really appreciate it! We've escalated this issue to the Windows/IE folks and they're hoping to have a fix by RC1.
Regards,
raja_t
Regards,
Christoph
Jeff Agent
Same here. Any workarounds for this I'm only getting this error when I try to access certain documentation, in this case the MSXML documentation.
Jeremiorama
This is a known issue with only "some" of the content in the Windows SDK. It's related to a particular script in the compiled help files and IE 7. We're attempting to identify all the help files with this problem and apply a fix for Beta 2.
Unfortunately, there is really no easy way to work around this problem.
Regards,
bieblsoft
diane martin
I have VS2005 with WinXP SP2 and IE2Beta2. I receive the above error for all content related to Office Primary Interop Reference.
Regards
Ron Wright
I need to make a small correction to my previous reply. For the MSH documentation, this script error should be fixed in the Feb CTP SDK build, which you can download/install now. For the MSXML docs, this should be fixed for Beta 2.
Namio, can you tell me which content in VS 2005 is giving you this error
For a work-around, if you're running IE 7 on XPSP2 or Server 2003 SP1, you can always uninstall IE 7 and roll back to IE 6.
Harmomelodic
After I uninstall IE7 Beta 2, the problem is gone.
Hope this is helpful for resolving the issue.
Thanks!
Rodpheus