"Junk after document element" errors upgrading vCenter Server 5.5 to 6.0 update 2a
search cancel

"Junk after document element" errors upgrading vCenter Server 5.5 to 6.0 update 2a

book

Article ID: 338808

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • Starting VMware Identity Management Services fails when upgrading vCenter Server 5.5 to vCenter Server 6.0 Update 2a.
  • Installing or upgrading to vCenter Server 6.0 update 2a fails with the error:
Encountered an internal error.
 
  • These errors are displayed at the end of the backtrace:
    • "WindowsError: [Error 2] The system cannot find the file specified
    • "WindowsError: [Error 183] Cannot create a file when that file already exists
       
  • In the /var/log/firstboot/vmidentity-firstboot.py_xxxxx_stdout.log file, there are entries similar to:
2016-12-14T20:53:38.220Z VMware Identity Service bootstrap: importDirectory=C:\ProgramData\VMware\vCenterServer\export\sso
2016-12-14T20:53:38.236Z VMware Identity Service bootstrap failed.
2016-12-14T20:53:38.236Z Exception: Traceback (most recent call last):
File "D:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 202, in main
vmidentityFB.boot()
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 181, in boot
self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval)
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 1145, in configureSTS
self.copyCertForTC()
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 810, in copyCertForTC
self.configureTCSSLProtocol(self.__tc_sts_server_xml_path, self.__ecdheFlag)
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 680, in configureTCSSLProtocol
tree = ET.parse(file_path)
...
ParseError: junk after document element: line 66, column 0
  • The %temp%\vminst.log file on the windows machine running the upgrade, there are entries similar to:
2016-12-14 12:52:50.999-08:00| vcsInstUtil-4541944| I: ProcessMsiMsg: ACTIONDATA reporting "Starting VMware Identity Management Service..."
2016-12-14 12:52:50.999-08:00| vcsInstUtil-4541944| I: Leaving function: UpdatePkgMgrProgressFromStatusFile
2016-12-14 12:52:50.999-08:00| vcsInstUtil-4541944| I: Leaving function: ParseStatusFile
2016-12-14 12:53:38.360-08:00| vcsInstUtil-4541944| I: Entering function: ParseStatusFile
2016-12-14 12:53:38.376-08:00| vcsInstUtil-4541944| I: ParseStatusFile: curr error msg: "Encountered an internal error.
 
Traceback (most recent call last):
File "D:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 202, in main
vmidentityFB.boot()
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 181, in boot
self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval)
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 1145, in configureSTS
self.copyCertForTC()
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 810, in copyCertForTC
self.configureTCSSLProtocol(self.__tc_sts_server_xml_path, self.__ecdheFlag)
File "D:\Program Files\VMware\vCenter Server\VMware Identity Services\vmidentity_firstboot_core.py", line 680, in configureTCSSLProtocol
tree = ET.parse(file_path)
...
ParseError: junk after document element: line 66, column 0
"2016-12-14 12:53:38.376-08:00| vcsInstUtil-4541944| E: ParseStatusFile: Displaying error message for " ": "Encountered an internal error.

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vCenter Server 6.0.x
VMware vCenter Server 5.5.x

Cause

This issue occurs when the server.xml file contains malformed data.
 
Note: This file is also used during enabling or disabling SSLv3 and any setting that were made to this may need to be reapplied. For more information, see Configuring SSLv3 protocol on vSphere 5.5 (2146255).

Resolution

To resolve this issue:
  1. Modify or replace the server.xml file correcting any issues:
    1. On the vCenter Server, create a backup of the C:\ProgramData\VMware\CIS\runtime\VMwareSTS\conf\server.xml file.
    2. Open the server.xml file in a plain text editor.
    3. Verify that the information is not duplicated. [Example: Check if the file is repeatedly copied after line 66]
    4. If there is no duplication, restore the file from the backup.
    5. Install a separate instance of vCenter Server 5.5 and transfer the server.xml file.
      • Ensure that there is no copy of the server.xml file in the C:\ProgramData\VMware\vCenterServer\export\sso file.
      • Ensure that the serverout.xml file does not exist in the C:\ProgramData\VMware\CIS\runtime\VMwareSTS\conf\ file.
  2. Upgrade to vCenter Server 6.0 Update 2 and then upgrade to vCenter Server 6.0 Update 2a.


Additional Information

Configuring SSLv3 protocol on vSphere 5.5
vCenter Server をバージョン 5.5 から 6.0 Update 2a にアップグレードすると失敗する
将 vCenter Server 从版本 5.5 升级到 6.0 Update 2a 失败

Attachments

Reference_server.xml get_app
Powered by Wolken Software