~Vera ElnubergetsiSep 4, 2014, 11:10 PM24 PostsSome possible optionsA lot of things come to mind, and this is far from a comprehensive list of things to look at, but at least a starting point: 1. In the "archive criteria" doc, the last field on the basics tab is a checkbox "In views and folders" where you can designate exactly which views and folders should participate in the archive process. But if most users get Sent items archived, then the cause is something else. If you had to and were not able to determine the root cause, you could always try applying a criteria including Sent view to those users whose sent items are not getting archived, to see if this works around the issue. However, if the docs have some data on them preventing archive, then a separate archive criteria doc would not resolve the issue. 2. I usually first look at the document properties and check to see if there are fields such as "ProtectFromArchive" or "$NoPurge". If those fields exist, the docs would never get archived. Calendar docs have a $NoPurge item, preventing them form being archived. 3. What kinds of docs are these? Are they created form the Memo/Reply forms or something else? 4. In the doc properties, also look at the Creation Date and last modified date. If this doc was really modified within 60 days or not, it should be listed there. 5. Use the free app NotesPeek to look at one of those docs: I see a lot of "malformed" date field data that is not visible in the client UI. For example, you may see one of the date items with "****" instead of a 4-digit year. We see this more on docs or newsletters that were auto-created from an external source, so it would be odd to see this on a Sent item. But if the system cannot determine a valid date, it cannot compute whether or not that doc qualifies for archive or not. 6. Use log_archiving=11 with console logging and manually kick off archiving. You will get a lot of data. The area I focus on is the NoteID table. Search for one of the (failing) docs' NoteIDs to see where it is found in the archive log output. You usually see a message about why it does or does not qualify for archive. I prefer to pull an OS copy of the db locally and set log_archiving=11 and console_log_enabled=1 in my client notes.ini. Makes it really easy to sift through the data. 7. Do those users have other archive criteria listed/enabled in their mail files? Look at the archive settings inside the mail file to see if they have a different criteria enabled. There must be something different about these users' mail dbs vs. others. 8. Along those same lines, run a policy synopsis on one working user and one failing one. Perhaps there are different criteria docs applied to each one? Use the "Detailed" with Archive option in the policy synopsis dialog box.
~Samuel OpnisterakolSep 8, 2014, 3:47 PM6 PostsArchiving Tasks Thank you Amy for your quick response. I will work through your suggestions and respond back.