Files configured for delayed processing are not processed in ERM

Symptom

Some files configured for delayed processing are not processed in Microsoft Prodiance Enterprise Risk Manager (ERM).  

Cause

Files that have a long file path configured for delayed processing are not processed in ERM, because if the resulting staging folder ends up with a file path of over 260 characters, then the system cannot process the file as the file path has hit the Windows 260 character file path limit.  

Resolution

The resolve the issue in order to start the files to processing again, you must choose one of the following workarounds:
  1. Disable delayed processing. In the audit configuration templates for all files, select the Options tab and select On file save under Audit changes and then click Save.
  2. Set the NTFS Processor to ignore save notifications. Open the Prodiance Service Manager, right-click the NTFS Processor and select Edit. On the General tab, in the Parameters field, configure the parameter /monitortype:dbqueue and then click.
  3. Enable the daily scan. Open the Prodiance Service Manager, right-click the NTFS Processor and select Edit. On the General tab, in the Parameters field, configure the parameter /rescantype:daily and then click.
  4. If you can predict which folders contain the files that have long file path/names, you could be more specific in setting up the base folder on the Network Shares tab of the Prodiance web portal Account administration. You can configure the base folder to include as much of the path as possible.
All files would be monitored only once each day without the ability to do “on save” for any of the files as only the midnight scans would detect the file changes.



Properties

Article ID: 2741493 - Last Review: 16 Jan 2013 - Revision: 1

Feedback