We know that setting up and maintaining FileCloud, at the beginning, can be a little intimidating. That’s what we’re here to help with! To ensure that your transition into using the best EFSS solution on the market is as painless as it can be, here are some answers to frequently asked issues of FileCloud. […]
We know that setting up and maintaining FileCloud, at the beginning, can be a little intimidating. That's what we're here to help with! To ensure that your transition into using the best EFSS solution on the market is as painless as it can be, here are some answers to frequently asked issues of FileCloud.
We will cover different applications of FileCloud troubleshooting in this blog post.
Unexpected problems can happen when you are installing or configuring your new FileCloud software.
If FileCloud Webserver or Database does not startup, it is most likely that another process is using the ports used by the Webserver and the Database. By default, FileCloud uses these 3 ports (80, 443, 27017), so if other programs are using these ports, the servers will not start up properly.
The most common applications that use these ports are Microsoft IIS, Skype, TeamViewer.
An alternative option to see Process running on ports 80,443 or 27017 is through GUI. Go to Start>>All Programs>>Accessories>>System Tools>>Resource Monitor (or Run resmon.exe)
PID (4) - Image (System) running on port 80 implies IIS may be running. Stop the IIS and try to restart Apache
Mod-Rewrite Setup Check Fails during Install
Whenever FileCloud encounters an error it records the issue in the log files with an error code. We suggest you go through the log files to know the error type.
Error codes are recorded with a prefix of CLFC and a series of 5-digit numbers
For example CLFC-012345
You can use the error code to understand:
Sometimes, one issue can cause one or more error codes to be reported in the log file.
In this scenario, you will see errors in the following formats:
| CLFC-xxxxx | 5 digits represent a single error |
| CLFC-xxxxx-xxxxx | 10 digits represent an issue with two errors |
| CLFC-xxxxx-xxxxx-xxxxx | 15 digits represent an issue with three errors |
Therefore, to resolve the problem you should address each error code.
Find out more about error code glossary here
Because of the wide variety of local computer environments as well as a variety of network and server configuration, there can be sometimes issues when synchronization occurs.
This can also make troubleshooting complicated. Use the following topics to find steps that will help you troubleshoot and resolve issues.
Note - Sync only detects changes when the file size changes. If the file size does not change, then the file modification is not detected by sync.
FileCloud Sync app stores synchronized files at a default location
The default location of this sync folder is listed below :
To change the sync folder, open the "Settings" option, and then click on the "Settings" tab.
FileCloud Sync app stores temporary files in a cache folder.
The default location of this cache folder is listed below :
To change the default location,
Getting the device logs is the first step to understand a problem and distinguishing between server-side issues and iOS issues.
Sharing log information with our support team will help us investigate your issue and solve it promptly.
To access the log files from user settings:
Just contact your administrator and reproduce the actions that cause the issue you are experiencing.
Starting with FileCloud Version 20.1, the setting TONIDOCLOUD_MAX_METADATA_EXTRACTION_FILE_SIZE_MB in cloudconfig.php file enables you to override the maximum file size for automatic metadata extraction to take place.
By default, the value of the setting is:
Change the maximum file size for metadata extraction:
define("TONIDOCLOUD_MAX_METADATA_EXTRACTION_FILE_SIZE_MB",500); |
For example:
define("TONIDOCLOUD_MAX_METADATA_EXTRACTION_FILE_SIZE_MB",128); |
