This guide provides information on known issues for Novell® iFolder® 2.1.3 and is divided into the following sections:
This section describes known issues for Novell® iFolder® 2.1 server software that have not been resolved for this release. These issues apply to all versions of iFolder 2.1, except where noted.
The issues are categorized as follows:
For information on installing and managing the iFolder server, see the Novell iFolder 2.1 Installation and Administration Guide.
The following installation and administration issues for Novell iFolder 2.1 server software apply to all server operating systems:
If an administrator's User object resides on multiple LDAP servers, do not enable the object as an iFolder server Admin user. If you have only one LDAP server and one corresponding Admin user, you can enable the object; however, enabling an administrator User object as an iFolder server Admin user is not recommended.
In the iFolder Management Console, when you attempt to update a User Disk Quota, the User Admin page reports the new User Disk Quota as if the update succeeded, but the Update command is not actually executed by the server. The user's client continues to report the old User Disk Quota. You must repeat the task to force the User Disk Quota to update.
To avoid this problem, modify the User's Disk Quota, then click Update two times, allowing time for the Web page to refresh between clicks.
The Username field is limited for iFolder user IDs.
eDirectory: An iFolder user ID cannot exceed 64 characters in length if you use Novell eDirectoryTM. If the user ID has more than 64 characters, neither the administrator nor the user can access the user's iFolder account.
Active Directory: An iFolder user ID cannot exceed 20 characters in length if you use Microsoft* Active Directory*. If the user ID has more than 20 characters, the operation fails with an error.
The reason for this is that the sAMAccountName attribute, which acts as the user's logon name, is limited to only 20 characters. The iFolderServer administrator applications sets both the user's CN attribute and the sAMAccountName attribute to the same value.
You can manage user accounts from the User Management page in the iFolder Management Console.
The Apache 2 Server registry and the iFolder server software do not support extended ASCII characters (characters above code point 127) in the following fields during the installation:
Additionally, use English when entering the SSL certificate location.
You can access the iFolder Management Console using Microsoft Internet Explorer (IE) 5.0 or later. Netscape* 7 or later is the recommended Netscape browser version.
For iFolder servers running on a NetWare® or Windows* 2000 server operating system, you must use IE to access your files via a Web browser.
For iFolder servers running on an IIS Web server, you must use an IE browser to access the iFolder Management Console or the default iFolder Web site from that server. You cannot access the iFolder Management Console and default iFolder Web site using a Netscape browser on an IIS server. If the iFolder server uses IIS and you want to use a Netscape browser, access the server remotely from a workstation.
The iFolder Java* applet can be accessed from the iFolder Web site using Microsoft Internet Explorer 5.0 or later. Netscape 7 or later is the recommended Netscape browser version.
We require Sun* Microsystems JVM* 1.3.1 to 1.4.1_02 for the iFolder Java applet to function properly. If you upgrade your browser (such as to IE 6 Service Pack 1), the upgrade will change the default JVM to Microsoft's version. Make sure to manually reset Sun's JVM as the default JVM after you upgrade.
Logging in to the Java applet fails with Sun Java Runtime Environment 1.4.2_01 and later. When you attempt to log in, the applet sometimes fails to initialize and returns an error message "Applet NIDapplet not inited." If it does initialize, the applet login fails and returns an error message "Authentication failed."
To avoid this problem, use Sun Java Runtime Environment (JRE) 1.3.1 to 1.4.1_02. Sun no longer supports these versions of JRE under Sun's standard support contracts. To download an archived version of Java 1.4.1, visit the Sun Java Technology Downloads Archive.
The iFolder Java applet is provided as is. It is no longer supported.
If you purchased iFolder 2.1.x as bundled with Novell NetWare 6.5 or Novell NterpriseTM Linux Services, Novell NetStorage is available to provide Web-based access for users to their data on the iFolder server. You must configure NetStorage to support iFolder services. For information, see the NetWare 6.5 NetStorage Administration Guide.
To achieve the best results when using the iFolder Java applet, inform your users of the following tips:
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 the user's iFolder data resides. However, in an iFolder system with multiple iFolder servers, you might relocate a user's iFolder data to a new server in the system or assign a different server to act as the default iFolder server. If the user's data does not reside on the selected server, the 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. 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 the user's iFolder data actually 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
To log in successfully, the user must replace nif4.yourdomain.com with the actual DNS name returned in the error message and add the iFolder directory to the end of the URL.
For the iFolder management and help tools to work properly, you must enable pop-up windows in your Web browser while configuring and administering iFolder. If you use an application that blocks pop-up windows, temporarily disable the blocking feature.
The login to Global Settings from the iFolder Management Console might fail intermittently, displaying a message "Previous Login Failed." To resolve this, repeat the login process until you are successful.
If your Web browser caches its pages, the next time you return to the iFolder Management console, after having logged out of the console and closed your browser, you might not need to log in again.
To avoid this security risk, configure your Web browser to delete the temporary files when you close the browser. For example, in Internet Explorer 6, click Tools > Internet Options > Advanced, under Security, check the Empty Temporary Internet Files When Browser Is Closed check box, then click OK.
The numbers displayed in the Totals field in the Reporting section of the iFolder Management Console reflect only the totals of the iFolder server that the iFolder administrator is logged in to, not the totals of all iFolder servers.
Rapidly toggling back and forth between the Reporting and System Monitoring screens in a Web browser might cause the iFolder server to hang. If iFolder hangs, stop and restart the iFolder server software.
If two administrators are simultaneously making system monitoring requests from two different browsers to two different iFolder servers, either of the iFolder servers in the iFolder system might hang. If iFolder hangs, stop and restart the iFolder software.
The following are known issues for Novell iFolder 2.1.3 running on Windows 2003 Server.
If iFolder is installed on Windows 2000 server and you upgrade the server to Windows 2003 server, then to retain the virtual directories, complete the following:
On IIS 6.0, enable the WebService Extension.
Select the Web Service Extensions folder in the IIS Manager.
In the details pane, click Add a new Web service extension.
Type iFolderServer as the name of the extension in the Extension name box.
Click Add .
In the Path to file box, type the path of the adifolderserver.dll if you are running iFolder on ActiveDirectory or iisifolderserver.dll if you are running iFolder on eDirectory.Click OK.
Set the Set extension status to Allowed checkbox.
Click OK.
In the metabase.xml file, change the keytype from iFolderDocumentRoot or iFolderExtension to IISWebVirtualDir for the following virtual directories.
This ensures that the virtual directories are visible in the IIS manager.
The iFolder Server Windows 2003 in non-English language does not work if the the iFolder username exceeds 20 non-English characters.
When the IIS Web site is configured to run in the IIS 5.0 isolation mode with security level set to Medium, the iFolder Administration page displaying error message such as The application called an interface that was marshalled for a different thread might display.
To resolve this, set the Security level to Low.
In case of large context names, Advanced Search feature might give problems while working with the IIS 6.0. Use the Simple Search instead.
If the Domain Controller for Active Directory is renamed after installing iFolder, iFolder stops working. Reinstall the iFolder Server in this case.
User login fails if the first LDAP server configured for an iFolder server is down. To prevent user login failure, make sure taht the first LDAP server configured for an iFolder server is up.
A non-replica directory server cannot be added as a user LDAP server.
If the user password assigned through the Add User page does not conform to the Active Directory password polices, creating users gives problems.
The account is created in the directory but is not activated. Activate the account with a valid password using Active Directory management tools. This enables the account for using iFolder.
This section describes known issues for Novell® iFolder® 2.1 client software and other user interfaces.
The issues are categorized as follows:
The following issues apply to all workstation operating systems:
The iFolder 2.x client cannot access an iFolder Standard Edition (1.0x) server; similarly, an iFolder 1.0x client cannot access an iFolder 2.1 server. If you have multiple iFolder accounts located on different servers, make sure that you are accessing the iFolder server with the correct version of the iFolder client. For example, use an iFolder 2.1 client to access your files on an iFolder 2.1 server.
If your workstation has Norton Internet Security (NIS) installed, you might see the following error message when attempting to log in to an iFolder server from an iFolder client:
Protocol version error - need newer version of client software.
To correct this problem:
Open the Norton Internet Security application.
Click Options > Internet Security.
Click General > Advanced Options.
Click Web > Add Site.
In the left pane, type the DNS name or IP address of the iFolder site.
In the right pane, click the Privacy tab.
Under Cookies, select Permit from the drop-down list.
Under Browsing Privacy, select Permit from the Referrer and Browser drop-down lists.
Click the Active Content tab.
Under Script, select Allow All Scripts to Execute from the drop-down list.
Click Apply.
Close Norton Internet Security.
Restart the iFolder client, then log in again.
The following issues apply to all workstation operating systems:
If you plan to use the encryption option for your iFolder user account, you must initialize the account by logging in for the first time while using the iFolder client or the Java applet. After the account is initialized, you can log in using the iFolder client, the Java applet, Novell NetStorage, or NetDrive.
If you attempt to initialize the account by logging in for the first time with Novell NetStorage, the account is set up as a clear text account with no encryption option. This occurs even if the administrator sets up encryption as a mandatory policy for all users. Unless your account is already set up for encryption, NetStorage does not offer you a passphrase entry option.
When you use NetStorage for the first time for an iFolder account with encryption, you must enter the passphrase. NetStorage might request the information two times. NetStorage stores the passphrase as an attribute of the User object in eDirectory. After that, NetStorage requests only a password during login.
The Username field is limited for iFolder user IDs.
eDirectory: An iFolder user ID cannot exceed 64 characters in length if you use Novell eDirectoryTM. If the user ID has more than 64 characters, neither the administrator nor the user will be able to access the user's iFolder account.
Active Directory: An iFolder user ID cannot exceed 20 characters in length if you use Microsoft Active Directory. If the user ID has more than 20 characters, the operation will fail with an error.
The iFolder client typically uses your network user ID and password as your login identity for iFolder. If your network user ID exceeds the iFolder limit, contact your system administrator to set your user ID to a value that meets the character limit for user IDs in iFolder.
In iFolder 2.1, if you enable both the Remember Password option and the Place a Shortcut on My Desktop check box, the shortcut persists across system restarts. Even if you delete the icon from your desktop, the icon is re-created every time you reboot your computer.
However, if you log out of the iFolder client and then log in again and uncheck the iFolder shortcut check box, the next time you reboot your computer, the iFolder shortcut will not be created.
If you get an error message indicating that you are not connected to the Internet and you know that you are, open the Internet Connection Wizard to troubleshoot your connection. Right-click the Internet icon on your desktop, then click Properties > Connections > Setup. When the Internet Connection Wizard launches, follow the on-screen instructions.
You must be working online in order for the iFolder client to synchronize files. If you are logged in to the iFolder server and set your Web browser to work offline, the iFolder icon in your system tray dims because working offline breaks the connection to the server. When you set your Web browser to work online, the iFolder client reconnects and logs in to the iFolder server, and the iFolder icon in your system try is once again active (colored).
Logging in to the iFolder Java applet fails with Sun Java Runtime Environment (JRE) 1.4.2_01 and later. When you attempt to log in, the applet sometimes fails to initialize and returns an error message "Applet NIDapplet not inited." If it does initialize, the applet login fails and returns an error message "Authentication failed."
To avoid this problem, use Sun Java 1.3 to 1.4.1_02.
The iFolder Java applet is provided as is. It is no longer supported.
If your iFolder administrator purchased iFolder 2.1.x as bundled with Novell NetWare 6.5 or Novell NterpriseTM Linux Services, Novell NetStorage can be made available to provide Web-based access for users to their data on the iFolder server. Your administrator must configure NetStorage to support iFolder services. For information, see the NetWare 6.5 NetStorage Administration Guide.
To achieve the best results when using the iFolder Java applet:
You can modify your iFolder preferences while logged in to your iFolder account but working offline. However, the changes will not take effect until you activate your Internet or network connection and log in again.
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.
The following issue applies to Windows 98SE operating system:
The iFolder client software requires that the client for Microsoft networks is already installed on your Windows 98SE workstation. Otherwise, your workstation might crash.
To avoid this problem, make sure to run the Internet Connection Wizard on the workstation before installing the iFolder client software. Right-click the Internet icon on your desktop, then click Properties > Connections > Setup. When the Internet Connection Wizard launches, follow the on-screen instructions.
The following issue applies to the Windows 2000 Server operating systems:
When Remote Installation Service is installed on your Windows 2000 server, SIS (Single Instance Store) is also installed. The driver for SIS (sis.sys) conflicts with the iFolder client filter driver (niffltr.sys). You must uninstall one of these two programs; otherwise, your users' workstations will not reboot during the iFolder client installation process and you will get an error message indicating that the two drivers conflict with one another.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
Patents Pending
Novell is a registered trademark of Novell, Inc. in the United States and other countries.
SUSE is a registered trademark of SUSE AG, a Novell company.
All third-party trademarks are the property of their respective owners.