1.10 Filr Issues

1.10.1 Reporting Issues

1.10.1.1 Email Report Is Missing Items from the Last Day of the Report

When running an Email report (as described in Email Report in the Novell Filr 1.0.1 Administration Guide), emails are not displayed for the last day of your report date range.

For example, if you are running an email report between February 3 and April 26, the email report does not show emails from April 26.

1.10.1.2 License Report Issues

The License Report currently counts Administrator, Guest, and three internal users (_emailPostingAgent, _jobProcessingAgent, and _synchronizationAgent) as local users. The Administrator counts as an active user, but the other four local users do not count against your Filr license usage.

For information about how to generate a license report, see License Report in the Novell Filr 1.0.1 Administration Guide.

1.10.1.3 Generating a User Activity Report Causes High Memory Utilization

Generating a user activity report for workspace or folder activity (as described in User Activity Report in the Novell Filr 1.0.1 Administration Guide) can lead to high memory utilization, depending on the number of files that were recently added to the Filr system.

This issue occurs only when no users are selected. To avoid this issue, select one or more users for which you want to generate the activity report, then generate the report.

1.10.2 My Files Storage Directory Is Displayed in Search

When Personal Storage is disabled and Home folders have not been configured, users can find a directory called My Files Storage when clicking in the global Search field and pressing the Spacebar. This is normally a hidden directory, but can it be displayed under these special circumstances.

When you click My Files Storage, it can take you to either your My Files area or to the profile of another user (depending on where you are when you do the search).

1.10.3 Sharing Issues

1.10.3.1 Cannot Share with a Group Whose Membership Includes an External User

If you try to share a file or folder with a group whose membership includes an external user, an error occurs and the file or folder is not shared with the group.

1.10.3.2 Editing an .rtf File Results in an Editing Conflict Error

After editing an .rtf file from Filr in a text editor (such as Microsoft Word), saving the file results in a message indicating that the file has been changed by another author. In this case, select the option to combine your changes with the other author’s changes, then click OK.

Changes that you make to the file are saved to Filr as expected.

For more information about editing files in Filr using Edit-in-Place functionality, see Editing Files with Edit-in-Place in the Novell Filr 1.0.1 Web Application User Guide.

1.10.4 External Users Cannot Browse to a Folder When Moving or Copying a File from a Shared Folder

External users who have Contributor rights in a folder that has been shared with them are not able to browse to a destination folder when moving or copying a file. Instead, external users must specify the name of the folder where they want to move or copy the file in the Destination Folder field, as described in Moving Files and Copying Files in the Novell Filr 1.0.1 Web Application User Guide.

1.10.5 LDAP Synchronization Issues

1.10.5.1 Issues When Deleting Users through LDAP

Novell recommends that you never select the option Delete Users That Are Not in LDAP when configuring your LDAP synchronization. This feature will either be enhanced or removed in future Filr releases. User accounts that are deleted cannot be recovered. As a best practice, leave this LDAP option unchecked. Doing so disables users rather than deleting them.

1.10.5.2 Issues with Initial Synchronization of Filr Users

The LDAP value of the attribute you specify for the LDAP configuration setting LDAP attribute for Filr name must be unique throughout your LDAP directory. For example, if you specify cn, all users in the LDAP directory might not have a unique value.

To resolve this issue, use an attribute whose value is always unique across all containers, such as emailAddress.

1.10.5.3 Hardcoded LDAP Limitation with Windows Server 2008 R2 and Windows Server 2008

Hardcoded LDAP limitations that exist with Windows Server 2008 R2 and Windows Server 2008 can result in LDAP returning less information for a single LDAP query. The limitations are:

  • Maximum number of users that can be synchronized: 20,000 (the default limitation is 5,000)

To work around this issue, create a base dn for each subcontainer.

For more information about this issue, see Windows Server 2008 R2 or Windows Server 2008 domain controller returns only 5000 attributes in a LDAP response in the Microsoft Support Forum.

1.10.5.4 Default Groups and Containers in Active Directory Are Not Synchronized to Filr through LDAP

Membership of groups that are located in the Default Users OU (such as the Domain Users group) in Active Directory are not synchronized to Filr through LDAP.

1.10.5.5 Issues with Renaming and Moving Users in Your LDAP Directory

In order to rename or move users in your LDAP directory, ensure that you have specified a value for the setting LDAP attribute that uniquely identifies a user or group, as described in LDAP Attribute to Identify a User or Group in Managing Users in the Novell Filr 1.0.1 Administration Guide. If a value is not specified for this setting, renaming or moving users in your LDAP directory might result in new users being created in Filr or in the existing user account being deleted.

1.10.5.6 Users Cannot Log in to the Filr Mobile App or Desktop Application with New Name after They Are Renamed in LDAP

After users are renamed in the LDAP directory, users must use their old user names when logging in to the Filr mobile app or the Filr desktop application.

Users can use their old or new user names when logging in to Filr from the Web client.

1.10.5.7 LDAP Referrals Are Not Supported

Novell Filr does not currently support the use of LDAP referrals in regards to LDAP synchronization.

1.10.5.8 Active Directory Cross Forest Trust Relationship Is Not Supported

Cross Forest Trust relationships in Active Directory are not supported in Filr.

1.10.6 Password-Protected Files Cannot Be Viewed

Files that have been password-protected in the application where they were created cannot be viewed on the Novell Filr site. This is working as designed.

1.10.7 Folder Nesting Issue

Because of database restrictions, the maximum number of nested folders that Filr allows is 45. For example, you can create a folder within a folder, then create a folder within that folder, and so forth, until the folder structure is 45 levels deep. You cannot exceed 45 levels in the folder structure.

1.10.8 Email Issues

1.10.8.1 Cannot Communicate with an External Outbound Mail System

If you cannot get your Filr site to communicate with an external outbound mail system (such as Novell GroupWise), you might need to configure the Filr outbound email server with TLS over SMTP. If your email application requires this type of configuration, you can configure Filr with TLS over SMTP by using STARTTLS, as described in Configuring Outbound Email with TLS over SMTP in Managing Email Configuration in the Novell Filr 1.0.1 Administration Guide.

1.10.8.2 Test Connection Fails without User Name and Password Even When Authentication Is Not Required

When configuring Filr to use an external outbound mail system (such as Novell GroupWise), the Test Connection button fails when no user name and password is specified, even when the Authentication required option is not selected.

For information about how to configure Filr to use an external outbound mail system, see Changing Outbound Email Configuration Settings in the Novell Filr 1.0.1 Installation and Configuration Guide.

1.10.8.3 Test Connection of the Outbound Email Server Fails after Reconfiguring the Filr Server

After reconfiguring the Filr server, the Test Connection button does not work because the password is cleared from the Outbound E-Mail page. However, outbound notifications are still sent from the Filr system because the password is retained in the system. (For more information about configuring outbound email, see Changing Outbound Email Configuration Settings in the Novell Filr 1.0.1 Installation and Configuration Guide.)

Retype the password in the Password field on the Outbound E-Mail page in order for the Test Connection button to function properly.

1.10.9 Cannot Drag and Drop Files into a Folder When Using Safari on Windows

You cannot drag and drop files into a folder (as described in Adding Files to a Folder in the Novell Filr 1.0.1 Web Application User Guide) when using Safari on Windows.

This is because the drag-and-drop window for adding files to folders in Filr uses HTML 5 functionality, which is not currently supported with Safari on Windows.

1.10.10 Filename Should Not Be More Than about 200 Characters

The exact maximum filename length depends on the configuration of the Filr server, but generally it is not less than about 200 characters. If filenames are too long, files cannot be added to Filr.

1.10.11 WebDAV Issues

1.10.11.1 Cannot Edit a File through WebDAV (Edit-in-Place) When the User Password Contains a Space

If you try to edit a file through WebDAV (as described in Editing Files with Edit-in-Place in the Novell Filr 1.0.1 Web Application User Guide) when your user password contains a space, the authentication fails.

To edit files through WebDAV, ensure that your user password does not contain a space.

1.10.11.2 Cannot Edit a File through WebDAV (Edit-in-Place) When Using LibreOffice on a Mac

If you are accessing Filr from a Mac and using LibreOffice as your document editor, you cannot edit files through WebDAV using Edit-in-Place functionality (as described in Editing Files with Edit-in-Place in the Novell Filr 1.0.1 Web Application User Guide).

If you are using Apache to front the Filr system, users are able to edit files through WebDAV when accessing Filr from a Mac and using LibreOffice as the document editor.

1.10.11.3 Windows Update for WebDAV Functionality for Windows Vista and Windows XP

IMPORTANT:Install this update only on Windows Vista and Windows XP. Do not install this update on Windows 7.

In order to use the Novell Filr Edit-in-Place feature in your browser on Windows Vista and Windows XP, you must install the following Windows WebDAV update:

Software Update for Web Folders (KB907306).

This Windows update enables OpenOffice.org and Microsoft Office to interact correctly with the Filr Edit-in-Place feature.

1.10.11.4 WebDAV/Edit-in-Place Issues with Microsoft Windows Vista and Microsoft Office

Microsoft Windows Vista has some issues with WebDAV access that affect all WebDAV interactions. In addition, a Vista-specific issue with applets can prevent the Novell Filr Edit-in-Place feature from working properly. Be sure you are running the latest version of Vista. Be sure you have installed the Windows WebDAV update described in Section 1.10.11.3, Windows Update for WebDAV Functionality for Windows Vista and Windows XP.

Windows Vista users who are using Internet Explorer might see a Java warning when they try to use Edit-in-Place. (Firefox users do not see this error.)

To configure Internet Explorer to support the Filr Edit-in-Place feature:

  1. In Internet Explorer, click Tools > Internet Options.

  2. Click Security, select Trusted Sites, then click Sites.

  3. In the Add this website to the zone field, specify the URL of your Filr server, then click Add.

  4. Select or deselect Require server verification (https:) for all sites in this zone, as appropriate for your Filr server.

  5. Click Close, then click OK to save the security settings.

To configure Windows Vista to support the Filr Edit-in-Place feature in Microsoft Office, you must add new keys to the Windows registry for each Microsoft Office application.

  1. In Windows Explorer, navigate to Program Files/Microsoft Office/Office12.

  2. Scroll down to each Microsoft Office .exe in turn:

    excel.exe
    powerpnt.exe
    winword.exe
    ...
    
  3. Right-click each executable, then click Properties.

  4. Click Compatibility.

  5. Select Run this program in compatibility mode for, then select Windows XP (Service Pack 2) from the drop-down list.

  6. Reboot the computer.

You should now be able to use the Filr Edit-in-Place feature with Microsoft Office files.

NOTE:Although these steps enable Edit-in-Place for Filr, they do not fix Vista’s inability to attach via WebDAV in Filr.

For additional information on applets, view the following Sun bulletins:

1.10.11.5 WebDAV Limitations on Mac

When you use WebDAV functionality in a Mac environment, you encounter the following limitation:

1.10.11.5.1 Limitations When Editing Files on Mac through WebDAV

Edit-in-Place functionality is not supported on a Mac when you use Microsoft Office as your document editor. To use Edit-in-Place functionality on a Mac, you must use OpenOffice or LibreOffice as your document editor.

1.10.12 Viewing a Filr Folder through Windows Explorer Displays an Additional Folder on Windows XP

On Windows XP, when you view a Filr folder through Windows Explorer, an additional sub-folder with the same name as the parent folder might be displayed.

To resolve this problem:

  1. Launch a Web browser.

  2. Navigate to the Microsoft Download Center and install the Software Update for Web Folders (KB907306) http://www.microsoft.com/downloads/details.aspx?FamilyId=17C36612-632E-4C04-9382-987622ED1D64&displaylang=en

  3. Follow the on-screen instructions to install the software update.

1.10.13 Cannot Log in to Web Client When Password Is Longer Than 79 Characters

Users cannot log in to the Filr Web client if the password length exceeds 79 characters.

1.10.14 Display Issues Due to Third-Party Software

1.10.14.1 Scroll Bars That Serve No Purpose Are Sometimes Displayed

Scroll bars that serve no purpose are sometimes displayed in certain folders and collection views. This issue is only occasionally seen and is not harmful.

1.10.14.2 Filr is Not Displayed Correctly When the Ask Toolbar Is Installed on Chrome

When the Ask toolbar is installed on a Chrome browser, it inhibits users from being able to view all of the Filr masthead. The Ask toolbar is not a Chrome-sanctioned toolbar and should not be installed on a Chrome browser.

1.10.15 Cannot View ODP and ODG Files That Contain Charts, Graphs, and Tables When Viewing in HTML Format

ODP and ODG files that contain charts, graphs, or tables are not displayed when viewing files by using the HTML view, as described in the following situations:

1.10.16 Time Stamps for Catalina.out Log File Are Always in UTC Time Zone

Time stamps for entries in the catalina.out log file are always in the UTC/GMT time zone.

1.10.17 Time Is Incorrect after Filr Is Restarted

The time of the Filr system clock is displayed incorrectly for a brief period of time after the Filr appliance is restarted and until another time synchronization in the Filr appliance occurs.

During this period of time, various issues can arise in your Filr site related to functionality that depends on correct time zone settings.

To force a time synchronization to occur in the Filr appliance and resolve this issue, specify the following command from the terminal prompt of the Filr appliance:

sntp -P no -r pool.ntp.org (or your preferred time server that is available to your network)