If you encounter a generic “VMware error” in Lansweeper, follow the steps below to identify and resolve the issue.
Step 1: Verify that Lansweeper is up to date
Lansweeper regularly releases patches, updates, and bug fixes. Running an outdated version may cause VMware scanning errors.
-
Update your installation by following this guide:
https://www.lansweeper.com/knowledgebase/updating-your-installation/
-
Review the changelog to see recent fixes and improvements:
https://www.lansweeper.com/changelog.aspx
-
Download the latest installer here:
https://www.lansweeper.com/update-lansweeper/
Step 2: Confirm your VMware scanning configuration
If your Lansweeper installation is already up to date, verify that your VMware scanning targets and credentials are configured correctly.
Lansweeper can scan VMware environments in two ways:
Option 1: Directly scanning an ESX(i) host
To scan an ESX(i) server directly, the following requirements must be met:
-
A read-only user account must be configured on the ESX(i) host and added to Lansweeper as a scanning credential.
-
VMware Tools must be installed on the guest machines to allow Lansweeper to correctly link virtual machines to their host.
Relevant documentation:
Option 2: Scanning through a vCenter server (recommended)
Scanning via vCenter provides a more complete and reliable overview of your virtual environment than the legacy VMware scanning method using the Managed Object Browser (MOB).
When scanning through vCenter, Lansweeper can collect information on:
- Datacenters
- Datastores
- Clusters
- ESXi hosts
- VMware guest machines
To scan a vCenter server:
Relevant documentation:
Step 3: Contact support if the issue persists
If the error continues after verifying your Lansweeper version and VMware scanning configuration, please open a support case for further assistance:
https://www.lansweeper.com/contact/contact-support/
