Journal Task - console says running, but it's not

[dihrig]

Client had a functioning Journal task. Then a couple days ago there was a temporary network issue that disrupted trusts/authentication between domains. That has been resolved. Since then, a Journal task starts and appears as running in the console, but never processes anything. Dtrace shows it never gets past the first ConfigureMsgService. Event log does not log task as starting or failing.

Already tried the following:

1. Open & access the target EV System mailbox & Journal mailbox from the EV Server using the VSA.
2. Deleted & recreated the Exchange domain, target server, journal mailbox in the VAC.
3. Ran Fixmapi and rebooted.
4. Deleted all EV outlook profiles.

Dtrace of affected Journal task is attached. GC looks OK. Any ideas are welcome.

[JesusWept3]

ok so firstly i would implement the Closest GC key just to make sure everythings all ok
secondly i would try using a different System Mailbox, making sure that the system mailbox is on the same exchange server as the journal mailbox, as a lot of times i've seen issues like this where people consolidate the system mailboxes to one exchange server, even though it's meant to be on a completely different server

[dihrig]

All the GC communication checked out OK. But after trying a Sync on the Journaling task, which also failed, the error logged in the VAC popup was 0xc00e0003. I googled that and it got some references to MSMQ. I shutdown all EV Services and deleted all MSMQ queues related to that task (some had a few items in them). After restarting all EV Services, journal task is running OK.

[JesusWept3]

good job :)