Jouke,

Just to double-check -- are you using NFR 2.0.0 or 2.0.1? If you're
still on 2.0.0, please update to 2.0.1; there are a large number of
bugfixes in 2.0.1, as well as a few new features you'll find useful.
You'll need to update your Engine and all of your Agents, as well as
re-run the Engine configuration utility once you upgrade the Engine to
2.0.1. (Note that this is just the Engine config, not the web config;
there are database schema updates that need to be added by the Engine
config utility.)

Aside from that, a couple other questions:

What sort of volume are you scanning? NSS? NCP? If NCP, what's the
underlying Linux filesystem?

If you look in the Agent log file, is there a particular path that
causes the scan to fail?

--
- NFMS Support Team

Novell File Management Suite Team;2266086 wrote:
On 5/31/2013 8:56 AM, joukejaap wrote:
>
>> Jouke,
>>
>> Just to double-check -- are you using NFR 2.0.0 or 2.0.1? If you're
>> still on 2.0.0, please update to 2.0.1; there are a large number of
>> bugfixes in 2.0.1, as well as a few new features you'll find useful.
>> You'll need to update your Engine and all of your Agents, as well as
>> re-run the Engine configuration utility once you upgrade the Engine to
>> 2.0.1. (Note that this is just the Engine config, not the web config;
>> there are database schema updates that need to be added by the Engine
>> config utility.)
>>
>> Aside from that, a couple other questions:
>>
>> What sort of volume are you scanning? NSS? NCP? If NCP, what's the
>> underlying Linux filesystem?
>>
>> If you look in the Agent log file, is there a particular path that
>> causes the scan to fail?
>>
>> --
>> - NFMS Support Team
>
>
> We updated Novell File Reporter with the 2.0.1 version as soon it
> became available.
> The volume that we are scanning is a NSS volume.
>
> This is the logfile of that particular volume that we are trying to
> scan.
>
> 01 2013-05-31 11:34:59 7200 3 0006 28553 7fa4e1c32700
> SRSScanAndCollectFileSystemDataService::FinalizeScanDataEntry() - Worker
> thread encountered an error and is exiting, Scan ID = "64", Result = 0.
> 01 2013-05-31 11:34:59 7200 8 8007 28553 7fa4e2433700 NWXPLAT:
> m_pfnNWClearThreadSessionContext() failed, rc = 0x0000886f.
> 01 2013-05-31 11:34:59 7200 3 0006 28553 7fa4e2433700
> SRSScanAndCollectFileSystemDataService::GetMetaDataAndSecurityInfo() -
> Worker thread encountered an error and is exiting, Scan ID = "64",
> Result = 265.
> 01 2013-05-31 11:34:59 7200 5 0006 28553 7fa4dcc28700
> SRSScanAndCollectFileSystemDataService::GetLocalAccountInfo() - Build
> Account Information operation has started, Scan ID = "64".
> 01 2013-05-31 11:34:59 7200 3 0006 28553 7fa4dcc28700
> SRSScanAndCollectFileSystemDataService::GetLocalAccountInfo() - Build
> Account Information operation has completed, Scan ID = "64", Result =
> 265.
> 01 2013-05-31 11:34:59 7200 3 0006 28553 7fa4dc427700
> SRSScanAndCollectFileSystemDataService::GetMetaDataAndSecurityInfo() -
> Get Meta Data

Novell File Management Suite Team;2266449 wrote:
On 6/4/2013 2:36 AM, joukejaap wrote:
>> >>- NFMS Support Team
Jouke,

This line in the Agent log indicates where the failure is occurring:

01 2013-05-31 11:34:58 7200 3 0006 28553 7fa4de42b700
SRSScanAndCollectFileSystemDataService::ProcessEnumeratedResults() -
Phase: Abort Directory, Search Path =
"\\AMS-ADM\USR\MEDEW\aps\Favorieten", Sequence ID = 283, Recursion Depth
= 3.

Some sort of file system object within the path
"\\AMS-ADM\USR\MEDEW\aps\Favorieten" is causing the scan to fail with an
error '14' (an internal error code for "An input parameter is invalid".
Most likely there's a file system object on this volume which can't be
read or opened; either its name contains a special character which the
Novell APIs don't handle properly, or it's corrupted in some way.

--
- NFMS Support Team