Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 6/10/2021 10:10:23 PM
Event ID: 6163
Task Category: Storage Restore
Level: Error
Keywords: Classic
User: N/A
Computer: Server2.SAMGWIN.local
Description:
Failed to obtain Format Name of queue "%2"
%1
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 6/10/2021 10:10:23 PM
Event ID: 6262
Task Category: Storage Restore
Level: Error
Keywords: Classic
User: N/A
Computer: Server2.SAMGWIN.local
Description:
Restore Server receive thread failed to initialize
Unspecified error (0x80004005)
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 6/10/2021 10:10:23 PM
Event ID: 6531
Task Category: Storage Archive
Level: Error
Keywords: Classic
User: N/A
Computer: Server2.SAMGWIN.local
Description:
Failed to open Queue: Enterprise Vault Storage Archive Queue
Queue FormatName: DIRECT=OS:entvault\Private$\Enterprise Vault Storage Archive
The Message Queuing service is not available (0xc00e000b)
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 6/10/2021 10:10:23 PM
Event ID: 6681
Task Category: Storage Archive
Level: Error
Keywords: Classic
User: N/A
Computer: Server2.SAMGWIN.local
Description:
StorageArchive.exe (0) - Process stopped
PID: 32124
Exit Code: 0
The process has stopped due to an unrecoverable error and will not be restarted. Check the event log for previous errors. Once the problem has been resolved the process can be restarted by stopping and restarting the Storage Service
In an Infoscale environment, below event can be seen:
Log Name: Application
Source: AgentFramework
Date: 6/10/2021 10:58:58 PM
Event ID: 17134
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server1.SAMGWIN.local
Description:
MSMQ:EV-Group-MSMQ:online:Clustered MSMQ service is NOT bound to correct port.
ClusterCompMgmt.msc does not show Clustered MSMQ under 'Services and Application' while the Clustered MSMQ resource is online:

1) This issue is seen if local and clustered MSMQ service are set to run as different accounts. Clustered MSMQ service is created automatically when its resource is started. It is set to run as Network Service by default.
2) The issue could also occur due to unavailability of Clustered MSMQ resource. Check if clustered MSMQ resource is online and EV Message queues can be seen using ClusterCompMgmt.msc console.
Set the Local Message Queuing service to run using Network Service account. Restart EV Storage service resource to confirm if the service is functioning now.
If the Clustered MSMQ resource is not coming online, you may need to involve the respective Vendor Technical Support.