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

mssql2k sqloledb.1 (re)connection failure

Hey all, 2 questions.

Is there a way to 'refresh' the value of adodb.connection.state? and When my ado class reconnects after a dropped connection i still get connection failure errors.

I'm trying to make the connection b/n the my work's app and mssql server more 'robust'.

Our ado class tests the connection in the 'execute' method ie if connect() execute db task

.connect() is

IF this.loConnection.State = adStateOpen
*-- The connection is already open.
ELSE
create connection
ENDIF

return (this.loConnection.State = adStateOpen)

Now, this works fine when starting up the app, and everything runs fine, but *in theory* it should be able re-establish the connection at any time. So i kill the connection @. on the sql server while the app is running and try to perform a task that requires a db connection.

problem is that 'this.loConnection.State' is still equal to 1 even though the connection is no longer there.

It gets changed to 0 when the .execute fails but the failure is less than graceful... and although it reconnects (sp_who shows a new connection), it seems like the ado object is trying to connect using the old connection rather than the new one. command.activeconnection is set to the new connection in the .connect method so i dunno what's up.

Any ideas?
If you look for DBPROP_CONNECTIONSTATUS you will see that the status can be
uninitialized, initialized, or communicationfailure.
You cannot get communicationfailure unless you execute something and it fails.|||I suspected that wouldn't be able to do anything with .State once the connection has been made.

Any tips re: the other problem? Is there anything else I need to recreate/reinitialise besides command.activeconnection when i open a new connection?
|||On a second thought the provider can actually check the connection when the property is requested by GetProperties. I think that SQLOLEDB might be doing this. I will have to check the code to see if this is the case, and also how ADO is refreshing the properties, unless of course somebody else does not come up with the answer sooner.|||Could you try checking "Connection Status" property of the ADO Connection?
I beleive that this is how DBPROP_CONNECTIONSTATUS is being exposed from a corresponding provider.

mssql2k sqloledb.1 (re)connection failure

Hey all, 2 questions.

Is there a way to 'refresh' the value of adodb.connection.state? and When my ado class reconnects after a dropped connection i still get connection failure errors.

I'm trying to make the connection b/n the my work's app and mssql server more 'robust'.

Our ado class tests the connection in the 'execute' method ie if connect() execute db task

.connect() is

IF this.loConnection.State = adStateOpen
*-- The connection is already open.
ELSE
create connection
ENDIF

return (this.loConnection.State = adStateOpen)

Now, this works fine when starting up the app, and everything runs fine, but *in theory* it should be able re-establish the connection at any time. So i kill the connection @. on the sql server while the app is running and try to perform a task that requires a db connection.

problem is that 'this.loConnection.State' is still equal to 1 even though the connection is no longer there.

It gets changed to 0 when the .execute fails but the failure is less than graceful... and although it reconnects (sp_who shows a new connection), it seems like the ado object is trying to connect using the old connection rather than the new one. command.activeconnection is set to the new connection in the .connect method so i dunno what's up.

Any ideas?
If you look for DBPROP_CONNECTIONSTATUS you will see that the status can be
uninitialized, initialized, or communicationfailure.
You cannot get communicationfailure unless you execute something and it fails.|||I suspected that wouldn't be able to do anything with .State once the connection has been made.

Any tips re: the other problem? Is there anything else I need to recreate/reinitialise besides command.activeconnection when i open a new connection?
|||On a second thought the provider can actually check the connection when the property is requested by GetProperties. I think that SQLOLEDB might be doing this. I will have to check the code to see if this is the case, and also how ADO is refreshing the properties, unless of course somebody else does not come up with the answer sooner.|||Could you try checking "Connection Status" property of the ADO Connection?
I beleive that this is how DBPROP_CONNECTIONSTATUS is being exposed from a corresponding provider.

MSSQL transactional replication failure timeout / general network error

Hi all,
I was hoping someone can assist me in a problem that has been going on
for some time.
We have been experiencing replication problems for a while, when
replicating data (1 table of approx 150,000 records, 1 of 75,000) to
our SQL server on our website.
We have noticed a lot of general network errors, and although it often
sorts itself out, it sometimes fails and needs to be started by hand.
The data changes in batches every hour and sometimes 5% of the records
may be replaced.
This has recently got worst, to the point that SQL server is now
refusing to connect to our web database when I delete and re-push the
replication job. It simply waits for quite a while and then times
out. If I try and replicate a small table from the same publisher to
the same subscriber it works fine.
Does anyone have any ideas?
By the way
Using SQL server 2K, transactional replication over a 2Mb leased line.
Many thanks
Chris
enable replication logging to see where it is failing.
Follow the instructions here on how to enable logging.
http://support.microsoft.com/default...b;en-us;312292
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Chris Bartington" <chris.bartington@.orange.net> wrote in message
news:175eba94.0411231017.76ce38d3@.posting.google.c om...
> Hi all,
> I was hoping someone can assist me in a problem that has been going on
> for some time.
> We have been experiencing replication problems for a while, when
> replicating data (1 table of approx 150,000 records, 1 of 75,000) to
> our SQL server on our website.
> We have noticed a lot of general network errors, and although it often
> sorts itself out, it sometimes fails and needs to be started by hand.
> The data changes in batches every hour and sometimes 5% of the records
> may be replaced.
> This has recently got worst, to the point that SQL server is now
> refusing to connect to our web database when I delete and re-push the
> replication job. It simply waits for quite a while and then times
> out. If I try and replicate a small table from the same publisher to
> the same subscriber it works fine.
> Does anyone have any ideas?
> By the way
> Using SQL server 2K, transactional replication over a 2Mb leased line.
> Many thanks
> Chris