Error Message When You Try to Dial a Connection: "Svchost.exe Has Generated Errors and Will Be Closed by Windows" (319161)



The information in this article applies to:

  • Microsoft Windows 2000 Professional
  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition
  • Microsoft Windows Small Business Server 2003, Premium Edition
  • Microsoft Windows Small Business Server 2003, Standard Edition

This article was previously published under Q319161
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 try to open a dial-up networking connection, you may receive the following error message:
Svchost.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log will be created.

CAUSE

This behavior can occur if a version of Novell GroupWise that contains the Gwtps1.dll file with a date earlier than July, 2000, is installed on your computer.

The early versions of the Gwtps1.dll file may corrupt the Windows dial-up networking registry keys. This has been corrected in the GroupWise Enhancement Pack Support Pack 2 client software.

This corruption occurs because the GroupWise client expects the dial-up networking registry keys to list the various dialing locations in the same manner as that of Microsoft Windows 95 and Microsoft Windows 98. However, the listing protocol for registry keys related to dialing locations is different in Windows 2000 or Windows Server 2003 from that in Windows 95 or Windows 98. In Windows 95 or Windows 98, the listing for dialing locations start at Location0 -- for example, Location0, Location1, and so on. In Windows 2000, dialing-location listings start at Location1 -- for example, Location1, Location2, and so on.

RESOLUTION

To resolve this issue, follow these steps.

NOTE: After you follow these steps, you may have to re-create many of your dialing locations.

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.
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. In Registry Editor, expand the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Locations

  4. On the Registry menu, click Export Registry File.
  5. In the File name box, type locations, and then click Save.

    NOTE: You can restore this registry subkey by double-clicking the Locations.reg file that you saved.
  6. Under the Locations subkey, delete all Locationx folders (where x is a number) except for Location1 and Location2. For example, if the Locations registry subkey listing is similar to the following
     -Locations
       |
       |-- Location1
       |-- Location2
       |-- Location3
       |-- Location4
    						
    delete the Location3 and Location4 subkeys.

    To delete a subkey, right-click the Locationx folder, and then click Delete. Click Yes to confirm the deletion.
  7. Rename the Location1 registry subkey as Location0 (zero). To rename a subkey, right-click it, and then click Rename.
  8. Rename the Location2 registry subkey as Location1.

    NOTE: The Locations subkey should appear as follows:
     -Locations
       |
       |-- Location0
       |-- Location1
    					
  9. Click the Locations registry subkey.
  10. In the right pane of the Registry Editor window, right-click CurrentID, and then click Modify. In the Value data box, type 1, and then click OK.
  11. Right-click LocationListVersion, and then click Modify. In the Value data box, type 2, and then click OK.
  12. Right-click NextID, and then click Modify. In the Value data box, type 4, and then click OK.
  13. Right-click NumEntries (if it is present), and then click Delete. Click Yes to confirm the deletion.
  14. On the Edit menu, point to New, and then click DWORD Value.
  15. Type NumEntries, and then press ENTER.
  16. Right-click NumEntries, and then click Modify. In the Value data box, type 2, and then click OK.
  17. In the left pane of the Registry Editor window, expand the Location1 subkey that is under Locations.
  18. If the AreaCodeRules subkey is not listed under Location1, follow these steps:
    1. Click the Location1 subkey (to select it if it is not already selected).
    2. On the Edit menu, point to New, and then click Key.
    3. Type AreaCodeRules, and then press ENTER.
  19. Quit Registry Editor.
  20. Restart the computer.

MORE INFORMATION

Contact Novell to obtain GroupWise 5.5 Enhancement Pack Service Pack 2 (G55esp2.exe for English only or G55esp2m.exe for multilingual).

For information about how to contact Novell, Inc., click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:

65416 Hardware and Software Third-Party Vendor Contact List, A-K

60781 Hardware and Software Third-Party Vendor Contact List, L-P

60782 Hardware and Software Third-Party Vendor Contact List, Q-Z

For additional information about this issue, browse to the following Novell Web site: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Modification Type:MajorLast Reviewed:12/19/2003
Keywords:kberrmsg kbprb KB319161