Microsoft KB Archive/188952

= "Internal Error Occurred" Error Message Using Internet Explorer =

Article ID: 188952

Article Last Modified on 1/23/2007

-

APPLIES TO


 * Microsoft Windows 98 Standard Edition
 * Microsoft Internet Explorer 1.0
 * Microsoft Internet Explorer 2.0
 * Microsoft Internet Explorer 3.0
 * Microsoft Internet Explorer 3.01
 * Microsoft Internet Explorer 3.02
 * Microsoft Internet Explorer 4.0 128-Bit Edition
 * Microsoft Internet Explorer 4.01 128-Bit Edition
 * Microsoft Internet Explorer 5.0
 * Microsoft Internet Explorer 5.01
 * Microsoft Internet Explorer 5.5
 * Microsoft Internet Explorer 3.2
 * Microsoft Internet Explorer 4.0 128-Bit Edition

-



This article was previously published under Q188952



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
When you are using Internet Explorer over a dial-up connection, the following error message may appear when you attempt to view a Web site:

Internet Explorer cannot open the Internet site. An internal error occurred in the Windows Internet Extensions.

When you click OK, the "Navigation Canceled" page appears in Internet Explorer.



CAUSE
This behavior can occur for any of the following reasons:
 * If you start Net.Medic 1.x by VitalSigns Software after you establish a dial-up connection but before you start Internet Explorer.
 * If the incorrect version of the Wsock32.dll file is installed on your computer.
 * There is a second copy of the Wsock32.dll file in the root folder.
 * The Winsock 2.0 Update is not properly installed on your computer.
 * The Winsock2 key in the registry is damaged.
 * There are multiple copies of the Winsock.dll file on the computer.
 * TCP/IP is not installed.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue, use the appropriate method:

Using Net.Medic

 * 1) Restart the computer. When you see the Windows 95 or Windows 98 startup screen, press and hold down the SHIFT key for the duration of Windows startup.
 * 2) If you are prompted for a user name and password during startup, release the SHIFT key and enter your logon information normally. Before you click OK, press and hold down the SHIFT key once again.
 * 3) Once you have verified that Net.Medic did not start, connect to the Internet and download the update from VitalSigns Software's Web site.

Incorrect Version of the Wsock32.dll File
 Click Start, click Shut Down, click "Restart the computer in MS-DOS mode," and then click Yes or OK. At the MS-DOS prompt, type the following command, and then press ENTER

drive:

where drive: is the letter of the drive on which Windows is installed. For example, if Windows is installed on drive C, type c:. Type the following commands, pressing ENTER after each command:

'''cd\windows\system

ren wsock32.dll wsock32.old

exit'''

 Extract a new copy of the Wsock32.dll file to the Windows\System folder. If you are using Windows 95, you can extract the Wsock32.dll file from the following locations:

 The Win95_11.cab cabinet file on the Windows 95 CD-ROM The Win95_12.cab cabinet file on the original Windows 95 DMF disks</li> The Win95_19.cab cabinet file on the original Windows 95 non-DMF disks</li> The Win95_18.cab cabinet file on the Windows 95 OEM Service Release 2 CD-ROM</li></ul>

For information about using the Extract tool, please see the following article in the Microsoft Knowledge Base:

129605 How to Extract Original Compressed Windows Files

If you are using Windows 98, you can extract the Wsock32.dll file using the System File Checker tool. For more information about using the System File Checker tool, please see "System File Checker Tool" section of the following article in the Microsoft Knowledge Base:

129605 How to Extract Original Compressed Windows Files

</li> Restart your computer normally.</li></ol>

Second Copy of Wsock32.dll in Root Folder
To resolve this issue, rename the Wsock32.dll file in the root folder to Wsock32.old, and then restart your computer. For information about renaming a file, click Start, click Help, click the Index tab, type renaming, and then double-click the "Renaming files" topic.

Winsock 2.0 Update Is Not Properly Installed
Remove the Winsock update by using the Ws2bakup.bat file. For additional information, please see the following article in the Microsoft Knowledge Base:

191064 Error Messages When Running TCP/IP-Based Utilities or Programs

The Winsock2 Key in the Registry Is Damaged
<ol> Uninstall Dial-Up Networking.</li> Using Regedit, remove the following key:

HKEY_Local_Machine\System\CurrentControlSet\Services\Winsock2

</li> After removing the key, reinstall Dial-Up Networking.</li></ol>

Multiple Copies of the Winsock.dll File on the Computer

 * 1) Click Start, point to Find, and then click Files or Folders.
 * 2) In the Named box, type winsock.dll.
 * 3) In the Look In box, click Local hard drives.
 * 4) Click Find Now.
 * 5) Right-click a Winsock.dll file that is not in the Windows folder, and then click Delete. Repeat for each extra copy of the Winsock.dll file that is not in the Windows folder.

TCP/IP Is Not Installed
Install TCP/IP:
 * 1) Click Start, point to Settings, and then click Control Panel.
 * 2) Double-click Network.
 * 3) Click Add, click Protocol, and then click Add.
 * 4) In the Manufacturers box, click Microsoft. In the Network Protocols box, click TCP/IP, and then click OK.
 * 5) Click OK, and then click Yes when you are prompted to restart your computer.

<div class="status_section">

STATUS
VitalSigns Software has confirmed this to be a problem with Net.Medic version 1.x.

<div class="moreinformation_section">

MORE INFORMATION
The third-party product discussed in this article is manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Microsoft in no way guarantees the accuracy of this third-party contact information.

Additional query words: net medic browse

Keywords: kberrmsg kbprb kb3rdparty KB188952

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.