Synchronizing A Large Number Of Files Randomly Requires Multiple Sync Cycles; Ifolder Data Does Not Sync And Cannot Be Removed From The Server; Samba Connection To The Remote Windows Host Times Out; Exception Error While Configuring Ifolder On A Samba Volume - Novell IFOLDER 3.7 - ADMINISTRATION Administration Manual

Hide thumbs Also See for IFOLDER 3.7 - ADMINISTRATION:
Table of Contents

Advertisement

A.7 Synchronizing a Large Number of Files
Randomly Requires Multiple Sync Cycles
When you attempt to synchronize a large number of files, a few files are not synchronized in the first
sync cycle. Complete synchronization of the files requires multiple sync cycles.
A.8 iFolder Data Does Not Sync and Cannot be
Removed from the Server
In some cases, an iFolder fails to synchronize, and when you attempt to revert the iFolder to a
normal folder, you get an exception error.
Although you can successfully revert that iFolder to a normal folder from other machines, the
original client machine you used to upload the iFolder shows the same iFolder on the machine.
A.9 Samba Connection to the Remote Windows
Host Times out
If Samba connection to the remote Windows host times out when you execute
samba mount
command, you must check whether the Windows firewall is enabled or not. If it is enabled, add the
Samba port to the list of permitted ports in the firewall configuration.
A.10 Exception Error while Configuring iFolder
on a Samba Volume
If iFolder server throws an exception when you configure the iFolder 3.7 server on a Samba volume,
check the properties of the folder in Windows. You must provide the read-write permission to the
network users. In other words, you must ensure that the Read Only check box is deselected
A.11 Giving Slash (/) at the End of the Default
iFolder Path Creates Corrupted iFolder
Using a Response file when you attempt to create a Default iFolder with a name that has a slash (/) at
the end; for example:
; it creates one with the name
. Synchronizing this
/home/test1/d/
Unknown
iFolder makes the UI hang.
The workaround for this issue is to specify the name of the Default iFolder without a slash (/) at the
end. For example:
.
/home/test1/d
A.12 LDAP Users Are Not Reflected in iFolder
If the LDAP users are not synchronized immediately in iFolder, check to see if the default interval to
synchronize the LDAP server with iFolder servers is 24 hours.
To reflect the changes immediately, you can use the Sync now option in the Server details page of
the Web Admin console.
Troubleshooting Tips For Novell iFolder 3.7 165

Advertisement

Table of Contents
loading

Table of Contents