Unable to add a Volume target to a Windows file server.
Article ID: 100034319
Updated On:
Description
Error Message
From the VAC when attempting to add the volume -
Failed to save or update details for volume ‘volume_name’. Could not add the volume to the list of managed resources. No such host is known.
A Dtrace of EvPlaceholderService on the Windows file server may show the following
(EvPlaceholderService) <2036> EV:L CBaseDirectoryServiceWrapper::GetInterface - EntryID [(null)]
(EvPlaceholderService) <2036> EV:M CServiceModule::WaitForDirectoryServiceSync - DirectoryService not available [0xc0042162] - retry in 30 seconds...
Cause
This error is caused by a name resolution issue from the file server to the EV server.
Resolution
Confirm that DNS is able to resolve the name showing in the Dtrace error.
Alternatively, a hosts file entry can be added on the file server pointing to the server in the following format.
IP_address EVSITE EVSITE.DOMAIN.COM
The first name should be the name within the Dtrace log. In this case, the name is the Netbios name and the FQDN also added. If the EV server has other alias names they should be added on the same line as well.
{VaultCreateInstanceRequest::ResolveMachineName} GetMachineNameUsingHostNameHelper failed. Server Name [EVSITE] Error [No such host is known. (0x80072af9)]Alternatively, a hosts file entry can be added on the file server pointing to the server in the following format.
IP_address EVSITE EVSITE.DOMAIN.COM
The first name should be the name within the Dtrace log. In this case, the name is the Netbios name and the FQDN also added. If the EV server has other alias names they should be added on the same line as well.
Issue/Introduction
Unable to configure a new volume under a Windows file server target from the Enterprise Vault (EV) Vault Administration Console (VAC).
Was this article helpful?
Yes
No
Powered by
