GlobalSCAPE Knowledge Base » Knowledgebase » WAFS and CDP

Section 508 Compliance - Voluntary Product Accessibility

GlobalSCAPE 5 — Tue, 30 Apr 2013 09:56:21 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

All GlobalSCAPE products, all versions

DISCUSSION

The attached PDF provides information regarding Section 508 Compliance Voluntary Product Accessibility.

For more information about Section 508 compliance, refer to http://www.section508.gov/.

Officially Supported Products and EOL Dates

GlobalSCAPE Support 1 — Wed, 20 Mar 2013 08:24:24 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

All Products

SUPPORTED PRODUCTS

Technical support is provided in accordance with the GlobalSCAPE End of Life (EOL) and Support Life Policy. The following products are supported to the extent specified. Products not listed are no longer supported.

FULL SUPPORT (Provided from the time of GA release until the End of Life or EOL² date.)

EFT Server 6.5 (GA release was Feb. 15, 2013)
EFT Server Enterprise 6.5 (GA release was Feb. 15, 2013)
Mail Express 3.3 (GA release was Feb. 15, 2013)
WAFS and CDP 4.1 (GA release was Oct. 29, 2012)
WAFS 3.7.1.0712 (GA release was Jul. 21, 2010)
CuteFTP Mac Professional 3.1.2 (GA release was Nov. 23, 2011)
DMZ Gateway 3.3 (GA release was Feb. 15, 2013)
CuteFTP Professional 9.0 (GA release was Nov. 27, 2012)

FULL SUPPORT (Wind-down Period¹) (During the Wind-down Period, for Cases that are not Severity One Issues, GlobalSCAPE will typically either (i) provide an existing Bug Fix, (ii) address the issue through a regularly scheduled Maintenance Release to the current Major Release of the Licensed Software product for which EOL has not occurred, or (iii) delay resolution and determine whether it will address the issue in its normal development of future Releases. The Wind-down Period extends 6 months maximum after EOL². )

CuteFTP Professional 8.3.4 (EOL was November 27, 2012, Full Support (Wind-down period) ends May 27, 2013³)
CuteFTP Home 8.3.4 (EOL was November 27, 2012, Full Support (Wind-down period) ends May 27, 2013³)
CuteFTP Lite 8.3.4 (EOL was November 27, 2012, Full Support (Wind-down period) ends May 27, 2013³)
Mail Express 3.2 (EOL was Feb. 15, 2013, Full Support (Wind-down period) ends Aug. 15, 2013³.)
EFT Server 6.4.10 (EOL release was Feb. 15, 2013, Full Support (Wind-down Period) ends August. 15, 2013³.)
EFT Server Enterprise 6.4.10 (EOL release was Feb. 15, 2013, Full Support (Wind-down Period) ends Aug. 15, 2013³.)
DMZ Gateway 3.2 (EOL release was Feb. 15, 2013, Full Support (Wind-down Period) ends Aug. 15, 2013³.)

PARTIAL SUPPORT (With Partial Support, our technical support engineers provide customers with known Bug Fixes, existing Maintenance Releases, or access to online self-help resources in response to requests for assistance. Partial Support will be subject to the availability of resources and may be limited as GlobalSCAPE determines in its sole discretion. The Partial Support period extends 12 months after GA Date⁴ or 6 months after wind-down period, whichever is greater. )

EFT Server 6.4.3 (Wind-down Period) ended Jan. 12, 2013 - EOSL⁵ will be Jul. 31, 2013.)
EFT Server Enterprise 6.4.3 (Wind-down Period) ended Jan. 12, 2013 - EOSL⁵ will be Jul. 31, 2013.)
EFT Server 6.4 (Wind-down Period) ended Sep. 28, 2012 - EOSL⁵ will be Mar. 28, 2013.)
EFT Server Enterprise 6.4 (Wind-down Period) ended Sep. 28, 2012 - EOSL⁵ will be Mar. 28, 2013.)

For more information about Support Levels or Support Periods, please browse to the GlobalSCAPE End of Life (EOL) and Support Life Policy.

¹The Wind-down Period is the period (6-months maximum) immediately following End of Life, or EOL.

²End of Life, or EOL, for any Major Release and its Maintenance Releases shall be the date of the release of the subsequent Major Release.

³Or earlier in the case of an expedited Wind-down Period which is defined in the GlobalSCAPE End of Life and Support Life Policy.

⁴ The GA Date is the date when a new Major Release is made generally available commercially.

⁵ End of Support Life, or EOSL, means when GlobalSCAPE ceases providing Full or Partial Support for a particular Licensed Software product.

Using Robocopy with WAFS

GlobalSCAPE 5 — Mon, 12 Nov 2012 08:36:38 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS/CDP

DISCUSSION

Microsoft Robocopy, included with the Microsoft Windows Server^® 2003 Resource Kit, is a utility for copying data. Robocopy does not have some of the common limitations of Windows Explorer or a Command prompt.

WAFS customers often use the following Robocopy switches:

/E = copy subdirectories, including Empty ones
/V = produce Verbose output, showing skipped files
/B = copy files in Backup mode
/R:n = number of Retries on failed copies; default 1 million
/W:n = Wait time between retries; default is 30 seconds
/NP = No Progress - don't display % copied
/LOG:file = output status to LOG file (overwrite existing log). e.g., /LOG:wafs.txt writes to wafs.txt
/TEE = output to console window, as well as the log file
/FP = include Full Pathname of files in the output
/DCOPY:T :: COPY Directory Timestamps. [Only for use with Windows 2008 R2 and Windows 7]
/XO :: exclude older files
/MT:n = copy using multithreading; n is the number of threads up to 125 [Only for use with Windows 2008 R2 and Windows 7]

Microsoft's Technet has a Robocopy description here: http://technet.microsoft.com/en-us/magazine/2006.11.utilityspotlight.aspx.

Wikipedia provides instructions on how to use Robocopy at http://en.wikipedia.org/wiki/Robocopy.

A list of switches is available at http://technet.microsoft.com/en-us/library/cc733145(WS.10).aspx.

How do I upgrade WAFS/CDP in a Windows Cluster?

GlobalSCAPE 5 — Wed, 31 Oct 2012 08:22:19 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS/CDP v3.7.x and earlier
For WAFS v4.x and later, refer to http://help.globalscape.com/help/wafs4/upgrading_wafs_in_a_cluster.htm.

QUESTION

How do I upgrade WAFS/CDP in a Windows Cluster?

This article describes how to upgrade the WAFS/CDP Server and Agents on Microsoft Windows Cluster platforms such as Advanced Servers and Datacenter Servers.

Please read the following important information before continuing:

To ensure a successful upgrade, review the entire procedure before starting, and follow the procedures in order, as described.
If you are unsure of any steps, please contact GlobalSCAPE Technical Support for assistance.
These instructions assume that the initial clustered setup was performed as described in "Setup for Windows Cluster" in the WAFS/CDP online help.
To avoid conflicts, perform the upgrades outside of production hours.
The Avcstuff directory is a hidden directory, so you will need to show hidden files and folders in order to see the directory.

To display hidden files and folders

Click Start, point to Settings, and then click Control Panel.
Double-click Folder Options.
On the View tab, under Hidden files and folders, click Show hidden files and folders, then click OK.

Step 1: Upgrade the Server Cluster

To upgrade the WAFS/CDP Server in a cluster

On the WAF/CDP Server, bring the Server Resource offline.
Run the WAFS/CDP upgrade executable on the Server's primary node.
Run the WAFS/CDP upgrade executable on the Server's secondary node.

The upgrade is complete on the Server.

Step 2: Upgrade the Agent Cluster

During the cluster setup, you chose the primary and secondary nodes to determine which computer would hold the Avcstuff directory locally on the C: drive, and which computer would hold the Avcstuff directory in the cluster.

To upgrade the WAFS/CDP Agent in a cluster

Before starting the upgrade of the Agent, copy the Avcstuff directory from the cluster drive to the C drive of the primary node.
In the Cluster Manager, verify that the Agent Resource is offline.
Run the WAFS/CDP upgrade executable on the Agent's primary node.

When prompted to restart the computer, DO NOT RESTART.

The C:\Avcstuff directory is now upgraded on the Agent's primary node.

Copy the now upgraded C:\Avcstuff directory and paste it over the cluster drive's copy of Avcstuff. (For example, F:\Avcstuff.)
After the copy/paste is complete, restart the Agent's primary node computer and allow the system to start as normal.

At this point, the primary node is upgraded and should be running its initialization scan. You should still have an Avcstuff directory in the root of C: on the Agent's primary node.

After the primary node is restarted and scanned, compare its version of the Avcstuff directory to the local version of the Avcstuff directory. If for some reason your Agent did not start correctly or files are the wrong versions, verify that you performed the steps above correctly.
(Note: For easier future upgrades, you can rename the Avcstuff directory.)
With the Agent Service offline, move the cluster group to the secondary node.
Run the WAFS/CDP upgrade executable on the Agent and allow it to run completely.
When you are prompted to reboot the computer, do so.
Bring the Agent Service back online in the Cluster Manager.

WAFS v4.x Antivirus Settings

GlobalSCAPE 5 — Wed, 15 Aug 2012 03:20:16 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS version 4.0 and later

For WAFS v3.7.1 and earlier, refer to KB article #10326.

DISCUSSION

Your antivirus configuration can affect file-access performance when using the system. This section describes how to optimize your antivirus setup for use with WAFS.

Choose from the following antivirus configurations based on your particular needs, in order from most to least recommended:

Antivirus at each end-user's workstation - If each of your end-users' workstations are protected, the possibility of an infected file is eliminated and there is no need to run antivirus on the computer running an Agent. This is the most effective level.
Protection at the Vault - All files move through the Vault. You can, therefore, run antivirus software on the Vault and scan the Vault's root before propagating files to the Agents.
Protection at the computer running the Agent - Instead of managing antivirus software on each user's workstation, some IT managers prefer to run antivirus software on the computers that run the Agents. When not done properly, this can affect the performance of user file access. Refer to Recommendations for Directories, Drives, and Processes to Exclude in Your Antivirus Software, below, for important exclusion setup notes.

Running antivirus software on an Agent can degrade the performance if not properly configured. The performance hit is caused by the antivirus software thinking that multiple copies of a file are opening. It may scan the same file up to 3 times when a user opens the file once. It may also perform background scans that appear as regular CPU cycles (Norton, E-Trust, NOD32, etc), as well as process scans of the application. If the file is in a linked folder, then the antivirus software scans the file from the original location upon open, AND from inside the replicate drive (e.g., F:\_MySrv\MyVol). Finally, the file is seen internal to the engine (e.g., C:\WINDOWS\AVMF or D:\AVMF), and scanned again.

In addition to on-the-fly scan when a file is changed, some antivirus software includes a daily scan. In this case, if it is necessary to do this daily scan, it might be useful to do it when the Agent is offline. For example, you can schedule the Agent so that it is online 22 hours a day, and offline for two hours during times when users are less likely to use the Agent. During that time, the computer running the Agent can do backups, virus scans, and so on.

Recommendations for Directories, Drives, and Processes to Exclude in Your Antivirus Software

Antivirus applications typically allow directories to be excluded from the antivirus scan (often called "exclusions"). When available, you should exclude directories AVM0 and AVMF. All data mirrored on the C drive will be in C:\Windows\AVMF and all data on any other drive will be in <drive_Letter>:\AVMF (e.g., D:\AVMF). Exclude the entire Vault Data drive (e.g., F:\_MyServer). If your antivirus scans processes (especially E Trust, Innoculan, Symantec Tamper Protection, Trend Micro OfficeScan/Server protect), always exclude WAFSAgentManager.exe.

Below is a list of files and locations, and exclusion suggestions for firewalls:

On the Agent computer:	C:\Program Files (x86)\GlobalSCAPE <Drive(s) with AVMF>:\AVMF <Drive with AVM0>:\AVM0 Vault drive letter C:\Program Files (x86)\GlobalSCAPE\WAFS Agent\AgentConsole.exe C:\Program Files (x86)\GlobalSCAPE\WAFS Agent\AgentService.exe C:\Program Files (x86)\GlobalSCAPE\WAFS Agent\WafsAgentManager.exe
On the Vault computer:	<Drive with AD>:\AD or <Drive with Vault Data>:\Vault Data C:\Program Files (x86)\GlobalSCAPE C:\Program Files (x86)\GlobalSCAPE\WAFS Vault\VaultConsole.exe C:\Program Files (x86)\GlobalSCAPE\WAFS Vault\VaultService.exe C:\Program Files (x86)\GlobalSCAPE\WAFS Vault\WafsVaultMonitor.exe
Regarding Firewalls:	Exclude any ports / additional channels that the WAFS Vault and WAFS Agents use Exclude the IP address of the WAFS Vault and WAFS Agents from monitoring / stateful packet inspection

Some local server antivirus applications in corporate environments, like McAfee, are controlled by a central monitor service run by your IT at headquarters. Exclusions must be specified at that central console; the console then pushes them out. The exclude list you see at each remote site is ignored in these hierarchical topologies. If slowness persists for user access to CAD files, exclude the CAD file extension from the workstation antivirus, and check the performance again.

Winsock Error Codes

GlobalSCAPE 5 — Mon, 09 Jul 2012 10:48:55 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

All Windows-based products

DISCUSSION

The table below lists some common Winsock error codes. Also refer to the Microsoft MSDN Library article "Winsock Error Codes" at http://msdn.microsoft.com/en-us/library/aa924071.aspx.

Return Code	Value	Description
WSAEINTR	10004	Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSAEACCES	10013	Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
WSAEFAULT	10014	Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof(sockaddr).
WSAEINVAL	10022	Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening.
WSAEMFILE	10024	Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
WSAEWOULDBLOCK	10035	Resource temporarily unavailable. This error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
WSAEINPROGRESS	10036	Operation now in progress. A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error.
WSAEALREADY	10037	Operation already in progress. An operation was attempted on a non-blocking socket with an operation already in progress—that is, calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed.
WSAENOTSOCK	10038	Socket operation on nonsocket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.
WSAEDESTADDRREQ	10039	Destination address required. A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY.
WSAEMSGSIZE	10040	Message too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself.
WSAEPROTOTYPE	10041	Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.
WSAENOPROTOOPT	10042	Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
WSAEPROTONOSUPPORT	10043	Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.
WSAESOCKTNOSUPPORT	10044	Socket type not supported. The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.
WSAEOPNOTSUPP	10045	Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.
WSAEPFNOSUPPORT	10046	Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT.
WSAEAFNOSUPPORT	10047	Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.
WSAEADDRINUSE	10048	Address already in use. Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all— connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf.
WSAEADDRNOTAVAIL	10049	Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0).
WSAENETDOWN	10050	Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
WSAENETUNREACH	10051	Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
WSAENETRESET	10052	Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
WSAECONNABORTED	10053	Software caused connection abort. An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
WSAECONNRESET	10054	Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. For more information see GlobalSCAPE Knowledge Base Article #10235
WSAENOBUFS	10055	No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. This error indicates a shortage of resources on your system. It can occur if you're trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that doesn't return system resources (like memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem. Another possible solution is to increase the available virtual memory by increasing the size of the Windows paging file. For more information see GlobalSCAPE Knowledge Base Article #10234
WSAEISCONN	10056	Socket is already connected. A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence.
WSAENOTCONN	10057	Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
WSAESHUTDOWN	10058	Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued.
WSAETIMEDOUT	10060	Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond. For more information see GlobalSCAPE Knowledge Base Article #10384.
WSAECONNREFUSED	10061	Connection refused. No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running. Sometimes a 10061 error is caused by either a firewall or anti-virus software presence on the local computer or network connection. Either one may be blocking the ports needed to make a successful FTP connection to the server. For a regular FTP session, disable the firewall or anti-virus software or configure it to allow CuteFTP to establish an FTP session over ports 20 and 21. Consult the documentation or help file for your specific firewall or antivirus software product for further instructions. Usually, the manufacturer of the device or software has specific instructions available on their website. If you continue to receive the same error after insuring ports 20 and 21 are open, contact the administrator of the server to which you are trying to connect.
WSAEHOSTDOWN	10064	Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.
WSAEHOSTUNREACH	10065	No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAEPROCLIM	10067	Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously.WSAStartup may fail with this error if the limit has been reached.
WSASYSNOTREADY	10091	Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check: That the appropriate Windows Sockets DLL file is in the current path. That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded. The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.
WSAVERNOTSUPPORTED	192	Winsock.dll version out of range. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed.
WSANOTINITIALISED	10093	Successful WSAStartup not yet performed. Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.
WSAEDISCON	10101	Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSATYPE_NOT_FOUND	10109	Class type not found. The specified class was not found.
WSAHOST_NOT_FOUND	11001	Host not found. No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database.
WSATRY_AGAIN	11002	Nonauthoritative host not found. This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.
WSANO_RECOVERY	11003	This is a nonrecoverable error. This indicates that some sort of non-recoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.
WSANO_DATA	11004	Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.
WSA_INVALID_HANDLE	OS Dependent	Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid.
WSA_INVALID_PARAMETER	OS Dependent	One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters.
WSA_IO_INCOMPLETE	OS Dependent	Overlapped I/O event object not in signaled state. The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete.
WSA_IO_PENDING	OS Dependent	Overlapped operations will complete later. The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed.
WSA_NOT_ENOUGH_MEMORY	OS Dependent	Insufficient memory available. An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources.
WSA_OPERATION_ABORTED	OS Dependent	Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.
WSAINVALIDPROCTABLE	OS Dependent	Invalid procedure table from service provider. A service provider returned a bogus procedure table to Ws2_32.dll. (This is usually caused by one or more of the function pointers being null.)
WSAINVALIDPROVIDER	OS Dependent	Invalid service provider version number. A service provider returned a version number other than 2.0.
WSAPROVIDERFAILEDINIT	OS Dependent	Unable to initialize a service provider. Either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup/NSPStartup function failed.
WSASYSCALLFAILURE	OS Dependent	System call failure. Generic error code, returned under various conditions. Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs. Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error.

Controlling Worksharing Display Update Frequency in Revit 2012

GlobalSCAPE 5 — Fri, 06 Jul 2012 04:06:53 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS v4 and later

DISCUSSION

In Revit, the Central file is used to store the current ownership information for all entities and worksets in the project, and acts as the distribution point for all changes published to the file. When operating in worksharing mode, users work on a local copy of the Revit model and can save changes to the Central file so that other users can see their work. The local file is the same size as the Central file and can exponentially increase the storage space required for a project when multiple local files are saved on the network. You can control how often Revit's worksharing display modes and editing requests are updated in model views, to reduce network traffic.

To change the worksharing update frequency in Revit 2012

Click R logo, then click Options.
In the Options dialog box, click the General tab.
In the Worksharing Update Frequency area, move the slider all the way to the left for manual updates only. When set to manual, display mode information is only updated when you borrow elements; worksharing display does not generate network traffic.
Click OK.

Windows Preview Pane locks files for extended period

GlobalSCAPE 5 — Tue, 22 May 2012 09:08:01 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS, all versions

SYMPTOM

On a Windows Vista or Windows 7 computer, you may see a “File in use” or “File_name is locked for editing by user_name” message when opening a Microsoft Office document (e.g., Excel or Word file) in a remote shared folder in Windows Explorer that used the Details view and the Preview Pane layout. This is caused by Windows holding a lock on the files for longer than normal, which is behavior associated with the Details view and Preview Pane layout. Per Microsoft Support, the cause of this issue is a sharing violation that happens between the operating system and the Office application over a network resource.

WORKAROUNDS

On desktops accessing the files on a remote shared folder, modify the following settings to disable the Windows functions that cause this behavior:

In Office 2010:

Click File ->Options->Trust center->Trust center settings.
Clear Protected View.

Windows Explorer:

Click one of the following: Tools -> Folder Options -> View or Organize ->Folder and search options.

Clear Show pop-up description for folder and desktop items.
Clear Show preview handlers in preview pane.

Click Organize -> Layout.

Clear Details Pane.
Clear Preview Pane.

RESOLUTION

Windows Vista: A HotFix is available from Microsoft Support at http://support.microsoft.com/kb/942146.

Windows 7: Add the following registry keys to the computer(s) accessing the document:

[HKEY_CLASSES_ROOT\CLSID\{993BE281-6695-4BA5-8A2A-7AACBFAAB69E}]
@="Microsoft Office Metadata Handler"
"EnableShareDenyNone"=dword:00000001
"NoOpLock"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{993BE281-6695-4BA5-8A2A-7AACBFAAB69E}]
@="Microsoft Office Metadata Handler"
"EnableShareDenyNone"=dword:00000001

To prevent Windows 7 preview functions from causing documents to open read-only, create the following registry entries:

The attached ZIP file contains a separate REG file for each of the registry entries below. If you can't download the attachment, copy and paste the text below into a text file and save it as one REG file.

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Modules\GlobalSettings\Sizer]
"PreviewPaneSizer"=hex:45,00,00,00,00,00,00,00,00,00,00,00,0c,02,00,00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Modules\GlobalSettings\Sizer]
"ReadingPaneSizer"=hex:6e,01,00,00,00,00,00,00,00,00,00,00,0c,03,00,00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\ShowPreviewHandlers]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\ShowInfoTip]

The attached ZIP files contain the registry entries in REG files:

Turn Off Preview Functions in Windows 7.zip contains only the last four "read-only" entries above in 4 separate REG files.
10862.zip contains each of the entries above ("read-only" plus Details/Preview pane entries) in one REG file.

WAFS Vault is filling up with large numbers of previous versions of files

GlobalSCAPE 5 — Mon, 21 May 2012 05:34:14 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS version 3.6.2 and later

SYMPTOM

Some applications save numerous versions (i.e., more than 32) of previous versions of files (e.g., Microsoft Outlook .pst files, AutoDesk Revit Files, Automatic ACL Replication files), causing the Vault to fill up very quickly.

RESOLUTION

In WAFS version 3.6.2, you can enable a cleanup algorithm to automatically remove the previous versions using the "enbSpecialPass" Windows Registry key. Set the key to 1 to enable the cleanup algorithm or 0 to disable it.

To add the key and enable the cleanup algorithm

Copy the text below for your operating system into a text file, then save it with a .reg extension:

On 32-bit systems:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Availl\Availl Server\Settings]

"enbSpecialPass"=dword:00000001

On 64-bit systems:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Wow6432Node\Availl\Availl Server\Settings]

"enbSpecialPass"=dword:00000001

Double-click the .reg file to write the key to the Windows Registry and follow the prompts.

Antivirus Settings in WAFS v3.7.1 and earlier

GlobalSCAPE 5 — Wed, 16 May 2012 03:40:39 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS/CDP, version 3.7.1 and earlier

For WAFS version 4.0 and later, refer to KB article #11016.

DISCUSSION

Yourantivirus configuration can affect file-access performance when using thesystem. This article describes how to optimize your antivirus setup for usewith WAFS/CDP.

Choose from the following antivirus configurations based on yourparticular needs:

Antivirus at each end-user's workstation - If each of yourend-users' workstations are protected, the possibility of an infected fileis eliminated and there is no need to run antivirus on the computer runningan Agent. This is the most effective level.

Protection at the server running the Agent - Instead of managingantivirus software on each user's workstation, some IT managers prefer torun antivirus software on the servers that run the Agent. When not doneproperly, this can affect the performance of user file access. Refer to "Toconfigure antivirus software at the computer running an Agent" below forimportant exclusion setup notes.

Protection at Server - All files move through the Server. You can,therefore, run antivirus software on the Server and scan the Server's rootbefore propagating files to the Agents.

Running antivirus software on an Agent can degrade the performance if notproperly configured. The performance hit is caused by the antivirus softwarethinking that multiple copies of a file are opening. It may scan the samefile up to 3 times when a user opens the file once. It may also performbackground scans that appear as regular CPU cycles (Norton, E-Trust,NOD32, etc), as well as process scans of the application. If the file is ina linked folder, then the antivirus software scans the file from theoriginal location upon open, AND from inside the replicate drive (e.g., F:\_MySrv\MyVol). Finally, the file is seeninternal to the engine (e.g., C:\WINDOWS\AVMFor D:\AVMF), and scanned again.

In addition to on-the-fly scan when a file is changed, some antivirussoftware includes a daily scan. In this case, if it is necessary to do thisdaily scan, it might be useful to do it when the Agent is offline. Forexample, you can schedule the Agent so that it is online 22 hours a day, andoffline for two hours during times when users are less likely to use theAgent. During that time, the computer running the Agent can do backups,virus scans, and so on.

To configure antivirus software at the computer running an Agent

Virus checkers allow directories to be excluded from the antivirus scan(often called "exclusions"). The following exclusions should be made at eachAgent:

Always exclude directories AVM0 and AVMF. All data mirrored on the C drive will be in C:\Windows\AVMF and all data on any other drive will be in <drive_Letter>:\AVMF (e.g., D:\AVMF).
Exclude the entire new drive letters (e.g., F:\_MyServer ).
If your antivirus scans processes (especially E Trust, Innoculan, Symantec Tamper Protection, Trend Micro OfficeScan/Server protect), always exclude AvlAgt.exe.

If slowness persists for user access to CAD files, exclude the CAD file extension from the workstation antivirus, and check the performance again.

Tips for working with AutoCAD

RContreras — Mon, 14 May 2012 05:13:20 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS
CDP

DISCUSSION

Refer to the following help topics:

WAFS/CDP v3.6 - 3.7.1:
- AutoCAD tips: http://help.globalscape.com/help/wafs3/Tips_for_AutoCAD.htm
- Using Revit with GlobalSCAPE WAFS: http://help.globalscape.com/help/wafs3/Using_Revit_with_GlobalSCAPE_WAFS.htm
WAFS/CDP v4:
- AutoCAD tips: http://help.globalscape.com/help/wafs4/Tips_for_AutoCAD.htm
- Using Revit with GlobalSCAPE WAFS: http://help.globalscape.com/help/wafs4/Using_Revit_with_GlobalSCAPE_WAFS.htm

Roaming Profiles

GlobalSCAPE 5 — Thu, 12 Apr 2012 07:58:12 GMT

The Information in This Article Applies to:

WAFS
CDP

Refer to the online help article Roaming Profiles.

Are GlobalSCAPE’s applications being developed using common secure coding practices?

GlobalSCAPE 5 — Mon, 09 Apr 2012 11:29:53 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

All GlobalSCAPE products

QUESTION

Are GlobalSCAPE’s applications being developed using common secure coding practices?

ANSWER

GlobalSCAPE takes application security very seriously, adhering to generally accepted application security standards as set forth by OWASP, Microsoft, and others, in order to prevent common coding vulnerabilities and to minimize security errors.

Specific security tactics include but are not limited to the following:

Follow secure coding practices as recommended by OWASP, Microsoft, and other resources
Conduct "brown bags" for engineers regarding secure coding practices, including classes offered by third-party security firms
Provide off-site training for engineers for secure coding practices
Enable security flags and high warning levels in the development environment to enforce use of secure functions and types
Maintain and follow a Security Vulnerability Assessment and Response Process
Monitor security industry watch lists for known vulnerabilities
Run security scanners/fuzzers against the various protocols and interfaces
Integrate security verification into the quality assurance process
Track and monitor potential vulnerabilities in a bug tracking system
Employ tools such as FindBugs and PMD to automatically catch potential coding and security issues
Follow a process to review and update third-party libraries for major releases
Implement security-related unit testing and automated testing to prevent accidental breakage

Cannot access Java-based web client

GlobalSCAPE 5 — Wed, 04 Apr 2012 03:21:49 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

EFT Server, v6.0 and later
WAFS, v3.7.x and later

SYMPTOM

Cannot access the JavaScript-based clients in EFT Server or WAFS

RESOLUTION

Enable JavaScript in your web browser.

MORE INFORMATION

To edit the browser settings:

In Internet Explorer:

Click Tools > Internet Options. The Internet Options dialog box appears.
Click the Security tab, then click Custom Level.
In the Security Settings dialog box, scroll down to the Scripting area, then under Active scripting, click Enable.
Click OK to close the Security Settings dialog box, then click OK to close the Internet Options dialog box.

In Firefox:

Click Tools > Options. the Options dialog box appears.
Click Content.
Select the Enable JavaScript check box.
Click OK.

In Chrome:

Click Tools (the wrench icon). The Options tab appears.
Click Under the hood, then click Content Settings.
In the JavaScript area, click Allow all sites to run JavaScript. (Enabled by default.)
Click the X in the upper right corner to close the Content Settings page.
Close the Options tab.

User with read-only permission on a file is able to edit and save the file.

GlobalSCAPE 5 — Wed, 07 Mar 2012 05:24:35 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS, all versions

SYMPTOM

User with read-only permission on a file is able to edit and save the file.

RESOLUTION

Ensure the operating system has all of the latest security patches installed.

MORE INFORMATION

Occasionally, organizations lock down their computers so that users cannot access the Internet. While preventing users from accessing the Internet can be good for security, it also prevents the operating system and associated software from receiving important updates, especially those that patch security holes. A system administrator can periodically connect to the computer outside of regular business hours, connect to the Internet, and download and install software updates, while still preventing the end user from accessing the Internet.

"Access Denied" error when opening some PDF documents after installing Adobe Reader v10

GlobalSCAPE 5 — Wed, 22 Feb 2012 04:47:27 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS, all versions
Any product that opens PDF documents

SYMPTOM

"Access Denied" error when opening some PDF documents after installing Adobe Readerv10.

(This issue was fixed in v10.1. For more information about Protected Mode,refer to the Adobe knowledgebase article,Protected Mode Troubleshooting. andKnownIssues. )

RESOLUTION

Since this error was resolved in v10.1 and current version is 10.1.2, the best solution is to update Adobe Reader on all computers. Alternatively, you can copy the PDF to your local drive before opening it or, if necessary, disable Adobe Reader's protected mode.

Adobe Reader uses Protected Mode to prevent malware from infecting computer systems, so turning off Protected Mode opens your computer up to viruses passed through PDF documents.

MORE INFORMATION

Adobe Reader 10.0 is installed in Protected Mode. Protected Mode protects users by limiting what malicious files can do and access. One of the features of the secure mode isthat it cannot open PDF files whose source is distributed file system (DFS) ornetworked file system (NFS). PDF files in shared locations on DFS/NFS cannot be opened. Attempting to open such a file results in an error opening the document.

Only if upgrading the free Adobe Reader to the version containing the fix is not an option, disable protected mode by completing the following steps:

Within Adobe Reader, clear the Enable Protected Mode at startup check box:

If you have a PDF document open, right-click within the document, then click Page Display Preferences.
If you opened Adobe Reader from the shortcut, click Edit > Preferences.

In the Categories pane of the Preferences dialog box, click General, then clear the Enable Protected Mode at startup check box.
Close and the reopen Reader.

If you're using Active Directory, you can push it out via Group Policy.

In the Group Policy Management Editor, pick a Group Policy that applies to all users or create a new one.
Click User Configuration -> Preferences -> Windows Settings -> Registry, then create or edit the following DWORD value:
Click Action: Update, then create or edit the following DWORD value in HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\10.0\Privileged

Value: bProtectedMode

Value data: 00000000

(For information about editing Group Policy, refer to the Microsoft TechNet website,Step-by-Step Guide to Managing Multiple Local Group Policy Objectss.

Using cscript.ext on 32-bit or 64-bit systems

GlobalSCAPE 5 — Mon, 06 Feb 2012 05:08:17 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

CuteFTP Pro^® all versions
EFT Server^™ all versions

DISCUSSION

Using cscript.exe on a 32-bit system:

Open a command prompt. (e.g., Start > Run > cmd.)
Change directory (cd) to c:\windows\system32. (e.g., cd c:\windows\system32)

Type cscript.exe followed by the script you would like to run. For example, the following example will run the Secure Ad Hoc Transfer (SAT) module script to send an email for any SAT accounts that have uploaded a file:

Using cscript.exe on a 64-bit system

Open a command prompt. (e.g., Start > Run > cmd.)
Change directory (cd) to c:\windows\SysWOW64 (e.g., cd \windows\syswow64).

Type cscript.exe followed by the script you would like to run. The following example will run the Secure Ad Hoc Transfer (SAT) module script to send an email for any SAT accounts that have uploaded a file:

Can I change the TCP window size for the WAFS Agent?

GlobalSCAPE 5 — Tue, 31 Jan 2012 07:34:43 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS/CDP version 3.7.1

QUESTION

Can I change the TCP window size?

ANSWER

The WAFS Agent sets its TCP window size to 131070. You can overwrite this value by adding a DWORD value called TcpWindowSize at the following location (depending on your OS):

32-bit: HKEY_LOCAL_MACHINE\Software\Availl\AvaillClient\Settings

64-bit: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Availl\AvaillClient\Settings

Editing the registry is for advanced users only. Incorrectly editing the registry can severely damage your system. You should always back up (export a copy of) the registry before you make any changes to it.

For more information about TcpWindowSize, refer to the Microsoft TechNet article at http://technet.microsoft.com/en-us/library/cc938219.aspx.

What are acceptable characters for WAFS/CDP file and folder names?

GlobalSCAPE 5 — Wed, 18 Jan 2012 09:18:05 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS/CDP

QUESTION

What are the WAFS/CDP file and folder name acceptable characters?

ANSWER

A filename cannot contain any of the following characters:

\ / : * ? " < > |

Characters that are valid for naming files, folders, or shortcuts include any combination of letters (A-Z) and numbers (0-9), plus the following special characters:

^ Accent circumflex (caret)
& Ampersand
' Apostrophe (single quotation mark)
@ At sign
{ Brace left
} Brace right
[ Bracket opening
] Bracket closing
, Comma
$ Dollar sign
= Equal sign
! Exclamation point
- Hyphen
# Number sign
( Parenthesis opening
) Parenthesis closing
% Percent
. Period
+ Plus
~ Tilde
_ Underscore

Unicode is not supported.

For more information regarding file-naming conventions, refer to the Microsoft Windows Developer Network article Naming a File and the Microsoft TechNet article How NTFS Works.

Permissions lost when copying/moving files and folders

GlobalSCAPE 5 — Wed, 18 Jan 2012 09:11:50 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS/CDP (all versions)

SYMPTOM

When you drag files from one folder to another with different permissions, the permissions from the previous folder follow the file. Then, when someone tries to open the file in the new folder, they do not have permission to open the file.

RESOLUTION

This has nothing to do with WAFS/CDP; it is the built in Windows behavior for NTFS volumes. When you copy or move a file or folder on an NTFS volume, how Windows Explorer handles the permissions on the object varies, depending on whether the object is copied or moved within the same NTFS volume or to a different volume. When moving files, Windows keeps the original file permissions if you are moving files to a location within the same volume. If you copy and paste or move a file to a different volume, it will be assigned the permissions of the destination folder.

Microsoft has a fix for this situation. (This is a per-system fix.)

http://support.microsoft.com/kb/310316

You can modify how Windows Explorer handles permissions when objects are copied or moved to another NTFS volume. When you copy or move an object to another volume, the object inherits the permissions of its new folder. However, if you want to modify this behavior to preserve the original permissions, modify the registry as follows.

Open the Registry Editor (click Start > Run, type regedit, then press ENTER).
Locate the following registry key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer

With the key selected, on the Edit menu, click Add Value, and then add the following registry value:

Value name: ForceCopyAclwithFile

Data type: DWORD

Value data: 1
Exit the Registry Editor.

Adjusting Communication Timeout Settings

GlobalSCAPE 5 — Wed, 18 Jan 2012 09:02:37 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS (All versions)
CDP (All versions)

DISCUSSION

This is an advanced topic. If you are not comfortable with making these settings, do not attempt this. Contact GlobalSCAPE Support for assistance.

What is the system timeout setting?

On-going communication occurs between each of the Agents and the Server. This communication involves sending a packet from the Agent to the Server, and receiving a reply packet that travels from the Server back to the Agent. The Agents and Server have timeouts built into them.

An Agent uses a timeout when waiting for a reply from the Server. If a reply does not arrive within the timeout window, the Agent assumes that the Server is off-line or the communication link to the server is broken, and switches itself to off-line mode. It will then poll the Server until communication is reestablished.
The Server uses a timeout for determining if an Agent is unreachable.

Why adjust the timeouts?

In the majority of cases, the default timeouts built into the software should not be altered. If you were not advised by GlobalSCAPE Technical Support to modify the timeouts, we recommend that you not tamper with them. You should consider modifying the timeouts only if you note communication problems or if you consistently have very large files.

If you have very large files: (single files usually 1GB and over, but 300MB is possible too) you may want to set the communications timeout if you notice the Agents are regularly going off line. The disconnect is because of the time it takes for the Server to respond, once it gets this larger request. The slowness of the platform that runs the Server will determine this response time. Either set the timeout at 500,000 or estimate a better setting, as described below.

To estimate the appropriate setting

On the computer that runs the Server, time a simple file copy of a large file from one normal Windows folder to another normal folder.

Multiply this time by 2, and convert to milliseconds for a staring point, then adjust down, if necessary.

If you have communications problems: If you have communications problems, it is best to diagnose the root cause of the problem in your network. Doing a ping or a trace might help identify the problem. For example, a flaky WAN or network could cause the following situations:

The Server Console displays a total of Agents connected to the Server in the total agents field. Each time an Agent disconnects from the Server, it tries to reestablish communication. When it succeeds, the total agents count is incremented. A relatively large number of total agents on the Server Console can indicate that are too many reconnects. For example, if 3 Agents are normally connected and the total agents is 70, you know that there are too many reconnects.
The "disconnected from server" message appears too often.
An Agent displays "illegal function" when browsing volumes on the computer running the Agent (i.e., not from the LAN).

In cases #1 and #2, increasing the timeout will likely help. For example, if there is a temporary 40-second loss of communication and the timeout is set at 60 seconds (60,000), then communication would resume without interruption. If a change is necessary, adjust the timeout setting by increasing it in 30-second increments, then monitor the performance and adjust the number again, if needed. You should set the same timeout on the Server.

In case #3, the timeout is too long. While the Agent is waiting for Server to reply for a given file operation, other components of the system timed out, resulting in this error. You should consider setting the Agent's timeout at 30 seconds, monitoring the performance, and then adjusting the number as needed.

If communication is highly reliable, then you can decrease the timeouts to about 30 seconds.

Adjusting the Timeouts

Adjusting the timeouts involves modifying registry settings on the Server and Agent. Only advanced users should modify the registry. Modifying the wrong key or erroneous deletion of keys might harm the operation of the entire computer. Always backup the registry file before attempting any changes.

The new value for the timeout registry should be determined using trial-and-error. We recommend the following procedure:

Identify why you have an occasional off-line situation. Consult with GlobalSCAPE Technical Support to make sure you have correctly identified the problem.
If the problem persists and you can reliably re-create it, adjust the timeouts on the Agents and the Server. Start with 30-second increments (30000 ms), and if the problem persists, increase or decrease the timeout.

To modify an Agent's timeout
Edit the Agent's registry setting:
For 32-bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Availl\AvaillClient\Settings\SndRcvTOut
For 64-bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Availl\AvaillClient\Settings\SndRcvTOut

Provide the new value, in milliseconds. For example, to set a timeout of one minute, enter 60000.

To modify the Server's timeout
Edit the Server's registry setting:
For 32-bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Availl\Availl Server\Settings\SndRcvTOut
For 64-bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Availl\Availl Server\Settings\SndRcvTOut

Provide the new value, in milliseconds. For example, to set a timeout of one minute, enter 60000.

On the Agent computers, the timeout is read from the registry every time the Agent connects to the server. Therefore, if you modify the timeout, it will take effect upon the next reconnect.

For important information regarding making changes to the registry, refer to Making Changes to the Registry.

Cannot logoff or reboot a computer running the WAFS Agent or WAFS Server after logging on and off the system multiple times

GlobalSCAPE 5 — Wed, 18 Jan 2012 08:56:17 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS/CDP v3.7.1 and earlier

SYMPTOM

Cannot log off or reboot a computer running the WAFS Agent or WAFS Server after logging on and off the system multiple times

RESOLUTION

Occasionally, if you log off of the system and then log back in, when you attempt to log off again, you are unable to log off or to reboot the computer.

If this occurs, do one of the following:

Stop the Server or Agent service that is running on the computer. You should now be able to log off or reboot the computer, if necessary.
Alternately, you can run the executable AvaillLogOff.exe in C:\AVCStuff. Running AvaillLogOff.exe issues the logoff command and logs the computer off of the system.

This is a known issue and is expected to be resolved in an upcoming release.

Does WAFS/CDP work with the Revit product suite by Autodesk?

GlobalSCAPE 5 — Wed, 18 Jan 2012 08:54:49 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS.CDP version 3.6.1 and later

QUESTION

Does WAFS/CDP work with the Revit product suite by Autodesk?

ANSWER

Yes, with some configuration changes, we have several customers who manage their Revit files with WAFS.

For details of using Revit with WAFS, refer to the help topic Using Revit with GlobalSCAPE WAFS.

Cannot delete roaming profile

GlobalSCAPE 5 — Wed, 18 Jan 2012 08:43:18 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS version 3.6.1 and earlier

This is issue is resolved in version 3.6.2

SYMPTOM

When WAFS replicates a roaming profile, a user or administrator might not be able to delete the user's roaming profile directory and/or subdirectories.

Depending on the level of the directory selected for deletion, the user or administrator might receive the message "Error Deleting File or Folder - Cannot remove folder <Folder>: The directory is not empty" or the folder will appear to delete, but then be replicated again from the WAFS Server.

RESOLUTION

Before you can delete a roaming profile directory and/or subdirectories, you need to remove the "Read-only" attribute on the applicable roaming profile subdirectories under the WAFS Job's ("RoamingProfiles") P directory in the WAFS Server vault ("AD").

To remove the read-only attribute from multiple subdirectories

Open a Windows Command Prompt on the WAFS Server computer.

Click Start, then click Run. The Run dialog box appears.
In the Open box, type cmd, then click OK (or press ENTER).

Change directories to the top level directory of the profile you want to delete. For example, type:

cd c:cd AD\RoamingProfiles\P\jsmith

Using the attrib command, recursively remove the read-only setting from child files/folders. Type:

attrib -R -S -H * /S /D

You can now delete the directory from any Agent using an administrator account. When deleting WAFS-replicated folders from the Agent machine, you must use SHIFT+DEL.

How can I configure the initial data transfer without bogging down the network?

GlobalSCAPE 5 — Wed, 18 Jan 2012 08:39:25 GMT

THE INFORMATION IN THIS ARTICLE APPLIES TO:

WAFS (All Versions)
CDP (All Versions)

QUESTION

How can I configure the initial data transfer without bogging down the network?

ANSWER

IMPORTANT:

Do not use this procedure before discussing your specific requirements with Customer Support.

WAFS/CDP native internal transport over your WAN is optimized for the byte-level differences that are transferred for changing files. WAFS/CDP has a maximum bandwidth use of around 4 GB per hour even on the fastest network. You may want to shorten the time for a first large initial full file transfer by using cloning.

You can easily setup your target computer's Agents, so that the initial data transfer does not use the network (via WAFS/CDP) to transfer your data to the other location: this is Cloning. If the data is already at the remote site, and is exactly the same as at the source, you can also use cloning to set up the remote site without any data transfer. If the data is not already at the remote sites, you can use movable media, FTP, or any other method to transfer it.

[The standard way to move data is to install Agents on all locations and then connect to the existing Job on them all. ALL of the data will appear in seconds on the second machine. It is immediately accessible and useable, BUT it is still transferring over the network. They stream when you open them so they will open more slowly until the initial transfer finishes.]

Overview

To clone an Agent, finish installing and setting up WAFS/CDP at one site, then send the catalog information that this source Agent has and your data to the target(s) where you will trick the remote Agent into believing it did a native transport. You will need:

A copy of the source Agent's AVMF and AVM0 directories.
A dump of the source Agent's HKEY_LOCAL_MACHINE\SOFTWARE\WAFS/CDP\WAFS/CDPClient registry.

Once you get these 2 pieces from the source, you can restart the Source Agent and use the data again. Once you get the destinations cloned, they will "see" any changes made in the meantime and update themselves.

Instructions

Before you begin, if they are not already installed, install an Agent on the Source (where your data already is) and install the WAFS/CDP Server.

Follow these steps exactly.

Configure the Source Agent:

Create new Job.
Replicate a folder or drag files into the WAFS/CDP volume.

Before continuing, wait for the WAFS/CDP Server and the Source Agent to be in steady state (files 100% completely uploaded to the Server) in the General info tab. This is CRITICAL.

Download and deploy an Agent on the Destination. The Agent on the Destination must be live and connected; the Job, volume name, and data do not matter.
Stop the Destination Agent.
Stop the Source Agent.
Dump the Source Agent's HKEY_LOCAL_MACHINE\SOFTWARE\WAFS/CDP\WAFS/CDPClient registry tree:

At a command prompt, type regedit.
Export the tree from the registry; select the NT4 format when saving).

Copy the exported tree to a CD, tape, hard drive that you will ship, or FTP or email it over to the remote sites where the Agents are located.
While the Source Agent is still shut off, copy its AVM0 and AVMF directories from the Source computer onto your media (or send it to the remote Agent sites).
Perform this step ONLY IF all your files are ALREADY at the remote site (s). Otherwise skip this step. If the exact (meaning 100% exact if you do a CRC) files/folders are at the Destinations by other means, there is NO NEED to transfer them again. Before sending the copy of AVMF and AVMO from the Source, go into these copies and find the "P" directory that has your files (either AVM0 or AVMF will have them - not both). Delete the files from these copies of AVMO or AVMF - you will then have an empty "P" directory. Then send the copy of AVMO and AVMF with the empty P to all the Agent destinations. Once at the destinations, copy the files (that were already at your Destination) back into the now-empty "P" directory in the copy of AVMO or AVMF and proceed. REMEMBER: AVMO and AVMF must now be 100% IDENTICAL at both/all the sites.

NOTE: Make sure that the files at your remote site are identical to the source files at the exact time you took that registry dump. They MUST be exact bit to bit.

Once you get the registry and the AVMO and AVMF copied, restart the Source Agent. Your files can now be used at the Source again. Send your media or email the registry dump and AVM0 and AVMF to the remote sites. The remote sites will "see" that the Source data has changed and will update themselves later.
Once your files/media arrive at the Destination computer, with the Destination Agent still OFF, restore (import) the registry dump onto the Destination computer and place the AVMO and AVMF on the Destination comptuer into the exact same drive letters and locations as it was on the Source (e.g., the Source C:\AVM0 should be copied to the Destination C:\AVM0). If it is not possible to have everything in the identical location, search the copy of the registry file you dumped and modify it so that every instance of the locations are changed to where you want it on the Destination/target.
Make sure you do not already have a folder with the same name and in the same location on the Destination as was used for your files at the Source. The Destination Agent will create it all for you on startup (from the AVMO, AVMF, and registry that you just imported).
Start the Agent on Destination. You are all set - users can use the files here now too.

Note: It is possible that the IP address on the destination Agents is not correct, and the Agents will not connect. This will be because the IP address at the machine you cloned from, used a local LAN address to communicate with the WAFS/CDP server. If the address at the destination Agent is not proper for a remote connection, then you will need to go into the registry at the destination, find the wrong address and edit the registry to the proper IP address of the machine running the WAFS/CDP server.

Note: As soon as you finished copying all the files, registry, etc. at the Source, you can re-start the Source Agent and use all your data files at the source. If there are changes in the data at the Source since the point in time you copied the data, then the Destination Agent will correctly grab the changes from the Server once it comes up. Nothing will be lost.

Note: If the files had not completed the upload from the Source Agent to the WAFS/CDP server when you cloned at the Source (on the Agent's General Info tab), then once the clone is done and the Destination Agent comes on line, the Destination Agent will upload data to the Server. You can use the files at the destination during this transfer.