ACC97: Internet Synchronization Fails with "Internet Is Very Slow" Error

ID: Q222150

The information in this article applies to:

Microsoft Access 97

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multiuser skills.

When you try to perform an Internet synchronization, you may receive the following error message:

Either the Internet is very slow OR there is some problem in the replication manager setup on the internet server machine.

CAUSE

You have installed either Microsoft Internet Explorer 5 or another Microsoft product that includes Internet Explorer 5 onto your Internet Server computer. The release version of Internet Explorer 5 includes a version of the file Wininet.dll that is incompatible with Microsoft Jet Internet synchronization.

-or-

You may also see this error if you tried to initiate an Internet synchronization from a Jet database that is located on the same computer as your Internet server. For additional information about this issue, please see the following article in the Microsoft Knowledge Base:

Q171949 ODE97: Can't Synchronize Over Internet to Same Internet Server

-or-

You are using IIS 4.0 installed on Terminal Server 4.0 for use as your Internet server. IIS 4.0 performance suffers when installed to Terminal Server.

RESOLUTION

You can solve this problem by forcing the Internet Server to use machine level proxy settings instead of user level. To do this, you need to add a value to the Windows Registry as follows.

WARNING: This workaround had not been fully tested. The effect that modifying this key will have on other internet application is unknown and may lead to unexpected results.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

Open the Registry Editor. (regedit.exe)

Using the editor, move to the following key in the registry.


    HKEY_LOCAL_MACHINE\ 
       Software\ 
          Microsoft\ 
             Windows\ 
                Current Version\ 
                   Internet Settings\

On the Edit menu, point to New and click DWORD.

Change the new value inserted to ProxySettingsPerUser and leave it set to the default value of zero (0).

Close the Registry Editor to save the change.

NOTE: The proxy settings are not automatically migrated from one registry key to another, so after you add this key to your server, you will have to manually create the proxy settings for Internet Explorer again.

You can use the Internet Explorer Administration Kit (IEAK) to create a custom setup that will automatically create this registry key during the installation of Internet Explorer 5.0. For more information about Per User versus Per System proxy settings, see the documentation that comes with the IEAK.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

When you install Internet Explorer 5.0, the proxy settings are installed Per User by default and are stored in the HKey_Current_User tree of the registry. During Internet Synchronization, the Jet Synchronizer on the Internet Server performs an FTP copy from the Internet dropbox to the Windows Temp directory. Because this operation is happening all within the same machine, Jet attempts to get these settings from wininet.dll while logged in as the System, not as a User. Because of this, Jet is denied access to the HKCU tree and the FTP copy fails. After this failure, an error is returned to the client and the synchronization process is terminated.

Additional query words: pra synch replication fail FTP

Keywords : kbdta RplGen
Version : WINDOWS:97
Platform : WINDOWS
Issue type : kbbug