Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

Troubleshooting import or export failures in VMware vCenter Lab Manager

Symptoms

Importing a virtual machine to Lab Manager fails
Exporting fails
Cannot export
Cannot import a virtual machine to Lab Manager
Templates, configuration files, or virtual machines have been removed, however the related files are still on the datastore
Storage usage seems excessive
Removed files are not cleaned up
Unable to power on a virtual machine
VMFS volume becomes inaccessible due to file corruption
Unable to take a snapshot
You see these errors:
- LabManager.Library.Core.UnsupportedException: The import process only supports ethernet0.
- Index was outside the bounds of the array.
- A file was not found.
- Operation not allowed in the current state .
- ASSERT /build/mts/release/bora-39823/bora/vmx/snapshot/snapshot_vmx.c:752
- Managed Server not able to access path
- No available drive letters

Resolution

Validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking 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.

Ensure that the virtual machine data storage is connected and working properly. For more information, see Identifying shared storage issues with ESX 3.x (1003659).
When importing, verify that the source virtual machine meets the import requirements for Lab Manager and that its folder structure is correct. For more information, see Checking import prerequisites in VMware vCenter Lab Manager (1006785).
Ensure that there is enough free network bandwidth to effectively copy the virtual machine between the source and destination. For more information, see Verifying host networking speed (1009527).
Ensure that all ESX hosts being managed by Lab Manager are connected to the same datastores so that every template and virtual machine is accessible to each ESX host. Log in to the server using the vSphere Client. Click Configuration > Storage and make sure that all ESX hosts can see the same datastores.
Assess the storage directory tree and ensure that the correct set of virtual disk files (VMDKs) are present. For more information, see Viewing Virtual Machine Storage Usage.
Check that the resource expiration settings are correct and garbage collection is working. For more information, see Setting the resource expiry settings and testing garbage cleanup functions in VMware vCenter Lab Manager (1006732).
Ensure that the virtual machine has all the required files present in the source directory. If the source is from an ESX host, see Verifying ESX virtual machine file integrity (1003743). If the source is from Workstation or Server, see Verifying hosted virtual machine file integrity (1003846).
Ensure that none of the virtual machine's files are locked or inaccessible. For more information, see Virtual machine does not power on because of missing or locked files (10051).
Ensure that all hosts have SMB mount access to the share. For more information, see Exporting templates and configurations fails in VMware vCenter Lab Manager (1002716).

Note: If your problem still exists after trying the steps in this article:

Gather the VMware Support Script Data. For more information, see Collecting diagnostic information for VMware Products (1008524).

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.

Update History

05/03/2011 - Added Lab Manager 4.0 to products

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.

Feedback

1 2 3 4 5

1 2 3 4 5

Actions

Bookmark Document

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)