7018563: Filr triggers notification for modified file even though file was not modified

In some Filr systems where one or more Net Folders are configured against Windows filesystem, Filr computes that files have been modified which then triggers notifications to users who have subscribed for email notifications. However, the files indicated as modified have not been modified.

When this happens, the appserver.log may contain entries which look as follows:

2016-12-12 12:18:25,745 INFO [pool-fullsync-thread-1-(1-1481570266926)] [com.novell.teaming.module.folder.impl.PlusFolderModule] – (full-ss)

The file {parentPath=null,name=filr 1.0.1 calculator v2.xlsx,handle=null,lastModified=1397504982000,directory=false,contentLength=80644,aclInherited=false,ownerId=lwegner.novell,ownerIdType=typeless_dn}

in the folder [/Home Workspace/Net Folders/POC docs/Filr]

has the modtime changed but not the size: previous modtime = 1397501382000 (Mon Apr 14 18:49:42 GMT 2014), new modtime = 1397504982000 (Mon Apr 14 19:49:42 GMT 2014)

Related:

7018456: Filr Desktop Client for Windows allows blacklisted processes to trigger file downloads

To determine which application(s) are making the Filr files available offline, you can investigate the %LOCALAPPDATA%NovellFilrServiceProvider.log file.

This file useful to determine if the downloading application indeed is a scanner or an other application. However, please be aware that this log file also contains the regular requested file downloads performed by the Filr Desktop client.

In case the application performing the unsolicited downloads is explorer.exe or svchost.exe and the files are mostly compressed archives have a look at TID 7018138.

An additional advantage of configuring the scanner application to exclude the virtual file system, represented in the Filr folder is that this reduces the amount of REST request made by the desktop, that are required to list the files and folders that are available via the Filr infrastructure. This reduces the load on both the workstation as the Filr appliance(s). Therefor there is no harm in excluding the Filr folder permanently from being scanned.

In case the workstation is configured with the default proposed configuration, the data that has been made available offline is stored under “%LOCALAPPDATA%Filr Storage”.

This folder can be scanned, without impact on files being downloaded or additional load on the Filr infrastructure.

To remove the data that was downloaded unsolicited, right-mouse button click on a top level folder in the Filr Area and select “Make available online-only”.

Related:

7017690: File uploads to Windows based Net Folders fail after upgrade to Filr 2.0

After upgrading to Filr 2.0, users are able to see and access their Windows based Home and Net Folders but any attempt to add files to these folders fail. It was also found that if SMBv2 was disabled and the system was set to use SMBv1 the problem was resolved.

The following errors were seen in the logs and traces:

In the browser:

Error saving file: Cannot execute [writeFile] on the resource [jdoeSales 2016Test_File.xlsx] – Access is denied.

In the packet trace:

Create Response, Error: STATUS_OBJECT_NAME_NOT_FOUND

In the smbclient.log:

[2016/04/29 08:52:37.010278, 3, pid=517, effective(0, 0), real(0, 0)] ../source3/libsmb/libsmb_misc.c:69(SMBC_errno) smbc errno NT_STATUS_ACCESS_DENIED -> 13

In the famtd.log:

Apr 29 08:56:05 mke-pds-filr-web-1 famtd[517]: ERROR:CIFSOperations:FAMT_Put:[sid – 6YqEiDL+Sr4P/4UGLbylvg==] SMBC_Open : errno : Permission denied: 13

Related:

7018561: Disk usage report in Filr fails with a HTTP 500 Error

This document (7018561) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus Filr 3.0

Novell Filr 2.0

Situation

When running the Disk Usage Report using one of the following two report options:

1. Total Usage by Workspace

2. Total Usage by User and Workspace

The report ends up in a HTTP 500 error shown in the browser with a java.lang.NullPointerException stack:

java.lang.NullPointerException

org.kablink.teaming.module.report.impl.ReportModuleImpl.generateQuotaReport(ReportModuleImpl.java:2014)

sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)

java.lang.reflect.Method.invoke(Method.java:620)

org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)

org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)

org.kablink.teaming.search.interceptor.IndexSynchronizationManagerInterceptor.invoke(IndexSynchronizationManagerInterceptor.java:73)

org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

org.kablink.teaming.module.interceptor.EventListenerManagerInterceptor.invoke(EventListenerManagerInterceptor.java:64)

org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

org.kablink.teaming.util.aopalliance.InvocationStatisticsInterceptor.invoke(InvocationStatisticsInterceptor.java:49)

org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

org.kablink.teaming.util.aopalliance.LoggingInterceptor.invoke(LoggingInterceptor.java:55)

org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)

com.sun.proxy.$Proxy14.generateQuotaReport(Unknown Source)

Resolution

A fix for this issue is available in the Filr 2.0 – Hot Patch 4 for Filr 2.0 and Filr 3.1 Update for Filr 3.0 via the Novell Patch Finder.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7018775: Missing Filr context menu if the storage location was changed with a case mismatch

If a user changes the default storage location for the Filr Desktop client from the default (C:UsersJohnFilr) to a different drive such as E: but types the target drive letter in lower-case, the folder gets moved successfully but the new location no longer show any of the Filr context menus.

For example: User wants to move Filr Storage location from C:UsersJohnFilr to E:UsersJohnFilr. However, instead of using the Browse button next to storage location, user manually types the new location as e:UsersJohnFilr and saves the changes. The folder gets moved and user can browse files in the new location, however if the user right-clicks on any folder or file, the Filr context menu is missing.

Related:

7018772: Filr Windows Desktop client deletes files due to file name case mismatch

In some Windows 7 and Windows 10 systems, the initial scan of the flesystem (brute-force scan) to detect any file changes triggers a series of delete requests on files that have been modified but are reported in all uppercase letters.

The following snippet from user’s Deskop client log the system returning folder names in All Uppercase:

2017-02-17 07:17:27,813 [filesync-monitor] [INFO] Begin brute force scan of file system to determine if anything has changed (aca.filesync2.watcher.local)

…..

…..

2017-02-17 07:18:18,987 [filesync-monitor] [INFO] Moved folder: 2017-BudgetReturn Process (2489) -> 2017-BudgetRETURN PROCESS (2489). (aca.filesync2.watcher.local)

2017-02-17 07:18:19,019 [filesync-monitor] [INFO] Moved folder: Finance documents2011Bayer (7775) -> Finance documents2011BAYER (7775). (aca.filesync2.watcher.local)

…..

…..

2017-02-17 07:21:48,131 [filesync-monitor] [INFO] Completed brute force scan of file system to determine if anything has changed (aca.filesync2.watcher.local)

Related:

7018774: Filr folders appear empty if VMWare Mirage is installed

This document (7018774) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus Filr 3.1

Micro Focus Filr Desktop client 3.1

Novell Filr 2.0

Novell Filr Desktop client 2.0

Situation

When Filr Desktop client is installed on a Windows system which has VMWare Mirage installed, the Filr folder appears empty and fails to show files that user has access to.

Resolution

A fix for this issue is available in the Filr 2.0 Hot Patch 4 and Filr 3.1.1 update, available via the Novell Patch Finder.

Cause

The altitude for FilrDriver and VMWare Mirage is the same value (= 370030) which leads to this problem.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7018773: Filr Driver prevents Windows Backups

This document (7018773) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus Filr 3.1

Micro Focus Filr Desktop client 3.1

Novell Filr 2.0

Novell Filr Desktop client 2.0

Situation

On some Windows 10 systems, the Windows Backup utility fails to create backups on the attached USB / Backup device. If the backup is attempted with the Filr driver stopped, the backup succeeds without problem.

Resolution

A fix for this issue is available in the Filr 2.0 Hot Patch 4 and Filr 3.1.1, available via the Novell Patch Finder.

Cause

Starting with Windows 10, Microsoft uses the USN Journal feature in the backup. When a backup is attempted, Windows attempts to read the USN journal information for each of the folders present in the user profile. Since Filr does not support the journal information, the backup is failing. This USN journal was present in earlier versions of Windows but it was not used during backups.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: