Issue
After a server was upgraded users could not access the DocuShare Server through their mapped Server.
The following error is displayed:
WSATIMEDOUT error – Attempt to connect timed out
DocuShare Windows Client (DSClient) logs display the following:
14:02:47 Sent
14:04:47 HttpRequestTimerProc: request timed out
Note: DocuShare was running fine. No backlog in the index and no Background jobs and no other errors.
The Client was uninstalled on 2 stations.
After restarting DocuShare, it was possible to map the Server in the Client once. After that, we were no longer able to map the Server or connect to the existing Mapped server.
Reason / Possible Cause
The Webdav.properties file may be corrupt.
Solution
1. Verify that the WebDAV service is running.
a. Open a Command Prompt window.
b. Change into the \bin directory.
c. Type dsservice report and press Enter.
d. Verify that the subcomponent webdav is in ReadWrite/Running state.
Note: If WebDAV is not running check to make sure the \tomcat\temp exists and that permission to the directory has been granted.
Option 1:
i. Restore the \config\webDAV.properties file from a backup before the corruption occurred.
Where is replaced with the installation directory for DocuShare. The default installation path is C:\Xerox\Docushare. Depending on your installation environment the path may vary.
ii. Restart DocuShare.
Option 2:
i. Move the corrupted or damaged WebDAV.properties file into a temp folder.
ii. Restart DocuShare.
iii. This will create a new WebDAV.properties file automatically.
Note: When there is a problem with the WebDAV service. This requires further troubleshooting by the DocuShare Technical Support Team to determine why the WebDAV service is not starting.
2. Re-map the server in the DocuShare Windows Client (DSClient).
Solution Published: September 30th, 2013
Solution ID: 1381