Novell IFOLDER 3.6 Readme

12

iFolder 3.6 Readme

May 2008

12.1 Overview

novdocx (en) 10 March 2008

12

This Readme discusses the known issues for iFolderTM 3.6 for OES 2 Linux and for the iFolderTM
client for iFolder

TM

3.6.

12.2 Known Issues for iFolder

 Section 12.2.1, “The First Connection to The Server Using iFolder Client Exceeds Server

Timeout,” on page 130

 Section 12.2.2, “Pre-Beta 5 Binary Upgrade is Not Supported,” on page 130

 Section 12.2.3, “First Nautilus Refresh Does Not Display iFolder Icons,” on page 130

 Section 12.2.4, “iFolder 3.6 Server Fails to Function After Upgrade from OES 1 SP2 to OES2,”

on page 131

 Section 12.2.5, “Managing Orphaned iFolders Fails in Multi-Server Environment,” on

page 131

 Section 12.2.6, “Large File Upload Fails,” on page 131

 Section 12.2.7, “Changing the LDAP Search Contexts in Web Admin Does Not Reflect in the

Server,” on page 132

 Section 12.2.8, “Simias Runs Even After iFolder Exit,” on page 132

 Section 12.2.9, “Enable/Disable Toggling Does Not Function in a Multi-Volume Configuration

in the Server Page,” on page 132

 Section 12.2.10, “LDAP Search Context in a Slave Server Configuration is Not Updated in the

Simias.config File,” on page 132

 Section 12.2.11, “System.NullReferenceException On Deleting an iFolder After Ownership

Transfer,” on page 132

 Section 12.2.12, “Removing Membership After Ownership Transfer Throws Exception,” on

page 133

 Section 12.2.13, “Web Admin/ Web Access Login Fails at The First Attempt,” on page 133

 Section 12.2.14, “Redirect URL Fails When Accessing iFolder Via NetWare Access Gateway,”

on page 133

 Section 12.2.15, “SSO with Identity Injection to iFolder Web Access Fails,” on page 133

This section describes known issues for the iFolder enterprise server, Web Access server, and Web
Admin server.

iFolder 3.6 Readme

129

12.2.1 The First Connection to The Server Using iFolder Client Exceeds Server Timeout

When you attempt to configure an iFolder user account, either it takes a longer time (90 to 20
seconds) than expected or it throws a Timeout error. In the latter case, further iFolder operations fail
and you cannot create a new account until the old one is removed. Due to this partial account
creation, user account details have incorrect information and certain operations throw exception
error.

The workaround for this issue is:

1 Go to /var/simias/data/simias directory and open the Simias.config file.

2 Search for Context dn in the config file.

3 Add each sub-container or sub-context or usergroup or dynamic group one after the other.

For eg:

Context dn="ou=<prv>,o=<novell>"/

Context dn="ou=<blr>,o=<novell>"/

Context dn="cn=<usergroup>,o=<novell>"/

novdocx (en) 10 March 2008

Context dn="cn=<dynamicgroup>,o=<novell>"/

4 Make sure that for all the above serach context, read rights are given for the iFolder proxy

users.

5 Save the file and restart Apache to load the new contexts with appropriate users.

12.2.2 Pre-Beta 5 Binary Upgrade is Not Supported

An automatic pre-beta 5 to FCS upgrade is not supported. To upgrade the iFolder server from a prior
beta version (beta1 to beta 4) to FCS, follow the steps given below:

1 Right-click the desktop and select Open Terminal.

2 At the command prompt, enter

rpm -Uvh --force ifolder3-enterprise-3.6.0.xxxx-1-2.1.i586.rpm

NOTE: Replace xxxx with the FCS build revision number.

IMPORTANT: The format for the version number for the iFolder enterprise server RPM is

3.6.0.xxxx. For example, ifolder3-enterprise-3.6.0.7226.1-2.

![(Bug 305852, Last updated:08/27/2007)]

12.2.3 First Nautilus Refresh Does Not Display iFolder Icons

When you convert a normal folder to an iFolder by using Nautilus, the change in the icon is not
reflected if your iFolder client runs on SLED 10. This issue is fixed on SLED 10 SP1.

![(Bug 271217, Last updated: 09/05/2007)]

130 iFolder 3.6 Readme

12.2.4 iFolder 3.6 Server Fails to Function After Upgrade from OES 1 SP2 to OES2

The iFolder 3.6 installed and conffigured on NSS volumes fails to function after the server upgrade
from OES 1 SP2 to OES2. The potential cause is that the Simias.config file created during the
upgrade is missing.

The workaround is:

1 Take the file system backup of iFolder 3.2 data store and Simias.config file.

Default location is /var/lib/wwwrun/.local/share/Simias.config.

Ensure that you know the iFolder Proxy user password.

2 Open a terminal console and enter /opt/novell/ifolder3/bin/simias-server-

setup --upgrade.

3 Follow the on-screen instruction to manually upgrade the server.

![(Bug 330324, Last updated: 10/03/2007)]

novdocx (en) 10 March 2008

12.2.5 Managing Orphaned iFolders Fails in Multi-Server Environment

In a Multi-server setup, where a master server connected to two slave servers, and an iFolder user is
removed from LDAP, the iFolders that belong to that user are not displayed as orphans.

![(Bug 328103, Last updated, 09/26/2007)]

12.2.6 Large File Upload Fails

When you attempt to upload large files of size more than 1 GB, upload is cancelled and iFolder
throws an exception.

To resolve this, you must install the latest Mono® and XSP patches which is available through
Novell Customer center.

To apply the patches,

1 Install iFolder with OES 2.

2 During OES 2 configuration, select Customer Center Configuration.

3 Complete the Novell Customer Center System Registration procedure.

4 Continue with the remaining steps for configuration.

5 Once you complete the configuration, open YaST2 > Online Update to resolve the

dependencies and apply the Software patches available on your machine.

![(Bug 236121 and 309100, Last updated: 09/20/2007 and 09/27/2007 respectively)]

iFolder 3.6 Readme

131