Xerox DocuShare Drive

Release Notes for Xerox® DocuShare® Drive

DocuShare Drive Version 1.0.0 build 37

INSTALLATION

You must be an administrator on the computer to install and remove DocuShare Drive. Creating a system restore point prior to running the installer is recommended. To run the installer, use DSDriveSetup.exe on a 32-bit machine, or DSDriveSetup64.exe on a 64-bit machine. The setup program ensures that the installer runs with an approriately elevated administrator privilege.

The setup program is generated using the Microsoft IExpress self-extract technology. It supports the setup switches described in the article from below.

http://technet.microsoft.com/en-us/library/dd346761.aspx

To perform the installation silently, use the /Q switch.

If you want to pre-select a DocuShare server for auto-mapping during the installation, you need to override the default MSI launch command. To do so, use the /C switch. Here is an example.

DSDriveSetup /C:"msiexec /i DSDrive.msi /lv DSDriveInstall.log DSURL=http://www.foobar.com/docushare MAPFIRSTSERVER=1"

The above command pre-selects a DocuShare at http://www.foobar.com/docushare for automatic mapping at the end of the installation process.

If you just want to extract the MSI file, use the /T switch (followed by specification of a destination directory).

If you have customized the MSI and must run the MSI directly, start a command prompt with administrator privileges, CD to the directory of DSDrive.msi, and issue the command, msiexec /i DSDrive.msi. If the installation is not run with an elevated privilege, the installer will not be able to correctly update your machine's netwok configuration. The installation itself may complete. But, the runtime will likely malfunction.

If you are installing DocuShare Drive on a machine with DocuShare Client installed, you must disconnect all servers prior to running the installation. Also, when running the DocuShare Drive installer, make sure that the 'DocuShare Client update' feature is selected in the Custom Setup screen.

The installation requires pre-installation of Microsoft Visual Studio C++ 2008 SP1 Redistributable . DSDriveSetup does not include it. So, you must install it separately. If the target machine is 64-bit, make sure that both 32-bit (x86) and 64-bit (x64) editions of the redistributable are installed. If you have access to the DocuShare Client 6.5.x setup program, you can use that to download and install the right prerequisite library. As soon as the library finishes installing, quit the setup program, and come back to DSDriveSetup. The prerequisite is already met if the target machine has the DocuShare Client installed. The redistributables are available from these Microsoft sites.

Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)

http://www.microsoft.com/en-us/download/details.aspx?id=5582

Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)

http://www.microsoft.com/en-us/download/details.aspx?id=2092

SYSTEM REQUIREMENTS

- Microsoft Windows 7 with SP1 (32- and 64-bit) or Microsoft Windows 8.1 (64-bit).

- Microsoft Visual Studio 2008 C++ Redistributable SP1

- Microsoft Internet Explorer version 8 or higher

- 1 GB RAM on 32-bit systems; 2 GB RAM on 64-bit systems

- 20 MB free disk space for program files on 32-bit systems; 40 MB on 64-bit systems

- 100 MB free disk space for work and temporary data

- TCP/IP network connection to a DocuShare server running version 6.6.1 R2, version 6.6.1 Update 2, or higher

KNOWN ISSUES

- DocuShare Search times out and causes Explorer to raise an error, depending on the search term. Make sure that your server is version 6.6.1 with the latest service pack installed.

- 'Check in documents' stores only one of multiple files selected for check-in.

- A search result for a file in an orphan collection does not work. The file does not open when it's double clicked in the search folder.

- Manually stopping the DocuShare network redirector using the service control API may cause a hang.

This happens because the driver is still used by a user-mode library of DocuShare Drive. The driver remains locked, and is unable to terminate. To avoid the problem, make sure that the user-mode component of DocuShare Drive is not running before the stop command is issued to the driver. To terminate the user-mode library, issue the command below from a command prompt.

C:\Progra~1\Xerox\DSDrive\xdsdrive -k

- Saving a pre-locked document from within an editor application may not start a check-in dialog. Lock a file in Windows Explorer. Open it for editing. Make edits, save and exit. The file gets silently uploaded as a new version of the server file. But, you never get a check-in dialog. To interactively check in a file, make sure you select the Check Out menu item.

- On some machines, copying a large file may cause Windows Explorer to raise an invalid-parameter error.

There is a known timing issue with the default synchronous file transfer function of the DocuShare network redirector driver. The driver can be instructed to use an alternative, asynchronous transfer function. Contact DocuShare Support for instructions on how to enable the alternate function.

FAQ

- The installer does not detect the missing C/C++ runtime library on my machine.

Sometimes, the uninstaller of the runtime library does not remove a registry setting that the DocuShare Drive installer uses to determine the need for prerequisite installation. That can cause the installer to skip installing the runtime library. If you suspect that, check the registry setting of 'Install' in the keys below. If 'Install' is set to 1, change it to 0. Then, run the DocuShare Drive installer.

64-bit systems:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VC\Servicing\9.0\RED\1033]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DevDiv\VC\Servicing\9.0\RED\1033]

32-bit systems:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VC\Servicing\9.0\RED\1033]

- Can my DSClient SDK application work with the DocuShare Drive?

Yes. The user-mode library of DocuShare Drive provides SDK functions, and retains compatibility with DSClient SDK applications written for SDK version 6.5.0 or higher. The library carries version 6.6.0.

- Results in Search DocuShare do not open.

If Windows Explorer displays a security warning message instead of a found search result, you may need to modify Internet Explorer security settings. Open Internet Options of IE, go to the Security tab. Check the box, 'Include all local (intranet) sites not listed in other zones.' You may also need to use Advanced to add your DocuShare server explicitly as a local intranet site.

- A long DocuShare server name does not work. I get an error if I type it in the Network folder.

If a server name is entered in the address bar that consists of more than 43 characters, the Windows Explorer does not accept the name and raises an invalid-name error. You will not be able to use the name to access the server. An example name that causes the problem is 'XDS@imperial-hv.na.xerox.org_38080~docushare'. It is for a server URL of http://imperial-hv.na.xerox.org:38080/docushare. The name is 44 characters long and is one character too long. The name cannot be used to address the server in Explorer. To work around the problem, create a short alias for the host name. To create an alias, define a setting in the registry key below that assigns an alias name to a full host name. A sample setting for the example server name is shown below. The name on the right-hand side of the equal sign is the alias. The left-hand side is the complete host name.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\XDSMRX\hostaliases]

"imperial-hv.na.xerox.org"="imperial"

Using the above alias setting, the name-length problem can be overcome. The above example server name can now be shortened to this.

XDS@imperial_38080~docushare

If the full server name ends with a directory name of docushare, there is another way to shorten the name. Replace the 'docushare' directory name with the predefined directory abbreviation of '~ds'. Here is a shortened form of the example server name that makes the replacement.

XDS@imperial-hv.na.xerox.org_38080~~ds

The shortened name is 39 characters long. It's within the 43-character limit, and so can be used to access the server in Explorer.

- I cannot map a SiteMinder-protected DocuShare server.

DocuShare Drive does not support SiteMinder-based authentication.

- Adobe Reader does not open a PDF. Why?

The behavior depends on the viewer's configuration. If you have this problem, run Reader, and uncheck the Enable Protected Mode at startup under the General tab in the Preferences dialog of Reader.

- A file continues to be visible in a web browser after it is hidden in Windows Explorer. Why?

The hidden file attribute is meaningful only for Windows. The DocuShare server does not support the Windows file attribute.

ADDITIONAL LICENSE INFORMATION

DocuShare Drive uses the OpenSSL library (version 1.0.1g). The OpenSSL and SSLeay licenses shown below apply.

/* ====================================================================

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

Original SSLeay License

-----------------------

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

Windows 7, Windows 8, Windows 8.1, Windows 2008, Windows 2012, Windows Explorer, Internet Explorer, and Visual Studio are either trademarks or registered trademarks of Microsoft Corporation.