Code 59, Code 64 and Code 87 Windows Errors

The following errors can occur in Windows:

• Win32 Error. Code: 59. An unexpected network error occurred.
• Win32 Error. Code: 64. The specified network name is no longer available.
• Win32 Error. Code: 87. The parameter is incorrect.

These errors are not caused by Accredo. They are returned by Windows to Accredo’s requests for file access, and essentially mean "I timed out waiting for the server to respond". 

These errors can be caused by one of the following:

• An interrupted connection due to network, configuration or hardware issues or a computer going to sleep.
• Cabling or wireless connection failures, or
• The server being overwhelmed with requests and therefore has begun dropping requests.

One-Off Errors

If this is a one-off error, or you know that your server connection was dropped (for example, if a server restarted, a network cable was bumped, or a wireless connection dropped out), then simply restart Accredo once the server is available and carry on.

Recurring Errors

If the errors recur, check the following:

• That your computer is not configured to sleep after a period of idle time and you are leaving Accredo running across this. When Windows puts a computer to sleep, open network connections are dropped because it is not responding to the server. This is a Windows setting and is not something Accredo has control over. When your machine wakes from sleep, Accredo wakes up and cannot survive since all its network connections have gone.
• Drive Letters mapped via Group Policy should be configured to Update rather than Replace. Replacing can cause the mapped drive to disconnect, and reconnecting can trigger Error Code 59 or 87 issues.
• Certain Windows power settings can cause your network adapter to go to sleep which will result in network errors. Ensure that the settings for Link State Power Management is set to 'Off'. You can find this in the Advanced settings for your Windows power plan. Windows Control Panel > Change Plan Settings > Change advanced power settings > PCI Express.
• ShadowProtect backup software can also cause issues by causing timeouts which can manifest as Error 59 or 64.

Intermittent Errors

If the errors are intermittent, it is likely to be a server resource or tuning issue and the following may assist:

When running across a network, Accredo needs your server to be tuned for Server Message Block (SMB) based file serving. Refer your IT support person to Microsoft's "Performance Tuning for File Servers" guidelines for your generation of Windows Server Operating System. We do not recommend changing settings to ignore Client flush requests.

Also ensure you have all Microsoft Patches and Hotfixes installed as well as having the necessary Registry settings applied for turning off problematic Opportunistic Locking (SMB1) and Client Side Caching (SMB2 and 3) on both the server and client machines. These Registry changes are made by Accredo during installation, but if machines have not been rebooted, or if Accredo has been copied, these registry changes will not have been applied. You can see full details of the Registry Data Safety Settings.

For best performance on Remote Desktop Services Systems, the Accredo Server should be installed on the Remote Desktop Host. This ensures users can directly access Accredo data using the Remote Desktop Host, rather than across the network, to give the best performance and eliminate any client side caching issues.

For this configuration, do not use mapped drive letters for Accredo on the Remote Desktop Host. Using a mapped drive letter makes requests go through the network redirector which causes intermittent problems due to a race condition (see below). You can use Subst instead of a mapped drive letter to get the same effect and this will bypass the network redirector.

If the Accredo Server and the Remote Desktop Host are on separate physical or virtual servers, ensure you are running Accredo Build 4.0.10.127 or later for all clients and add /DEFEAT=Y to the System.cfg file in the Accredo System directory to enable Oplock Defeating. Ensure all users are logged out prior to applying the switch and ensure all users are on the version 4.0.10.127 or later executable, otherwise you may get locking errors. The OpLock defeating prevents SMB2/SMB3 race conditions which occur under high network I/O load (commonly on Remote Desktop Host servers not desktops) in which Oplocks can result in data corruption.