Msxml What Is It
Roxanna Fitting
Microsoft XML Core Services (MSXML) are set of services that allow applications written in JScript, VBScript, and Microsoft development tools to build Windows-native XML-based applications. It supports XML 1.0, DOM, SAX, an XSLT 1.0 processor, XML schema support including XSD and XDR, as well as other XML-related technologies.
All MSXML products are similar in that they are exposed programmatically as OLE Automation (a subset of COM) components. Developers can program against MSXML components from C, C++ or from Active Scripting languages such as JScript and VBScript. Managed .NET Interop with MSXML COM components is not supported nor recommended.[1]
As with all COM components, an MSXML object is programmatically instantiated by CLSID or ProgID. Each version of MSXML exposes its own set of CLSID's and ProgIDs. For example, to create an MSXML 6.0 DOMDocument object, which exposes the IXmlDomDocument,[2] IXmlDomDocument2,[3] and IXmlDomDocument3[4] COM interfaces, the ProgID "MSXML2.DOMDocument.6.0" must be used.
MSXML also supports version-independent ProgIDs. Version-independent ProgIDs do not have a version number associated with them. For example, "Microsoft.XMLHTTP". These ProgIDs were first introduced in MSXML 1.0, however are currently mapped to MSXML 3.0 objects and the msxml3.dll.
Different versions of MSXML support slightly different sets of functionality. For example, while MSXML 3.0 supports only XDR schemas, it does not support XSD schemas. MSXML 4.0, MSXML 5.0, and MSXML 6.0 support XSD schemas. However, MSXML 6.0 does not support XDR schemas. Support for XML Digital Signatures is provided only by MSXML 5.0. For new XML-related software development, Microsoft recommends[5] using MSXML 6.0 or its lightweight cousin, XmlLite, for native code-only projects.[6]
Tried to unistall MSXML 6 SP2 first, but nothing in Add/Remove programs applet, and Installer Cleanup Utility does not list any MSXML items on my system (XP SP3), although msxml6.dll has version 6.20.1076.0.
Hello
We are on GP 10 and using FRx 6.7 (release 6.7.5014). The report serveris together with the GP 10 (sp4) server on Windows Server 2003 SP 2 64-bit.So far the reports had been running just fine, until...
Most users were on Windows XP. However, we just recently upgradedusers' workstation to Windows 7. And for some reason I cannot get mostof the reports working for the Windows 7 users exceptone report that still can run, but the rest I get this error message:
The first error message is:
"FRx is unable to process this output request for the following reason:
C:\Windows\system32\msxml.dll could not be found.
Generating a DrillDown Viewer or XML output file requires the following:
- Microsoft Internet Explorer 6.0 or later
- MSXML 4.0 SP1 or later
It may be necessary to install (or reinstall) the component or components listed above."
I already have MSXML 4.0 SP2 and even after reinstalling it, stilldoesn't work after registering it. I'm using Internet Explorer 8 rightnow.
I copied the msxml.dll from the report server and did not fix the problem.
The FRx report is still working on the Windows 2003 server... does thismean that FRx does not work in Windows 7? There is one report that isstill working on the Windows 7 stations, is what I'm confused of right now.
Could someone please help me with this issue? Thanks in advanced for your help,
-Elizabeth
The key here, is to make sure you run the installation and service pack exe files as Administrator (right click, "run as"). Simply click OK at the end of the installation when an error comes up. Then do your service pack.
If you have any issues with this I would be happy to help out. Just shoot me a line at Rob.I...@MSXGroup.com. You can also find out about our services, support options, training classes and FREE webinars on FRx, Forecaster, Management Reporter and PerformancePoint Server at
I know this group is difficult to search but I remembered another thread about FRx and Windows 7 that I think you should look at. It might help. It has the title FRx OFSI Error - 6.7, Windows 7. The last post tag was 9-22-2010 at 12:04PM. It was one page back when I found it.
We are running a different accounting software that requires MSXML Parser 4.0. It is not used daily, but there is a feature present that depends on it (some reporting probably). Removing/unregistering it causes our accounting software to throw an error upon start about MSXML Parser 4.0 that is not present/found. As soon as you put it back, everything keeps working again.
Unregistered msxml4.dll ( regsvr32 /u msxml4.dll ) and then deleted it and the associated msxml4 files along with it after backing them up. No errors reported with the software that may have been using it. I figured it was fairly safe to do, but there is always the remote possibility doing so ends up being a mistake.
Now, Remember there are two Installations running so two identical programs will apear in the Applications list. You need to look for the one Second down the list, as the most recent apps appear at the top of the list and we want to kill the first one.
Thanks for that! It seems like it has been installed but i forgot about one more thing during the installation of Microsoft Flight Simulator X. When i try to install the game it come's up with an error which says:
I don't know why this shows up but i have an idea about what's causing it - Microsoft Visual Studio C++ 2005 maybe? Don't know if it's inappropriate for this topic but any help would certainly be appreciated!
Indeed Microsoft Flight Simulator X is an old software released back in 2006 and the team is currently working on a new game called Microsoft Flight that will be compatible with Windows 7. But Microsoft Flight Simulator X is compatible with Windows 7. Maybe my laptop is too new to be able to play this game so i guess there isn't much more that could solve the problem, in fact nothing. Anyway thanks for helping me so much!
Yesterday, Microsoft has released Security Advisory 2719615, associated to a vulnerability in Microsoft XML Core Services. We want to share more details about the issue and explain the additional workarounds available to help you protect your computers.
A vulnerability exists in Microsoft XML Core Services 3.0, 4.0, 5.0, and 6.0 that could be exploited if a user views a specially crafted webpage using Internet Explorer. The issue is triggered when MSXML attempts to access an object in memory that has not been initialized, which may corrupt memory in such a way that an attacker could execute arbitrary code in the context of the logged-on user. This class of vulnerability is exploitable by preparing both stack and heap memory with attacker-controlled data before the invalid pointer dereference.
In a web-based attack scenario, an attacker would have to host a website that contains a specially crafted web page. The vulnerability can be triggered only through the use of Active Scripting, so the following standard workarounds still apply:
We consider these, together with disabling MSXML ActiveX controls, to be too disruptive to the Internet Explorer browsing experience to be considered practical for wide adoption. At the same time, we know this vulnerability is actively exploited in the wild for targeted attacks. In such situations, we offer guidance and workarounds in a Security Advisory, in order to protect customers as fully as possibly while we prepare the necessary security update.
This ensures that it is not applied to the wrong version of msxml?.dll and that the results of the change are what were intended by the workaround. If a certain msxml?.dll does not pass all of these checks, it will not be modified.
Applying this workaround will not interfere with the installation of the final security update that will address this issue. However, applying the workaround will have a small effect on the startup time of Internet Explorer. Therefore, as you are applying the final security update, you should uninstall the workaround as it will no longer be needed. We believe this workaround would not cause any application compatibility issues, but at the same time recommend that you test it with any internal line-of-business applications before deploying it. The final security update to address this issue will be fully tested and ready for broad deployment.
You might have noticed that msxml5.dll is not covered by the previous workaround. MSXML5 is not on the pre-approved controls list and should not be used on any web pages. Internet Explorer will pop up the security bar every time a website tries to use it:
As part of Security Advisory 2719615, we are also recommending EMET as a potential mitigation for possible attacks attempting to exploit this vulnerability. The Enhanced Mitigation Experience Toolkit (EMET) is a utility that helps prevent vulnerabilities in software from successfully being exploited by applying in-box mitigations such as DEP to applications configured in EMET. We recommend to our customers to do a thorough assessment in their test environment before large scale deployment.
Shout to Fermin Serna and the Google Security Team for sharing their findings with us; to Qihoo 360 Security Center for reporting the vulnerability. Also thanks go to Bruce Dang, Elia Florio, and Matt Miller for their tireless advice.
I think your first thought about this article would be that: "oh, another tool to parse XML like MSXML". In fact, this article is based on MSXML. What I will present for you is not a general XML parser, but a generator to create a specific XML parser. The purpose of my article is not to teach you some knowledge about a grammar parsing technique, but to provide you some idea of auto code generation through an XML parser generator. XML parser may not be of any use in your programming area, but that does not matter, if you could get a fresh feeling at the end of my article, it will also help in your future exciting programming life.
4a15465005