The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Using the vCenter Server datastore browser to download or copy a powered-on virtual machine's .vmx and .nvram files fails (1019286)
- Downloading the .vmx or .nvram file of a powered-on virtual machine from the datastore browser in vSphere Client fails.
- You see the error:
Expected put message. Got: ERROR
- Copying the .vmx or .nvram file from the datastore browser in vSphere Client fails.
- You see the error:
Unable to access file [filename]
- Using vifs.pl to get the .vmx or .nvram file directly from an ESX host that can see the datastore holding these files fails.
- You see the error:
Error: File can not be downloaded to <destination path>
- Connecting to the vCenter Server URL (http://VC-hostname), navigating from the web-based the datastore browser link to the .vmx or .nvram file of a powered-on virtual machine, and attempting to download the files fails with an http error or the error:
The downloaded file is of size 0 bytes
- When set to trivia logging, the vCenter Server's vpxd logs contain the entry:
Sending soap request to [TCP:<ESX-HostName>:<Port>]: nfcMakeTicketByDatastore.
You can enable trivia logging for vCenter Server to capture information about the ESX host which vCenter Server selects to service the download request. For more information, see Enabling trivia logging in vCenter Server (1001584).
- The vpxa.log for the ESX host contain errors similar to:
[2010-02-04 14:26:40.367 0xf7bbab90 info 'Libs'] [NFC DEBUG] NfcFileRawOpen: failed to open: Generic error..
[2010-02-04 14:26:40.367 0xf7bbab90 warning 'Libs'] [NFC ERROR] NfcFile_Open: Open failed:
[2010-02-04 14:26:40.367 0xf7bbab90 warning 'Libs'] [NFC ERROR] NfcStartFileSend : failed to open file
This issue may occur when the .vmx or the .nvram files are stored on a shared datastore (that is, if the datastore is visible to more than one ESX host). The ESX host holds a lock to these files when the virtual machines is powered-on, so attempting to download these files from another ESX host results in failure.
When browsing a web-based datastore browser or vSphere Client's datastore browser after connecting to vCenter Server, vCenter Server chooses an ESX host to service the download or copy operation. Problems occur if this ESX host is not the host on which the powered-on virtual machine is running. Similarly, the download or copy operation can fail when browsing in a web-based datastore browser or vSphere Client's datastore browser after connecting to the ESX host where the virtual machine is not running but the datastore is visible.
To work around this issue, try one of these options:
- Use the datastore browser in vSphere Client directly connected to the ESX host on which the virtual machine (whose .vmx or .nvram files are of interest) is running.
- Use vifs.pl and connect directly to the ESX host on which the virtual machine (whose .vmx or .nvram files are of interest) is running.
- Use a web-based datastore browser by connecting a browser directly to the ESX host on which the virtual machine (whose .vmx or .nvram files are of interest) is running.
- In vCenter Server 4.0 Update 2 and vCenter Server 4.1, use a web-based datastore browser by connecting a browser to vCenter Server.
Note: If the download fails, retry the download operation.
Note: If the preceding options do not resolve your issue, contact VMware Support. For more information, see How to Submit a Support Request.
- Enabling trivia logging in vCenter Server 4.0.x/4.1.x/5.0.x/5.1.x
- Investigating virtual machine file locks on ESXi/ESX
- No se puede utilizar el buscador del almacén de datos de vCenter Server para descargar o copiar archivos .vmx y .nvram de una máquina virtual encendida
- Falha ao usar o navegador de armazenamento de dados do vCenter Server para baixar ou copiar arquivos .vmx e .nvram de uma máquina virtual ligada
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.