Error Message

Either of the following errors are displayed in the System Event Viewer log on the EV server:

Event ID 10028:
Description: DCOM was unable to communicate with the computer XXXXXX using any of the configured protocols; requested by PID XXXX (C:\Program Files (x86)\Enterprise Vault\AdminService.exe).

Event ID 10009:
“DCOM was unable to communicate with the computer XXXXXX using any of the configured protocols”


When performing a DTRACE of the Admin service the following message is returned:

Note: This message is displayed when Enterprise Vault checks if the non-Windows target is a Windows server and gets an error 0x800706ba:

(AdminService) <6520> EV:L                {CVolumeInformation::IsVolumeAWindowsServer:#460} Testing if [XXXXXXXX] is a Windows Server...
(AdminService) <6520> EV:L                {CVolumeInformation::IsVolumeAWindowsServer:#470} Platform Id: [500]
(AdminService) <6520> EV:H                {CVolumeInformation::IsVolumeAWindowsServer:#484} _com_error caught. Error: [The RPC server is unavailable.  (0x800706ba)]
(AdminService) <6520> EV:L                {CVolumeInformation::IsVolumeAWindowsServer:#496} Is [XXXXXXXX] a Windows Server? [False]

 

In order to support NetApp C-Mode Vserver targets with EV 11.0.1, a change was introduced to also validate the C-Mode platform. The method used initially resulted in some Windows File Servers being incorrectly detected as C-Mode Vservers. In 11.0.1 CHF4 another change was introduced to modify the order in which the platforms are validated, processing the Windows platform validation first.
 
With this latest change, the validation against Windows uses DCOM to communicate with the File Server, and as a result, if the file server is a non-Windows platform, the DCOM request will fail, therefore reporting the error in Event Viewer.

The change was introduced in 11.0.1 CHF4 and applies to any subsequent builds, including EV 12.0.x.

This result is expected behavior for Enterprise Vault and the error can be ignored in the above described circumstances.

The System Event log shows a DCOM error before starting any File System Archiving (FSA) synchronization or the FSA Archiving Task whilst processing a non-Windows target

As the process continues, it checks to see if the target is a Celerra/VNX or a NetApp filer. Once the validation is completed, the processing of the targets continues with no additional issue.