perfectxml.com
 Basic Search  Advanced Search   
Topics Resources Free Library Software XML News About Us
  home » Focus » MSXML » KB Articles Thu, Oct 11, 2007
NEWS
MSXML 4.0 SP2 now available!

 
MSXML
Basics
DOM
SAX
XPath
XSLT
Schemas
SOM
HTTP Access
.NET
Data Islands
Ask a Question
   Past Q&As
C++ Samples
DLL/Version Info
Reference Guide
Books
KB Articles
   HOW TO
   SAMPLE
   INFO
   BUG/PRB
   FIX
   Misc.
MSXML Tips
   August 2002
   September 2002
MSXML Tools

Microsoft XML Core Services

Select KB Articles Category:
Page: 1  2  3  4  5  6  
PRB: Run-Time Error When You Use Custom Type Mapper on SoapClient

If you use a custom type mapper on the client, when you specify the Web Services Meta Language (WSML) file in the mssoapinit call to initialize the SoapClient object, you may receive an error message similar to the following:
Run-time error '-21472214005 (800401f3)':
WSDLReader:Analyzing the WSML file failed HRESULT=0x800401F3 - WSDLReader:Initializing the service SoapEmployee failed HRESULT=0x800401F3 - WSDLService:The PROGID EmpServer.clsEmpServer is invalid HRESULT=0x800401F3
where the PROGID EmpServer.clsEmpServer is the PROGID of the Component Object Model (COM) object that you are exposing through SOAP Toolkit 2.0.
PRB: Creation of Active User Object Fails After Call to BinaryRead

Site Server Membership.UserObjects in an Active Server Pages (ASP) page, for example
set usr = server.CreateObject ("Membership.UserObjects.1") use ASP Request to retrieve information from Site Server. If BinaryRead is called on the ASP Request object before this creation, the following error occurs: error 'ASP 0208 : 80020009' Cannot use generic Request collection Cannot use the generic Request collection after calling BinaryRead.
NOTE: With MSXML 3.0, IXMLDOMDocument::load can be called directly with Request object, and the load internally calls BinaryRead on Request to retrieve the XML data stream. For example: set doc = Server.CreateObject("MSXML2.DOMDOCUMENT.3.0") doc.load(Request) set usr = server.CreateObject ("Membership.UserObjects.1")
If the load is called before the creation of the UserObjects, the error described in this section occurs.
PRB: Namespace Prefixes Are Declared as FIXED Attributes in an XML DTD

The Microsoft XML (MSXML) parser does not interpret namespace prefixes that are declared as FIXED attributes in an XML Document Type Definition (DTD). If you use a FIXED value attribute in a DTD to declare a namespace prefix, and if you use the namespace prefix to qualify element or attribute names without explicitly declaring the prefix in an XML document that references the DTD, you may receive the following error message when the MSXML parser tries to load the XML:
Reference to undeclared namespace prefix: This error occurs whether you program the MSXML Document Object Model (DOM) through code or open the XML document in Microsoft Internet Explorer.
BUG: Cached XML Files Generate Unnecessary GET Requests

After an Extensible Markup Language (XML) or Extensible Stylesheet Language (XSL) document has been cached on a client computer, subsequent requests to use the file may result in an unnecessary "If-Modified-Since" GET request to the server if the file has not expired. These extra requests slow down the performance of high-scaled servers and large applications.
PRB: ISAXXMLReader::parseURL Consumes Large Amount of Memory Over HTTP

When you use code such as the following, note that the parseURL method of the SAXXMLReader object consumes an unexpectedly large amount of memory when parsing a large XML file over HTTP:
Set saxReader = CreateObject("Msxml2.SAXXMLReader.3.0")
saxReader.putFeature "server-http-request", true

saxReader.parseURL "http://localhost/big.xml"

You expect that the parseURL method would not consume much more memory than the actual size of the XML file.
PRB: "Access Denied" Error Message When Using ServerXMLHTTP to Access an Authenticated Site

When you use the ServerXMLHTTP object to access a Web site that is configured to use Integrated Windows authentication, and a valid NT User ID and password are not supplied in the call to the Open method of the ServerXMLHTTP object, you may receive the following error message:
401 - Access Denied Typically, this error indicates that the NT User ID that is used to access the Web site does not have the permissions to execute the requested HTTP operation. In such a situation, the NT User ID must be granted the required permissions for the request to succeed.
However, when you use the ServerXMLHTTP object, the error can also occur when the NT User ID (under whose credentials the ServerXMLHTTP object code is executing) has the rights that are required to execute the HTTP operation that is specified as the first parameter of the object's Open method.




BUG: XMLHTTP Fails to Send Cookies from a Client

When you send cookies from a client by using the MSXML2.XMLHTTP object, you may see that the cookies are empty when they arrive at the server.
NOTE: Usually a server sends and receives cookies. In this case, you may be submitting cookies from a client so that you do not have to reauthenticate the client.
Error Message Occurs When You Import a Web Part into a Dashboard Site

When you attempt to import a Web part into your dashboard site from an external (Internet) Web part catalog, you may receive the following error message in the browser:
An unexpected error occurred.
An error occurred while accessing the dashboard. This error may be caused by the proxy server settings for the dashboard. Contact your server administrator. If you are a server administrator, configure the proxy server settings by using the proxycfg utility. Consult the product documentation and the Readme file for more information about configuring the proxy server settings. Important: You must configure the proxy server settings for the dashboard even if you are not using a proxy server.
-2147221499
PRB: Insufficient Room for Growth in Master or Model Databases May Corrupt the sysdepends Table in the Model Database

Failure to provide sufficient disk space for database growth during the SQL Server 2000 upgrade process may corrupt the sysdepends table in the model database or may cause the process to stop responding (hang) without any informational message.
ACC2002: Requery Method Does Not Rebind Page to XML Data File

If you change data in an XML file to which a data access page is bound, requerying the page through script does not show the updated data. You may see this behavior if the page is bound at run time or by using the user interface.
ACC2002: Data Access Page That Contains Embedded XML May Open Slowly

In Access 2002, you can bind a data access page to XML embedded in the page or to an external XML file. Embedded XML is also referred to as an XML data island. If you open a page that is bound to a large XML data island, it may take a while for the page to open.
PRB: Browsing and Saving the Default MSXML XSL Stylesheet in Internet Explorer

Attempting to save the default Microsoft Extensible Markup Language (MSXML) Extensible Stylesheet Language (XSL) stylesheet after opening the stylesheet in Internet Explorer does not persist the XSL to the specified file and location. No error or informational message displays to indicate that the save operation did not succeed. Attempting to run a View Source when the XSL is displayed in the browser window causes the following informational message to appear:
The XML source file is unavailable for viewing.




PRB: ServerXMLHTTP Object Adds Content-Type Header with XML Data

When posting XML data to a Web server by passing a DOMDocument object to the send method of a ServerXMLHTTP object, a content-type header of "text/xml" is automatically added. If you set the request header before sending XML data, the content-type header sent to the Web server is "Text/xml, text/xml" instead of "Text/xml," which may cause problems.
ACC2002: When You Change the XML Location from Embedded to Data File, the Embedded XML Remains Part of the Data Access Page

By using the new properties of the data source control, you can bind a data access page to XML data that is embedded within the data access page or in a separate XML file. Embedded XML is also known as a data island. If you bind the page to an XML data island and subsequently bind the page to a separate file, the data island remains part of the page.
PRB: Load Method Fails When Loading XML File Over HTTP

When you use the Load method of either the MSXML.DOMDocument or the MSXML2.DOMDocument object to load an XML file over HTTP, the method fails with this error message:
-2146697209 - No data is available for the requested resource.
PRB: Error ClassFactory cannot supply requested class (80040111) When You Use ServerXMLHTTP Object

When you try use the ServerXMLHTTP object on a Windows 95 or Windows 98 platform, you may receive the following error message: error 80040111 ClassFactory cannot supply requested class. Reason being the ServerXMLHTTP object is not supported on the Windows 95 and Windows 98 platforms.
PRB: Application Errors Occur After You Run Xmlinst.exe on Production Servers

After you run Xmlinst.exe, applications (such as SQL Server 2000) may not operate as expected.
MSXML May Leak Memory in a Multithreaded Application

When you use Microsoft XML (MSXML) in a multithreaded application that passes Extensible Markup Language (XML) objects (such as nodes and documents) between application components, if the components are running on separate threads, the application may leak memory over time. This is indicated by a growth in private bytes in the process. To measure the private bytes of a process, use a program such Performance Monitor.

In Microsoft COM+ on Microsoft Windows 2000, this problem may also occur when you pass XML objects between components that are running on the same thread because of the marshaling that occurs between COM+ contexts




BUG: Internet Explorer Stops Responding When You Download Images

When you browse to a Web site that dynamically adds images to a page, some of those images may intermittently fail to appear. The Internet Explorer icon continues to spin for five minutes in the upper-right corner of the browser as if the browser stops responding (hangs) while it attempts to download the content.
System Does Not Respond When You Open Large XML Files in Internet Explorer

When you load a large XML file with Internet Explorer, your system performance may be slower or it may look as if your system has stopped responding. You may also receive the following error message: Your system is running low on virtual memory. Please close some applications. You can then start the system option in the Control Panel and choose the Virtual Memory button to create an additional paging file or to increase the size of your current paging file.
Page: 1  2  3  4  5  6  


  Contact Us | E-mail Us | Site Guide | About PerfectXML | Advertise ©2004 perfectxml.com. All rights reserved. | Privacy