Troubleshooting
Default Log Locations
In case of any problems with the TransferAgent, please examine the TransferAgent logs, which can provide help in identifying issues:
Windows
C:\Program Files (x86)\FileCatalyst TransferAgent\logs
OR
C:\Program Files\FileCatalyst TransferAgent\logs
depending on whether you use a 32 or 64 bit operating system.
Mac OSX
/Users/{USERNAME}/Library/Application Support/FileCatalyst/TransferAgent/logs
which is only accessible via Terminal.
Linux
{INSTALLATION_ROOT}/logs
This default location is always the default log location for the TransferAgent when installed on Linux.
Transfer Related Issues
If you experience a file transfer related issue, such as connectivity or file transfers errors, please contact the administrator of the web application. In other words, the organization who owns the site which is providing the Web UI.
Installation Issues
If there is an installation problem with the TransferAgent, open a trouble ticket directly with FileCatalyst at support.filecatalyst.com
Windows Mapped Network Drive
Windows machines which have mapped network drives may not being visible to the TransferAgent due to Microsoft's implementation of User Access Control (UAC) starting with Windows Vista.
There are examples online on how to disable this or set the system to allow drives to be visible to services.
To implement a workaround:
-
Unzip the file enablelinkedconnections.zip in the application directory (C:\Program Files\FileCatalyst TransferAgent\)
-
Run the registry entry enablelinkedconnections.reg to enable the TransferAgent to see mapped network drives.
-
A reboot will be required for this to take effect.
-
To uninstall, run the undo.reg the same way as enablelinkedconnections.reg, a restart is also required on uninstall.
Deploying FileCatalyst on Your Own Network
Interested in putting FileCatalyst to work for your own organization? We have a solution for almost any file transfer workflow. Please contact FileCatalyst at http://www.filecatalyst.com/trial.