This article has been archived. It is offered "as is" and will no longer be updated.
Applications that use the Microsoft XML Parser (MSXML) Document Object Model (DOM) or the XML classes in the Microsoft .NET Framework experience a slow and steady increase in handle usage when the applications are opening XML files from XML Web services. This problem may exhaust process resources and cause an error or an out-of-memory condition. The program must be restarted to reclaim the lost handles. This problem occurs on computers that have Microsoft Office 2003 installed. The problem does not occur on computers that have earlier versions of Microsoft Office installed.
This problem is caused by a leak of registry key handles in a client-side MIME protocol filter for XML files that are returned from XML Web services. The Microsoft Office XML MIME filter (Msoxmlmf.dll) is a registered MIME protocol handler. Msoxmlmf.dll can load indirectly in any application that uses the MSXML to parse XML data from an XML Web service. The filter is used by the Wininet library component and the Urlmon library component to identify XML files that are associated with Office 2003. One registry key handle is leaked every time that the filter object is created. The filter object is typically created one time per session. However, services that destroy and re-create repeated XMLHttpRequest objects and that parse the resulting XML may experience conditions that cause a new session to be created for every request. When a new session is created for every request, a slow leak of registry key handles occurs.
Clients can remove the filter to avoid the leak if the problem is so serious that it causes application errors in other processes. To remove the filter, follow these steps:
Verify that the Msoxmlmf.dll filter is installed in the Office shared folder. The following is the default location for this folder: