12-10-2018 12:39 PM - edited 12-10-2018 12:43 PM
It seems like every few months, I check the Journal task and it quit archiving the journal mailbox. I've tried all my tricks from the past that has fixed it and so far, as much as I can tell, it's still broken and not archiving the journal mailbox. I just got done deleting the target and task for journal. In the past I would do this and rebuild it and find out that the service account moved to a different exchange server or something which would cause me to not be able to rebuild it until it was corrected fixing the overall issue of journal task not working. No such luck this time. I rebuilt the task and target without problem.
When I run a dtrace on the journal task, it's full of this...
993387 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993388 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993389 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993390 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993391 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993392 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993393 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993394 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993395 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993396 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993397 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993398 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993399 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993400 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993401 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993402 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993403 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993404 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993405 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993406 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993407 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993408 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
993409 14:43:04.762 [7296] (JournalTask) <9388> EV:M :CArchivingAgent::IsEligibleForArchive() |Entering routine |
993410 14:43:04.762 [7296] (JournalTask) <9388> EV:H :CArchivingAgent::IsEligibleForArchive() |Exiting routine |
Not much of anything else when I dtrace the journal task and the storage archive. These IsEligible entries should be coming back with message headers but it's not scanning the emails it appears.
12-12-2018 02:03 AM
Hello,
9.0.2 is really old, no chance of upgrading I assume?
Anyway. after you have created the new task, have you verified the MSMQ's for this task have been created? Are the items in the 'old' MSMQ? Have you examined the Journal Mailbox? If you sort on messageclass, do you see EV related classes (Pending Archiving/Pending Archving part?). Have you ran Deployment Scanner against Exchange, to see if something went amiss? Which Exchange version do you have?
Can you create a new Journal Mailbox in Exchange, and a corresponding archive in EV, define that new mailbox to be archived by the new task. Then create a 2nd task to archive the old Journal Mailbox.
See what that does.
12-13-2018 07:46 AM
I'm attaching an image of my msmqs. The journal mailbox is on our tn001wexmbx008 server so one of those msmqs coorespond to it but how do I know which one is the right one?
12-14-2018 12:40 AM
Wow, 7 journal tasks on 1 server. Below query will show the info you look for.
Queues which are not in use anymore (because task is deleted) AND it shows 0 items, can be deleted.
Use EnterpriseVaultDirectory
Select TS.Name "Task Name", JT.MessageQueue "Message Queue Name"
From Task TS, JournalTask JT
Where TS.TaskEntryId = JT.TaskEntryID
Order by JT.MessageQueue
12-17-2018 10:28 AM
I ran the query and I get this back...
Task Name Message Queue Name
Exchange Journaling Task for TN001WEXMBX007 1 TN001WENJRNL01\Private$\Enterprise Vault Exchange Journaling Task for TN001WEXMBX007 151022101621
Exchange Journaling Task for TN001WEXMBX008 TN001WENJRNL01\Private$\Enterprise Vault Exchange Journaling Task for TN001WEXMBX008 181210143420
Exchange Journaling Task for TN001WEXMBX07 TN001WENJRNL01\Private$\Enterprise Vault Exchange Journaling Task for TN001WEXMBX07 110906142351
12-17-2018 10:32 AM
I see that cleaning this up may make our msmq look nicer, but it looks like a lot of busy work and having non-working msmq queues probably isn't hurting anything or breaking anything.
12-18-2018 03:28 AM
Is that all you get back? If so, you might have some issues indeed.
what I would do:
Set all task in backup mode. Restart tasks. Let them run until MSMQ is empty. (all 0), and not showing new additions.
When empty, set backup mode on the indexes and Vault Stores, then stop all EV services. Delete all MSMQ's. Start Directory service (which starts admin service). Start Taskcontroller service. Verify new MSMQ's are being created. Verify eventlog for EV to see if tasks also started. Start other services also (shopping/indexing/storage).
Be advised, the above needsto be done only after having taken a full backup of the server itself, and, if somehting goes wrong, you're on your own....