The following issues apply to all workstation operating systems:
In the iFolder client tray application, the iFolder Web site link opens a Web browser to the iFolder Web site on the default iFolder server in the iFolder system. This server is typically the server where your iFolder data resides. However, in an iFolder system with multiple iFolder servers, your system administrator might relocate your iFolder data to a new server in the system or assign a different server to act as the default iFolder server. If your data does not reside on the selected server, your log in to the iFolder Java applet fails.
On login failure, the iFolder Java applet returns the User Resides on a Different Server error message. The message contains an incomplete URL in the instructions for resolving the login error. For example, the message reads:
User resides on a different server. Open the following server URL and select ’login’: http://nif4.yourdomain.com
where nif4.yourdomain.com represents the DNS name of the server where your iFolder data now resides.
This URL provides the correct server address, but the URL is incomplete. The address should include the iFolder directory. For example:
http://nif4.yourdomain.com/iFolder
Replace nif4.yourdomain.com with the actual DNS name returned in the error message.
If problems occur when communicating with the iFolder server while either uploading or downloading files, iFolder will return an error and will not try again to upload or download until the next set synchronization interval.
Do not try to synchronize your GroupWise® archive by setting a GroupWise archive path to the location of your iFolder directory. If you do this, the iFolder client will corrupt the GroupWise archive. This happens because iFolder does not synchronize files as a set and GroupWise needs the files in the archive to be maintained as a set of files.
This problem has been identified for GroupWise; however, similar problems might arise with any database that is implemented as a collection of linked files.