FIX: Application fails because MSXML 3.0 SP5 changes dispatch IDs for the IXMLDOMSchemaCollection interface

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

SUMMARY

When an application uses early-bound COM IDispatch object dispatch IDs (DispIDs) for the MSXML 3.0 IXMLDOMSchemaCollection interface when MSXML 3.0 Service Pack 5 (SP5) is installed, the application fails.

The problem occurs because MSXML 3.0 SP5 changed dispatch IDs for methods in the IXMLDOMSchemaCollection interface.

You can resolve this problem by applying the hotfix, or you can work around the problem by rewriting the application so that it does not use early-bound dispatch IDs.

Back to the top

SYMPTOMS

An application that uses early-bound COM IDispatch object dispatch IDs (DispIDs) for the MSXML 3.0 IXMLDOMSchemaCollection interface fails when MSXML 3.0 Service Pack 5 (SP5) is installed on the computer.

Back to the top

CAUSE

MSXML 3.0 SP5 changed the following IDispatch object dispatch IDs for the following methods of the IXMLDOMSchemaCollection interface:

Collapse this tableExpand this table

Method	SP5 DispID	Correct DispID
add	0x00000002	0x00000003
get	0x00000003	0x00000004
remove	0x00000004	0x00000005
length	0x00000005	0x00000006
addCollection	0x00000006	0x00000008

Any application that is compiled with early-bound dispatch IDs for the MSXML 3.0 IXMLDOMSchemaCollection interface calls the wrong method because MSXML 3.0 SP5 has changed the method values. Typically, this behavior causes the application to fail because the arguments to the function and to the returned result are incorrect.

Back to the top

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must install MSXML 3.0 SP5 on your computer before you apply the hotfix. To download MSXML 3.0 SP5, visit the following Microsoft Download Center Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=4a3ad088-a893-4f0b-a932-5e024e74519f&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=4a3ad088-a893-4f0b-a932-5e024e74519f&DisplayLang=en)

Restart information

You do not have to restart your computer after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date      Time   Version      Size   File name
   ----------------------------------------------
   02-Sep-2004  22:10  8.50.2163.0     1,189,888  Msxml3.dll

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Back to the top

WORKAROUND

To work around this problem, rewrite the application so that it does not use early-bound dispatch IDs.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

MORE INFORMATION

Most of the applications that use MSXML 3.0 are not affected by this dispatch ID change. Most MSXML 3.0 applications either call the GetIdsOfNames method to dynamically determine the dispatch ID of the interface method at runtime, or they bind directly to the MSXML 3.0 COM interfaces.

Applications that call the GetIdsOfNames method to obtain the dispatch ID of the method at runtime are not affected. For example, using MSXML 3.0 inside an ASP page or inside Visual Basic script will not be affected by this change. This is because all scripting languages use the GetIdsOfNames method to obtain the dispatch ID of the method at runtime. Similarly, applications that bind directly to the MSXML 3.0 COM interfaces are not affected. For example Visual Basic applications that use early binding with MSXML 3.0 and C++ applications that use direct COM interface pointers with MSXML 3.0 are not affected. Only applications that are compiled with early-bound dispatch IDs for the MSXML 3.0 IXMLDOMSchemaCollection interface are affected by this change.

Back to the top