Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Adding an ESX host to VirtualCenter fails with the error: A general system error occurred: at line number 7, not well-formed (invalid token) (1008707)

Last Updated: 9/19/2023Categories: TroubleshootingTotal Views: 9768Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

You cannot add an ESX 3.5 host to the VirtualCenter inventory.

You can add other ESX hosts installed on the same server model to VirtualCenter.

If you try to add the ESX host to the VirtualCenter inventory and enter the root username and password, you see the error:

A general system error occurred: at line number 7, not well-formed (invalid token)

The VirtualCenter vpxd trivia logs contain entries similar to:

Note: See Enabling trivia logging in VirtualCenter (1001584) if trivia logging needs to be enabled.

[2009-02-13 10:51:50.274 'App' 1068 error] [VpxVmdbCnx] Authd error: 551 There is no VMware process running for config file vmware-vpxa
[2009-02-13 10:51:50.274 'App' 1068 error] [VpxVmdbCnx] Failed to connect to host esx5.gsslabs.org:902. Check that authd is running correctly (lib/connect error 11)
[2009-02-13 10:51:50.274 'App' 1068 verbose] [VpxVmdbCnx] Failed to connect to host <esx5.gsslabs.org>
[2009-02-13 10:51:50.274 'SOAP' 1068 trivia] Sending soap request to [TCP:esx5.gsslabs.org:443]: GetChildEntity
[2009-02-13 10:51:50.321 'SOAP' 1068 trivia] Received soap response from [TCP:esx5.gsslabs.org:443]: GetChildEntity

[2009-02-13 10:51:50.430 'SOAP' 1068 trivia] Sending soap request to [TCP:esx5.gsslabs.org:443]: GetHost
[2009-02-13 10:51:50.461 'SOAP' 1068 trivia] Received soap response from [TCP:esx5.gsslabs.org:443]: GetHost
[2009-02-13 10:51:50.461 'SOAP' 1068 trivia] Sending soap request to [TCP:esx5.gsslabs.org:443]: queryConnectionInfo
[2009-02-13 10:51:50.508 'App' 1068 error] [VpxVmomi] Unhandled Exception: at line number 7, not well-formed (invalid token)
[2009-02-13 10:51:50.508 'App' 1068 error] [VpxVmomi] Backtrace:
backtrace[00] eip 0x0128e8b6 ?GenerateCoreDump@System@Vmacore@@YAXXZ
backtrace[01] eip 0x011d6d3a ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z
backtrace[02] eip 0x011aff6e ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$a

Manually installing the vpxa agent on the ESX host does not resolve the issue.

This issue may occur with Fujitsu, Siemens RX300 S4, and Sun Blade X6250 servers. However, it might also occur with other servers.

Solution

This issue may occur if the BIOS of the hardware platform does not provide correct information for the Product Name field.

Note: This issue has been observed on, but is not specific to, Fujitsu, Siemens, and Sun systems.

To resolve this issue, contact your server vendor to change the name in the BIOS or to update to a newer a BIOS version which displays the correct information.

To identify the issue:

Log in as root to the ESX host experiencing this issue using an SSH client.

Run the following command and record the output:

esxcfg-info | grep -i 'product name'

Note: The command dmidecode can also be used on ESX classic instead of esxcfg-info. The command smbiosDump can also be used on ESXi instead of esxcfg-info.

Repeat steps 1 and 2 on an ESX host of the same make and model which does not experience this issue.

Compare the output of the two hosts.

The following examples of the Product Name field can cause this issue. The information is usually inaccurate or contains additional characters:

|----Product Name.............................................PRIMERGY RX300 S4 6x 3,5́́

|----Product Name.............................................y

|----Product Name.............................................

The following examples of the Product Name field do not cause this issue:

|----Product Name.............................................PRIMERGY RX300 S4

|----Product Name.............................................Sun Blade X6250

To resolve this issue, contact your server vendor to change the name in the BIOS or to update to a newer BIOS version that displays the correct information.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
アプライアンスベースの Platform Services Controller または vCenter Server を vSphere ドメインに参加させようとすると次のエラーで失敗する：ERROR_TOO_MANY_NAMES (2114233)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
如何在 Customer Connect 中查看合同和支持信息 (2007002)

KB
•
Customer Connect でサポート リクエストを表示して更新する方法 (2007048)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 4.0.x

VMware ESX Server 3.5.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant