When performing a Report Action operation that applies MIP Sensitivity Labels to files there may be an issue at the point of labeling a file that causes the ActiveNav Scheduler Windows service to stop.
This applies to Migrate actions with MIP Sensitivity Label Mapping or MIP Sensitivity Labeling actions.
This can happen in limited circumstances when specific issues are encountered in the Microsoft labeling libraries that Discovery Center makes use of to apply labels to files.
The outcome of the ActiveNav Scheduler Windows service stopping is that the Report Action in progress will remain in a 'Running' state in the Discovery Center Current Activity page, but no further progress will be made. The ActiveNav Scheduler Windows service can be started manually at any point after the failure, at which point the Report Action will immediately complete in an 'Error' state.
Due to the fact that Report Actions are performed in batches in the Discovery Center application, with details of a completed batch not being flushed to the database until the entire batch has completed, this will also mean that the Audit and Exception logs for the Report Action will not be reported correctly in the Discovery Center Activity History page.
As noted this issue occurs for a limited set of files in specific circumstances and is caused by problems in the Microsoft labeling process. ActiveNav is working with Microsoft to understand the issue further and aim to provide a fix as soon as is practical but if this problem is encountered identifying the files that cause the issue and excluding them from further MIP Sensitivity Label Report Actions is advised.