MSXML6 breaks viewer used with Microsoft Electronic Learning Library

Installation of SQL 2005 Express resulted in the failure of the viewer used with the Microsoft Electronic Learning Library products. The viewer runs under IE and is driven by an XML file.

This has been verified on several systems. I uninstalled only MSXML6 and the viewer worked normally.

I have no idea if the problem is with the viewer script, the XML file driving it, or MSXML6 but obviously this might be a breaking change to the product.

Can anyone shed light?

Tom Skinner [C# MVP]

Hi Tom,

I'm looking into this for you.

Mike Wachal
SQL Express

|||

I found a workaround. If you disable the XML DOM Document 6.0 add-on in IE the viewer loads OK. Apparently MSXML6 is used by IE as the default if it is installed. This broke the MELL viewer. It would still be valuable to know why as other programs using IE as a frontend may break as well.

Tom Skinner [C# MVP]

|||

Hi,

The MELL dev team has been made aware of the issue that XML Parser 6.0 breaks MELL. They are currently working on putting together a patch for this. As soon as the patch becomes available, we will let you know.

Thanks.

|||

Before you run Mell, open up a dos window and run:

regsvr32 -u %windir%\system32\msxml6.dll

You should get an acknowledgement that the unregister was successful.

Start up your Mell training.

Go back to the DOS window and run:

regsvr32 %windir%\system32\msxml6.dll

Again, you should get an acknowledgement. Learn away. Doing it this way means you won't forget to put things back so that SQL Server 2005 is fully functional.

David Rogers (MCP, LIMOM)

|||Thanks. This fix my e-learning viewer problem. Is SQL 2005 express the only program dependent on msxml6.dll?|||according to MS this "bug" was done by design, the new xml parser blocks certain calls from mell because they are less secure, and ms is suppossed to have released a fix for this, but they have not done so yet...and the ppl from the xml team say the work around posted here (which has been suggested in many other places) is not recommended since it defaults your system to use the older less secure xml parser|||The fix is now located at http://support.microsoft.com/kb/917583/en-us