Search the VMware Knowledge Base (KB)
View by Article ID

"Internal error occurs during Export of vSphere ESX Agent Manager" error when migrating vCenter Server 6.0 to 6.5 (2147898)

  • 8 Ratings
Language Editions


  • Migrating a vCenter Server 6.0 installed on Windows to the vCenter Server Appliance 6.5 fails with this error:

    Internal error occurs during Export of vSphere ESX Agent Manager
After a vCenter Server 6.x upgrade failure on the source Windows vCenter Server there will be a file called VMware-VCS-logs-<year><month><day><hour><minute><second>.zip created on the desktop. The below log entries below are found in this zip file.  For more information see Triaging a vCenter Server 6.0 installation or upgrade failure (2105258).  
  • In the UpgradeRunner.log the following error messages are found:

    2016-11-16T14:49:53.634Z ERROR upgrade.states.component_states eam:Export: Remote script failed with an error [InternalError()]
    2016-11-16T14:49:53.634Z ERROR upgrade.states.component_states eam:Export: failed with internal error. For details take a look at Export_com.vmware.eam_2016_11_16_09_42.log.
    2016-11-16T14:49:53.638Z WARNING wf.wf_processor State Export com.vmware.eam has failed.
Note: The UpgradeRunner.log is found in the VMware-VCS-logs-<year><month><day><hour><minute><second>/vcsUpgrade folder.


This article explains how to recover from an EAM export failure during a Windows vCenter Server 6.0 migration to vCenter Server Appliance 6.5.


There are multiple reasons that the EAM export would fail to export. Verify the resolutions below to resolve the issue.

JVM heap issues

    • In the Export_com.vmware.eam.log the following error messages are found:

      2016-11-16T14:49:47.786Z WARNING eam vmware-eam service is not fully started, waiting till get up and running. Sleeping for5seconds. Error: HTTP Error 503: Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:0000000001F40F00] _serverNamespace = /eam _isRedirect = false _port = 15005)
      2016-11-16T14:49:52.786Z ERROR __main__ Upgrade Phase 'eam:Export' failed. Exception: expected string or buffer

      Note: The Export_com.vmware.eam.log are found in the VMware-VCS-logs-<year><month><day><hour><minute><second>/vcsUpgrade folder.

    • In the eam.log the following error messages are found:

      2016-11-14T02:29:10.868-05:00 |  INFO | eam-0 | | 167 | Connecting to vCenter as com.vmware.vim.eam extension
      2016-11-14T02:29:10.881-05:00 |  INFO | eam-0 | | 603 | Connecting to https://vCenter:8089/sdk/vimService via vCenter proxy http://localhost:80
      2016-11-14T02:29:15.900-05:00 | ERROR | eam-0 | | 179 | Failed to login to vCenter as extension. vCenter has probably not loaded the EAM extension.xml yet.: Cannot complete login due to an incorrect user name or password.
      2016-11-14T02:29:15.900-05:00 |  WARN | eam-0 | | 114 | Trying to recover from error

    • In the wrapper.log the following messages are found:

      INFO   | jvm 2    | 2016/11/16 04:24:12 | java.lang.OutOfMemoryError: Java heap space

      Note: The eam.log and wrapper.log are found in the VMware-VCS-logs-<year><month><day><hour><minute><second>/vcs_logs/eam folder.
           This issue is resolved in VMware vCenter Server 6.5 b, available at VMware Downloads.

To workaround this issue, start the VMware ESX Agent Manager (EsxAgentManager) service on the Windows vCenter Server 6.0 and run the migration again. For more information on restarting services, see Stopping, starting, or restarting VMware vCenter Server 6.x services (2109881).

Port configuration

    • In the UpgradeRunner.log the following error message is found:

      2016-11-16T20:33:32.342Z ERROR __main__ Cannot perform the upgrade, because of the following not allowed custom ports: HTTP Port (81, default 80)

      Note: The UpgradeRunner.log is found in the VMware-VCS-logs-<year><month><day><hour><minute><second>/vcsUpgrade folder.

    • The EAM service is using a custom port.  In the example above, the default port of 80 has been changed to 81.

To resolve this issue, change the EAM port back to the default port (80) in

Note: The default location for the file is C:\Program Files\VMware\Infrastructure\tomcat\webapps\eam\WEB-INF.

See Also

Update History

03/17/2017 - Added 6.5 b fix in resolution.

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.


  • 8 Ratings

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)

Please enter the Captcha code before clicking Submit.
  • 8 Ratings