The likely causes are: either the server is down, the network connection is lost, the configuration settings are incorrect, or the DMS and Go-Between versions do not match. First, check if you are able to connect using a web browser. If you are, the problem is likely either the configuration settings or the versions do not match. To check the version number in the Go-Between, check the configuration dialog. To check the version number in the DMS, open a web browser to the DMS and check the number in the footer. It is not necessary that the build numbers match. The Go-Between will, as well, give a warning when the version numbers do not match.

If you are not able to connect with a web browser either, it is possible that the URL has changed, that the DMS server is down, or the network is down. If it is Local Solution, if possible, try to access the DMS from the computer on which it is installed. If you do not have access to this computer, ask someone with access to try to view the DMS from a web browser launched from that computer. Someone in the firm should know the IP address of the server. If it is a Hosted Solution, you may ask OpenEngagement for assistance.

Check the version of Working Papers your are using. The Go-Between will not work with versions of Working Papers prior to 2005.00.

The Go-Between may not have been installed. Using a DOS window, navigate to the directory where the dms.dll file is located and from the command line enter: regsvr32 dms.dll. You will get a dialog box which will indicate if the Go-Between's .dll file was registered with Windows properly.

Check if the Go-Between is installed multiple times on your computer. You may use the Windows search function in the Windows Start menu to search for instances of the file dms.dll. If there are multiple installations, unregister all instances of the dms.dll, then register the correct instance. Preferably, delete all copies other than the correct one.

If you are able to search and navigate using the Go-Between but not upload or download client files, the problem is likely a security setting related to SSL certificate revocation. This error is particularly known to occur with computers using Windows 2003 SP 1. If you have a log file, you can check it for the string: 12057. This is the Microsoft error code related to this problem. If you do not have a log file, you can nevertheless try this fix if you wish.

To fix:

• Close all instances of Internet Explorer except one
• Close all instances of Working Papers
• Click on Tools -> Internet Options
• Click on the Advanced tab
• Scroll down to the Security Section (near the bottom)
• Uncheck 'Check for server revocation'
• Close Internet Explorer
• Restart Working Papers and try again