All failed tasks experiencing this issue will log the Event ID 3220:
Event ID: 3220
Description:
Could not detect the MSMQ service. Error: 0xC00E000B Check that the MSMQ services are running.
V-437-3320
If a Mailbox Archiving Task is configured then the event ID 2256 will be logged:
Event ID: 2256
Description:
The Archiving task '
V-437-2256
If a Journal Task is configured then the event ID 2258 will be logged:
Event ID: 2258
Description:
The Journal Task '
V-437-2258
If a Public Folder Task is configured then the event ID 2949 will be logged:
Event ID: 2949
Description:
The Public Folder Task '
V-437-2949
A Dtrace of the relevant archiving task (ArchiveTask, JournalTask or PublicFolderTask) will display lines similar to the following:
Could not Locate the "6628" Queue, call returned
That fact that the archiving task process shows "Could not detect the MSMQ service" in the DTrace log suggests a problem with Microsoft MSMQ.
As per https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/ms700106(v=vs.85):
MQ_ERROR_SERVICE_NOT_AVAILABLE (0xC00E000B) translates to "Returned when the application is unable to connect to the queue manager".
Solution 1
Ensure the MSMQ service is running.
If it is, attempt to restart MSMQ, then attempt to restart the failed task(s)
If it is not started, attempt to start MSMQ, then attempt to restart the failed task(s)
If the issue persists, contact Microsoft Technical Support, to troubleshoot MSMQ issues.
Solution 2
If the MSMQ service is started then these errors can also be seen after performing a disaster recovery of the Enterprise Vault server incorrectly where a different hostname which does not match the name in the EnterpriseVaultDirectory database is used.
If this scenario is seen following a disaster recovery of the Enterprise Vault server and further assistance is required then please raise a support case with Veritas Enterprise Vault Support.