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

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-ussql

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

MSSQL7 and WinXP

Hi!
We're closer to a solution to our problem with slow machines on a MSDE
database (two weeks ago).
We now have one standalone machine that runs MSSQL7, SP4 (SP4 was
installed after it did not work without it).
The computer has been freshly set up with WinXPPro, MSSQL7 and our
application. All current Windowsupdates applied afterwards.
OK, what we have now:
1) Extremely quick resutls when using osql
2) Extremely slow startup time of our application. (Delphi, using ADO as
connection)
The reason for 2) is (or rather one effect of it) can be seen in the error
log:
--8<--
2004-06-17 15:14:19.43 spid5 Startet Datenbank 'Patient'.
2004-06-17 15:14:19.43 spid5 Opening file C:\MSSQL7\data\Patient.mdf.
2004-06-17 15:14:19.43 spid5 Opening file
C:\MSSQL7\data\Patient_log.LDF.
2004-06-17 15:14:20.01 spid14 Closing file C:\MSSQL7\data\Stammdaten.mdf.
2004-06-17 15:14:20.01 spid14 Closing file
C:\MSSQL7\data\Stammdaten_log.LDF.
--8<--
Sections like this one are repeated *quite* often, read: immediately
afterwards. Several times. For approx.10 seconds per database. (which
makes about 10-20 retries).
We then noticed that this machine has hyperthreading enabled, which we
disabled. The entries in the log file were reduced to a more sensible
amount, still it happens more often than on other machines with our
software and MSSQL7 or MSDE.
Question: What else can we do? Is there something with respect to
hyperthreading that can still interfere? Have others also seen multiple
repeating entries in the log files and have a clue as to where they come
from?
Thanks for reading,
Stefan
See the BOL for information concerning the AUTO_CLOSE option. It appears to
me that you have that enabled (the default for MSDE) and the database server
is closing the database after all connected clients are disconnected.
Jim
"Stefan M. Huber" <looseleaf@.gmx.net> wrote in message
news:opr9qpvxj0s9ddfw@.news.individual.de...
> Hi!
> We're closer to a solution to our problem with slow machines on a MSDE
> database (two weeks ago).
> We now have one standalone machine that runs MSSQL7, SP4 (SP4 was
> installed after it did not work without it).
> The computer has been freshly set up with WinXPPro, MSSQL7 and our
> application. All current Windowsupdates applied afterwards.
> OK, what we have now:
> 1) Extremely quick resutls when using osql
> 2) Extremely slow startup time of our application. (Delphi, using ADO as
> connection)
> The reason for 2) is (or rather one effect of it) can be seen in the error
> log:
> --8<--
> 2004-06-17 15:14:19.43 spid5 Startet Datenbank 'Patient'.
> 2004-06-17 15:14:19.43 spid5 Opening file C:\MSSQL7\data\Patient.mdf.
> 2004-06-17 15:14:19.43 spid5 Opening file
> C:\MSSQL7\data\Patient_log.LDF.
> 2004-06-17 15:14:20.01 spid14 Closing file
C:\MSSQL7\data\Stammdaten.mdf.
> 2004-06-17 15:14:20.01 spid14 Closing file
> C:\MSSQL7\data\Stammdaten_log.LDF.
> --8<--
> Sections like this one are repeated *quite* often, read: immediately
> afterwards. Several times. For approx.10 seconds per database. (which
> makes about 10-20 retries).
> We then noticed that this machine has hyperthreading enabled, which we
> disabled. The entries in the log file were reduced to a more sensible
> amount, still it happens more often than on other machines with our
> software and MSSQL7 or MSDE.
> Question: What else can we do? Is there something with respect to
> hyperthreading that can still interfere? Have others also seen multiple
> repeating entries in the log files and have a clue as to where they come
> from?
> Thanks for reading,
> Stefan
>
|||On Fri, 18 Jun 2004 09:44:47 -0700, Jim Young <thorium48@.hotmail.com>
wrote:

> See the BOL for information concerning the AUTO_CLOSE option. It appears
> to me that you have that enabled (the default for MSDE) and the database
> server is closing the database after all connected clients are
> disconnected.
Thanks for the pointer. However, I wonder, why this happens when only one
single client wants to connect at startup. I'll check that next time I am
at work. Thanks.
Stefan
"Mobile launchers are more difficult to detect because they move
around, unlike fixed launchers."
-- Katie Couric, NBC News