Can you give an example of a rule in a job log that fails? This will help us to create a script/command to get the information you need.

SourceOne reporting is part of the issue, and this is what support is working on.

Phased roll-out is how we are going to have to do it.

Still, I would like to be able to schedule a daily report so the server admins can address the issue and I don't know how this could be done.  That's why I'm looking for suggestions

Hi,

Maybe SourceOne Reporting is a solution? I don't know by heart if failed UNC-paths are listed there.

The way I would process this:

- Phase by phase roll-out on different UNC-shares and daily follow-up of the (failed) logs.

This might be time-consuming but could help you out with this issue!

These are plain and simple File Archive - Historic types against shares via UNC paths.  Nothing special.  Support has us running custom binaries to generate more logging, but these will not be used in production once they resolve the issue.  What I am looking for is a way to generate a report on all failed items that doesn't require greping through detailed logs or opening a gui.  That way I can have it captured/scheduled and emailed to team members.