Knowledgebase
Client Not Connecting To The Server
Posted by Ketul Patel on 05 September 2019 09:04 AM

A Client connection to the server can fail due to the following reasons.

  1. A firewall on the server side is blocking connections to the Docsvault background service. Docsvault adds all necessary
    exceptions to the Windows Firewall during installation. However, if you are using a third-party firewall you need to add
    exceptions for the following:

    Docsvault Client side:

    dvClient.exe (by default located at C:\Program Files\Docsvault SB\Client\)

    Docsvault Server side:

    dvServer.exe (by default located at C:\Program Files\Docsvault SB\Server\)
    sqlservr.exe (by default located at C:\Program Files\Microsoft SQL Server\MSSQL10_50.DOCSVAULT\MSSQL\Binn\
    (Note: Replace MSSQL10_50.DOCSVAULT by your actual SQL instance folder if you used your own    SQL server to host Docsvault db)
     
    sqlbrowser.exe (by default located at "C:\Program Files\Microsoft SQL Server\<90 or 100>\Shared\"


  2. The background Docsvault and/or SQL server services are not running on the server-side for some reason. (Note: If you can open
    up the Docsvault Server Manager and see your Docsvault services running under the "Services" node skip this point.
    )

  3. The server name specified on the client-side is not reachable because of a network issue or the specified server IP address has changed.

If you lost client connectivity because you changed the hostname of the server machine, please contact Docsvault Support for further help on this.