The content of this FAQ has been updated and migrated to the following topics:
We recommend that you always use the latest document version in https://docs.itrsgroup.com/ to keep you up-to-date.
Why is the FKM unable to detect some files?
The common reason is because the user running the NetProbe has no permission to the directories required. Make sure that the user running the NetProbe has the necessary permission to access the file and all the directories leading to the file.
When performing wildcard matches on a UNIX (Linux/Solaris/AIX) server, the "NOT_FOUND: Permission Denied" status message means that the user running the NetProbe does not have permissions to traverse higher level directories. This can also occur if the wildcard pattern could match multiple directories, some of which are protected, and no matching paths leading of the file are found - as the globbing system cannot distinguish between the file not existing or being in a directory that it cannot traverse.
A status of "NOT_FOUND: No such file or directory" means that all directories are searchable and no file matches.
On Windows make sure that the user running the NetProbe has the necessary permissions to the directories and files. Remember that typically the NetProbe runs as a Windows Service and this process has no access to mapped drives - only local files will be accessible to FKM.