You may experience one of the following errors when trying to add a datastore:
FileNotFound: A file was not found.
DuplicateName: The name already exists.
Purpose
This article provides troubleshooting steps to eliminate factors that may prevent you from adding a datastore.
Resolution
Please validate each troubleshooting step below. Each step will provide instructions in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
Note: If you perform corrective action in any of the following steps, try to add the datastore again.
Confirm that you have the correct permissions. Depending on the operating system of the VMware host installation computer, authenticate as either the local Administrator user or as root.
Verify that the value entered in the Name field is not already in use by an existing datastore.
Verify that the value entered in the Directory Path field exists on the filesystem. This value must point to an existing directory.
Note: If CIFS is selected (as opposed to Local Datastore), verify that the file share location can be accessed from the computer where the VMware host is installed using the same information that has been entered in the datastore creation wizard.
Confirm that you are not using a subdirectory of a directory path already that is directly defined by an existing datastore.
For example:
NameDirectory PathNotesDatastore1
Datastore2D:\Datastore
D:\Datastore\NewDatastoreInvalid. The directory path D:\Datastore is already in use by Datastore1 and cannot be used by Datastore2.Datastore1
Datastore2D:\Datastore
D:\NewDatastoreValid. The directory path D:\NewDatastore is not in use by any existing datastore and is available for use.Datastore1
Datastore2D:\Datastores\Datastore1
D:\Datastores\Datastore2Valid. Both datastores use a common D:\Datastores directory path, but neither one point directly to it.
Note: If your problem still exists after trying the steps in this article, please:
File a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request.