background image

iFolder 3.6 Readme

131

no

vd

ocx 

(e

n)

  

10

 Ma
rch 20

08

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)]

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)]

Summary of Contents for 3.6 05-2008

Page 1: ...anging 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 F...

Page 2: ...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 appropriat...

Page 3: ...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 d...

Page 4: ...a data store In other words even if the data store is enabled the Enable button stays active and when the data store is disabled the Disable button stays active When you select any part of the data st...

Page 5: ...onsoles fails when you access iFolder through NetWare Access Gateway Bug 250186 Last updated 09 19 2007 12 2 15 SSO with Identity Injection to iFolder Web Access Fails The SSO with identity injection...

Page 6: ...a Binary Upgrade is Not Supported on page 134 Section 12 4 2 File Size Limit for Uploading on page 135 Section 12 4 3 An Encrypted iFolder Fails to Prompt for a Passphrase On Downloading on page 135 S...

Page 7: ...09 20 2007 12 4 4 Migration Wizard Throws a Random Exception When you attempt to migrate iFolder 2 x to 3 6 the Migration Wizard randomly throws exception error even though it successfully migrated to...

Page 8: ...r 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...

Page 9: ...oduct that is described in this document In particular and without limitation these intellectual property rights may include one or more of the U S patents listed at Novell Legal Patents Web Page http...

Reviews: