Microsoft KB 293623 for IE

 

This article was previously published under Q293623

Important This article discusses a very specific Internet Explorer crash in older versions of the script debugger (Pdm.dll) that was included with Office 2000 and Visual Studio 6 (pre-SP3 version). If you view the error report details listed in the "Symptoms" section, and Pdm.dll version 6.0.0.8169 is not listed under Module Name, then this article does not apply to you.
:

You receive the following error message in Windows Explorer, Internet Explorer, or MSN Explorer:

Microsoft Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience.

In the error message, click the click here link at the bottom of the message box. For this particular error, the following error signature information is displayed:

Program Name   Program Version   Module Name   Module Version   Offset
   ------------------------------------------------------------------------
   Explorer.exe   various           Pdm.dll       6.0.0.8169       0001259d
   Iexplore.exe   various           Pdm.dll       6.0.0.8169       0001259d
   Netdocs.exe    various           Pdm.dll       6.0.0.8169       0001259d
   Msn6.exe       various           Pdm.dll       6.0.0.8169       0001259d

If your error signature information does not match this one, this article does not apply to you.

This error message occurs when the Pdm.dll file is out of date. 

This resolution requires you either to disable script debugging or to update the Pdm.dll file. If you must have the script debugging capability, you have to update the Pdm.dll file. To update your version of the Pdm.dll file, go to the "Download the updates to the Pdm.dll from the product update Web site" section. Otherwise, to avoid this error, disable script debugging in Internet Explorer. If you are running Windows XP, use Guided Help to disable script debugging. If you are running any other operating system, go to the "Manually disable script debugging" section.

Manually disable script debugging

This resolution can be used for all operating systems. If you do not want to disable script debugging, go to the "Download the updates to the Pdm.dll from the product update Web site" section.

To manually disable script debugging in Internet Explorer, follow these steps:

1. Start Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Advanced tab, under the Browsing section, click to select the Disable script debugging (Internet Explorer) check box and the Disable script debugging (Other) check box if it is present.
4. Click OK, and then restart your computer.

If these steps resolved the error message, you are finished.

If these steps did not resolve the error message, go to the "Download the updates to the Pdm.dll from the product update Web site" section.

Download the updates to the Pdm.dll from the product update Web site

This resolution can be used for all operating systems except Windows 98 and Windows Millennium Edition (Me). Use this resolution if you must have the script debugging capability. To repair and use script debugging, you have to update the Pdm.dll file. To update the Pdm.dll file, install the appropriate upgrades that are described in this section.

Note If you are running Windows 98 or Windows Millennium Edition (Me), the following upgrades do not install an updated version of the Pdm.dll file. The only resolution available to you is to upgrade your operating system.

If you are running Microsoft Office 2000, upgrade to Microsoft Office 2000 Service Release 1a (SR-1a). To download this upgrade, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=AF6C8D03-7633-45B4-AB96-795EE656F2A2&displaylang=EN (http://www.microsoft.com/downloads/details.aspx?FamilyID=AF6C8D03-7633-45B4-AB96-795EE656F2A2&displaylang=EN)

If you are running Microsoft Visual Studio 6.0, upgrade to Microsoft Visual Studio 6.0 Service Pack 5 (SP5) or a later version. To download this upgrade, visit the following Microsoft Web site, click the Service Packs link, and then click the service pack version that you want to download:

http://msdn2.microsoft.com/en-us/vstudio/aa718353.aspx (http://msdn2.microsoft.com/en-us/vstudio/aa718353.aspx)

If you are running the Microsoft Script Debugger in Windows 2000, Windows NT 4.0, Windows Server 2003, or Windows XP, upgrade to a newer version.

Note Although the Script Debugger upgrade is available for these operating systems, it is no longer supported. You can still download and use this upgrade.

To download this upgrade or for more information, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en)

If these updates resolve the error message, you are finished.

If you still receive the error message after you download and install these updates, go to the “Next Steps” section for information about how to contact Support.

If the steps in this article did not resolve the error message, you might want to ask someone you know for help, or, you can also use the Microsoft Customer Support Services Web site to find other solutions. Some services that the Microsoft Customer Support Services Web site provides include the following:

• Searchable Knowledge Base (http://support.microsoft.com/search/?adv=1) : Search technical support information and self-help tools for Microsoft products.
• Solution Centers (http://support.microsoft.com/select/?target=hub) : View product-specific frequently asked questions and support highlights.
• Microsoft Customer Support Newsgroups (http://www.microsoft.com/communities/newsgroups/default.mspx) : Contact counterparts, peers, and Microsoft Most Valuable Professionals (MVPs).
• Other Support Options (http://support.microsoft.com/default.aspx?pr=csshome) : Use the Web to ask a question, contact Microsoft Customer Support Services, or provide feedback.

If you continue to have questions after you use these Microsoft Web sites or if you cannot find a solution on the Microsoft Support Services Web site, click the following link to contact