Table of Contents
Advertisement
A.2 Login to the Web Consoles Fails
If you cannot log in to Web Admin or Web Access console, consider the following cause:
You are using a DSfW server as the LDAP server.
The workaround for this issue is to ensure the following:
iFolder Admin and iFolder proxy users are created on the DSfW server.
iFolder is configured by using command line script
Use port 1389 for non-SSL and port 1636 for SSL communications.
A.3 Mono Crashes in OES2 SP1 64-bit Server
Running on XEN
If the iFolder is running on a OES2 SP1 64-bit virtualized environment, logging in to iFolder Web
Access or iFolder Web Admin makes mono crash.
The workaround is to update mono by applying the latest patch for SLES 10 SP2.
A.4 Full Restore of Backed-Up Files Fails in
iFolder
If iFolder throws a null exception error when you attempt to restore all the backed-up iFolder data in
debug mode, consider the following cause:
iFolder does not support restoring all the backed-up files. However, restoring user-level and
individual iFolder-level files functions properly.
The workaround for performing a full restore is to perform a File System restore of the all the
backed-up files.
A.5 Enabling a Large Number of Users at the
Same Time Times Out
In the Web Admin console, if enabling a large number of users at the same time throws a time-out
error message, consider the following cause:
The Web Admin console is opened by using Internet Explorer.
The workaround for this issue is to open the Web Admin console by using Mozilla Firefox.
A.6 Changes Are Not Reflected After Identity
Sync Interval
The changes you have made in the iFolder domain, such as adding a new user to the iFolder domain
from the LDAP, are not reflected even after the identity sync interval. The workaround is to click the
Sync Now button after you make the changes.
164 OES 2 SP1: Novell iFolder 3.7 Administration Guide
.
simias-server-setup
Advertisement
Table of Contents
