Table of Contents
Advertisement
3 Run
rm -rf <home directory>/local/share/simias
NOTE: Removing the simias directory deletes all the meta data of iFolder, so you need to
configure the account again.
4 Restart iFolder after a few seconds to launch it successfully.
B.4 Encrypted iFolders Take a Long Time to
Synchronize
If the encrypted iFolder takes considerably long time to synchronize, consider the following causes:
iFolder performs a full data sync every time the file is changed.
You have reset the passphrase.
To avoid the issue, consider the following actions:
To avoid the issue with full data sync, you must remove the encrypted iFolder and create a new
sharable iFolder.
If the passphrase has been reset, you must re-login to synchronize the encrypted iFolders to and
from the iFolder server.
B.5 No Name Conflict When Filenames Differs
Only By Case
When filenames differ only by case, iFolder must create a name conflict. For example: You have
created two files named
A.txt
If you don't get a name conflict error message, consider the following possible cause:
The first synchronization cycle synchronized only one file.
To get a name conflict error message, consider the following actions:
Wait for the second synchronization cycle.
Perform a manual synchronization of both the files.
B.6 Resolving Name Conflict in Maintosh Client
Throws Error
In iFolder client for Macintosh, when you attempt to resolve the name conflict from the GUI, it
gives you an exception. This is because, the client does not support naming conflict. You must
manually change the name of the file in conflict.
B.7 iFolder File Fails to Synchronize
If an iFolder file fails to synchronize, consider the following possible causes:
You have the Read Only right to the shared iFolder. For information, see
"Understanding User Access Rights," on page
and
.
a.txt
88.
to remove the simias directory.
Section 8.6.1,
Troubleshooting 119
Advertisement
Table of Contents
Troubleshooting
