UNABLE To VIEW XML Pages ??

[Don]

Greetings,

I have a late model Dell with XP-Home IE-6 sp2

When I access SOME particular pages (Dell support page for example), In
addition to some parts being normal page presentation, I am getting parts
of the page with only code. (the entire left side)

Below is an example:

<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="../style/search.xsl"?>
- <left title="Search Support" image="dell.gif">
<content button="content_action.gif" buttonURL="javascript:bindAndGoReg()"
buttonAlt="Go" linkText="Advanced Search" linkImage="content_arrow.gif"
linkImageAlt="Advanced Search" linkURL="advSearch.htm" />
</left>

Any suggestions

Thank You (e-mail address removed)

 

[Guest]

xml loads data to another page they are not normally set
up to be viewable.

if you go to www.testshoot.com/nycast.asp you will see a
page that uses an xml doc (www.testshoot.com/news.xml) to
load data to a page. that is how xml works

 

[Don]

Maybe I am describing the problem wrong.

When I go to a dell support page, I am not getting the correct
presentation. I am getting part of the page normally, and other parts are
nothing but code. Please see: >Below is an example:

 

[Robert Aldwinckle]

Do you have access to another machine where it works the way you expect?

In that case here is how I have replied to this question before:

<quote>
See if you can get some clues by comparing the output
of XMLVersionText on both systems.

<TITLE>278674 - Determine the Version of MSXML Parser Installed on a Computer</TITLE>
</quote>


BTW I didn't know what you meant by "Dell Support page"
but I went here and didn't see any XML being used.
< http://support.dell.com/ >

If you need more help it may help to provide an explicit sample link.


HTH

Robert Aldwinckle

 

[Robert Aldwinckle]

Robert,

Thank You for responding to my problem.
The Dell Support page that I speak of does not have an address field like a
typical web page.

Pre loaded on my computer is a link that is to a program called Dell
Support. It has links within the program that require internet connection,
but most of the program is self contained.
(I have re-loaded the Dell Support program at least twice) IE does not have
to be open.

Also when I open Musicmatch Juke box, and select: view, radio stations, I
get nothing but code. When I make other selections, all is normal.

Below is an example when either on or off line:

Don,

Both of your examples seem to be showing that your XML support
is deficient. It appears that the files being rendered may be local
but since I'm not familiar with either let me suggest another approach
to testing if we are on the right track.

Can you render your Windows Update iuhist.xml file (or any other
local XML files)? IE should be able to show you such files nicely indented,
color-coded and with collapsible items (e.g. click on ones prefixed by
a minus sign and the subordinate items will disappear and the minus sign
replaced by a plus sign and vice versa.)

Can you use the Windows Update Troubleshooter without seeing
similar symptoms?
< http://v4.windowsupdate.microsoft.com/troubleshoot/ >

If you can you can find some problem resolutions where suggestions
are made to reinstall or upgrade the XML parser. I have called this
a bit of a Catch-22 since the troubleshooter is implemented by XML
and what is worse it requires much better XML support from IE than
merely rendering an XML file in a structured fashion as above does.

E.g. this link is offered in one of the more general examples

< http://msdn.microsoft.com/library/default.asp?url=/downloads/list/xmlgeneral.asp >

as where "You can download the latest parser from".

I'm including it here in case the troubleshooter doesn't work for you.
If I hadn't I think that the only way that you would be able to see it
would be to view the TIF and look at a file called IssuesXML.xml
by dragging it to a Notepad window.


....

Robert, I dont know what you mean by this below:

That is the title of an MSKB article I was referring the previous poster to.
The number in the title is the article's KB number.
You can find it either by typing in the number at the support site
where it lets you search by number or if you prefer you could
find it with Google by searching with KB278674. You can refine
the search by specifying site:microsoft.com with your search terms
or equivalently by starting from
< http://www.google.com/microsoft.html >

Note that unfortunately Google ignores all the META Keywords
which microsoft includes in its articles and which can make
searching on the microsoft support site so much more precise.

In any case here's where those searches could lead to:
< http://support.microsoft.com/?kbid=278674 >

The most significant thing is that there is a download link in there
for a tool called XMLVersionText.exe. As I mentioned it will be
more useful as a diagnostic if you can execute it in two settings,
one which has the problem symptom and one which doesn't.

Thank You again for the help. It sounds like a problem with XP Home itself,
and maybe not IE.

Close enough.


HTH

Robert
---

 

[Don]

Can you render your Windows Update iuhist.xml file (or any other

local XML files)? IE should be able to show you such files nicely indented,
color-coded and with collapsible items (e.g. click on ones prefixed by
a minus sign and the subordinate items will disappear and the minus sign
replaced by a plus sign and vice versa.)

I do not know exactly what you mean by "render"
I am able to view the iuhist.xml file. It is all code like you say above.
I am able to click on the + and make it a - etc. subordinate items will disappear
Below is a cut from one of my examples of what I am displaying.
(there was a + or -, in the below example but for some reason it did not copy/paste)
And I was able to toggle it.

For some unknown reason I am displaying code instead of the result. I don't know, but does Active X have anything to do with this?

<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type='text/xsl' href='/aod2/homePageTemplate.xsl?version=2003.12.18'?>
- <opt>
- <stationRecArtists>
<artistProfile hasAod="1" count="1" rowColor="artistlistbox1nb" name="OutKast"

Can you use the Windows Update Troubleshooter without seeing
similar symptoms?

Yes it looks normal as can be with no code.

In any case here's where those searches could lead to:
< http://support.microsoft.com/?kbid=278674 >

The most significant thing is that there is a download link in there
for a tool called XMLVersionText.exe. As I mentioned it will be

I ran the version test and for the most part I don't understand what it's telling me. It is over my head.
What I did notice was that it said that MSXML 3.0 is not installed
And that The version used by IE for .XML files is MSXML 3.0



Very confusing. Or may it be as simple as just that? (MSXML 3.0 is not installed)

Thanks again Robert for trying to help.


Don.....


(c) Microsoft Corporation 2001, All Rights Reserved.Produced using XMLVersion by Bruce Taimana, Microsoft Corporation
Name Version File Location
MSXML 2.5 Non-SidebySide Registration Version 8.0.6730.0 C:\WINDOWS\System32\msxml.dll
MSXML 2.6 SP3 8.30.8709.0 C:\WINDOWS\System32\msxml2.dll
MSXML 3.0 is not installed Not Applicable Not Applicable
MSXML 4.0 SP1 4.10.9404.0 C:\WINDOWS\System32\msxml4.dll
MSXML 5.0 is not installed Not Applicable Not Applicable
MSXML 6.0 is not installed Not Applicable Not Applicable
WINHTTP5 is not installed Not Applicable Not Applicable
WINHTTP 5.1 WinXP sp1 5.1.2600.1106 C:\WINDOWS\System32\winhttp.dll


Mode In Replace Mode - Please check ProgIDs to make sure
The version used by IE for .XML files is MSXML 3.0
IE Version 6.0.2800.1106 - Internet Explorer 6 SP 1


Proxy Configuration Type: None Configured
Proxy List: None

ByPass List: None



ProgID CLSID Threading Location
MICROSOFT.XMLDOM {2933BF90-7B36-11D2-B20E-00C04F983E60} Both C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLDOM.1.0 {2933BF90-7B36-11D2-B20E-00C04F983E60} Both C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLDSO {550DDA30-0541-11D2-9CA9-0060B0EC3D39} Apartment C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLDSO.1.0 {550DDA30-0541-11D2-9CA9-0060B0EC3D39} Apartment C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLHTTP {ED8C108E-4349-11D2-91A4-00C04F7969E8} Apartment C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLHTTP.1 {ED8C108E-4349-11D2-91A4-00C04F7969E8} Apartment C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLHTTP.1.0 {ED8C108E-4349-11D2-91A4-00C04F7969E8} Apartment C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLPARSER {D2423620-51A0-11D2-9CAF-0060B0EC3D39} Both C:\WINDOWS\SYSTEM32\MSXML3.DLL
MICROSOFT.XMLPARSER.1.0 {D2423620-51A0-11D2-9CAF-0060B0EC3D39} Both C:\WINDOWS\SYSTEM32\MSXML3.DLL
MSXML {CFC399AF-D876-11D0-9C10-00C04FC99C8E} Both C:\WINDOWS\SYSTEM32\MSXML3.DLL
MSXML.DOMDOCUMENT {2933BF90-7B36-11D2-B20E-00C04F983E60} Both C:\WINDOWS\SYSTEM32\MSXML3.DLL
MSXML.FREETHREADEDDOMDOCUMENT {2933BF91-7B36-11D2-B20E-00C04F983E60} Both C:\WINDOWS\SYSTEM32\MSXML3.DLL
MSXML2 {F6D90F10-9C73-11D3-B32E-00C04F990BB4} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.2.6 {F5078F22-C551-11D3-89B9-0000F81FE221} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.DOMDOCUMENT {F6D90F11-9C73-11D3-B32E-00C04F990BB4} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.DOMDOCUMENT.2.6 {F5078F1B-C551-11D3-89B9-0000F81FE221} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.DOMDOCUMENT.4.0 {88D969C0-F192-11D4-A65F-0040963251E5} Both C:\WINDOWS\System32\msxml4.dll
MSXML2.DSOCONTROL {F6D90F14-9C73-11D3-B32E-00C04F990BB4} Apartment C:\WINDOWS\System32\msxml2.dll
MSXML2.DSOCONTROL.2.6 {F5078F1F-C551-11D3-89B9-0000F81FE221} Apartment C:\WINDOWS\System32\msxml2.dll
MSXML2.DSOCONTROL.4.0 {88D969C4-F192-11D4-A65F-0040963251E5} Apartment C:\WINDOWS\System32\msxml4.dll
MSXML2.FREETHREADEDDOMDOCUMENT {F6D90F12-9C73-11D3-B32E-00C04F990BB4} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.FREETHREADEDDOMDOCUMENT.2.6 {F5078F1C-C551-11D3-89B9-0000F81FE221} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.FREETHREADEDDOMDOCUMENT.4.0 {88D969C1-F192-11D4-A65F-0040963251E5} Both C:\WINDOWS\System32\msxml4.dll
MSXML2.MXHTMLWRITER.4.0 {88D969C9-F192-11D4-A65F-0040963251E5} Apartment C:\WINDOWS\System32\msxml4.dll
MSXML2.MXNAMESPACEMANAGER.4.0 {88D969D6-F192-11D4-A65F-0040963251E5} Apartment C:\WINDOWS\System32\msxml4.dll
MSXML2.MXXMLWRITER.4.0 {88D969C8-F192-11D4-A65F-0040963251E5} Both C:\WINDOWS\System32\msxml4.dll
MSXML2.SAXATTRIBUTES.4.0 {88D969CA-F192-11D4-A65F-0040963251E5} Apartment C:\WINDOWS\System32\msxml4.dll
MSXML2.SAXXMLREADER.4.0 {7C6E29BC-8B8B-4C3D-859E-AF6CD158BE0F} Both C:\WINDOWS\System32\msxml4.dll
MSXML2.SERVERXMLHTTP {AFBA6B42-5692-48EA-8141-DC517DCF0EF1} Apartment C:\WINDOWS\SYSTEM32\MSXML3.DLL
MSXML2.SERVERXMLHTTP.4.0 {88D969C6-F192-11D4-A65F-0040963251E5} Apartment C:\WINDOWS\System32\msxml4.dll
MSXML2.XMLHTTP {F6D90F16-9C73-11D3-B32E-00C04F990BB4} Apartment C:\WINDOWS\System32\msxml2.dll
MSXML2.XMLHTTP.2.6 {F5078F1E-C551-11D3-89B9-0000F81FE221} Apartment C:\WINDOWS\System32\msxml2.dll
MSXML2.XMLHTTP.4.0 {88D969C5-F192-11D4-A65F-0040963251E5} Apartment C:\WINDOWS\System32\msxml4.dll
MSXML2.XMLPARSER {F5078F19-C551-11D3-89B9-0000F81FE221} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.XMLPARSER.2.6 {F5078F20-C551-11D3-89B9-0000F81FE221} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.XMLSCHEMACACHE {373984C9-B845-449B-91E7-45AC83036ADE} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.XMLSCHEMACACHE.2.6 {F5078F1D-C551-11D3-89B9-0000F81FE221} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.XMLSCHEMACACHE.4.0 {88D969C2-F192-11D4-A65F-0040963251E5} Both C:\WINDOWS\System32\msxml4.dll
MSXML2.XSLTEMPLATE {2933BF94-7B36-11D2-B20E-00C04F983E60} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.XSLTEMPLATE.2.6 {F5078F21-C551-11D3-89B9-0000F81FE221} Both C:\WINDOWS\System32\msxml2.dll
MSXML2.XSLTEMPLATE.4.0 {88D969C3-F192-11D4-A65F-0040963251E5} Both C:\WINDOWS\System32\msxml4.dll


Name Registry Key Key Value
MDAC Version HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\FullInstallVer 2.71.9030.0
Name Directory File Name Version Version first included Removed after
ActiveX Data Objects C:\Program Files\Common Files\System\ado\ msado15.dll 2.71.9030.0
ODBC Sql Server Driver C:\WINDOWS\System32\ sqlsrv32.dll 3.81.9041
ODBC Driver C:\WINDOWS\System32\ odbc32.dll 3.520.9041.40

 

[Robert Aldwinckle]

What I did notice was that it said that MSXML 3.0 is not installed

And that The version used by IE for .XML files is MSXML 3.0

You're right. I think that that is the most significant difference between
my report and yours. You definitely should have the module msxml3.dll

According to the WU troubleshooter (do a find for msxml3 and click on
the bottom entry) you can install the modules needed for that version
by "reinstalling the latest version of the XML parser" at that MSDN URL
I gave you.

I would try that. In fact, I'm going to try it myself anyway because
I just noticed that there is a newer service pack level for version 4.0
that the one that I have. ;o


Good luck

Robert

 

[Robert Aldwinckle]

If you experience problems attempting to use MSXML 3.0 SP4 after

removing an application that might have been using it, you can fix this
issue by repeating the registration of msxml3.dll on your system.

I thought about pointing out that approach used by the troubleshooter
but then thought that the first few lines of your report were showing that
perhaps the module wasn't even there. If that was the case just trying
to do regsvr32 commands wouldn't work but would give you cryptic error
messages. I decided that telling you to install the service pack would
result in less potential for more followup.

Glad to see you found a fix.


Robert
---


....
Robert,

I found the problem with your help in setting me in the right direction.

http://download.microsoft.com/downl...8-4828-9094-697103203a32/MSXML3SP_RelNote.htm


Thank You again for offering assistance, it was a real learning experience.

Don....

Troubleshooting Notes

There are many applications that ship MSXML 3.0. Accidentally uninstalling
any one of those applications on a Windows system could potentially
unregister the MSXML 3.0 assembly files (msxml3.dll and msxml3r.dll).
This is possible when MSXML 3.0 appears to no longer be installed or
available, but its assembly files still remain in the Windows system folder.

If you experience problems attempting to use MSXML 3.0 SP4 after
removing an application that might have been using it, you can fix this issue
by repeating the registration of msxml3.dll on your system.

To register MSXML 3.0

1. From the Start menu, click Run.
2. Enter the following command:
regsvr32 %windir%\system32\msxml3.dll
3. Click OK.

If the registration is successful, you should see a message box that reads
similar to the following:

DllRegisterServer in C:\WINDOWS\system32\msxml3.dll succeeded.

Bingo !!!!! No More Code !!!