A general system error occurred: "N7Vmacore3Xml17XMLParseExceptionE not well-formed (invalid token) (39)"
search cancel

A general system error occurred: "N7Vmacore3Xml17XMLParseExceptionE not well-formed (invalid token) (39)"

book

Article ID: 322076

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

While Performing Reconfigure in SRM appliance with vCenter, we see the below error. 

N7Vmacore3Xml17XMLParseExceptionE not well-formed (invalid token) (39)

Environment

VMware Site Recovery Manager 8.x

Cause

  • While configuring SRM, the configuration service uses an XML file to register the vCenter extension. User-provided data is saved in a specific XML file, which is then used for the vCenter registration process. However, including special XML characters in certain fields can cause the XML file to become ill-formed.
  • Below details found in SRM logs.

   drconfig.log

   2024-03-01T02:05:32.013Z panic vmware-dr[01700] [SRM@6876 sub=Default] Application error: N7Vmacore9ExceptionE Registration with the local VC server was not found.

   --> [context]zKq7AVECAAQAAL/UWwEQdm13YXJlLWRyAAD9BVBsaWJ2bWFjb3JlLnNvAADy/CQA/HwiAITsGwGjRgJ2bXdhcmUtZHIAAZmzCwLexQlsaWJkci1hdXRob3JpemF0aW9uLnNvAAECdgsBQywMAT5fCwFFGwMBK1sMA4YYC2xpYmRyLXZtYWNvcmUuc28AAaDRAgQKfgJsaWJjLnNvLjYAAQ3UAg==[/context]

   --> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 8.8.0, build: build-22795455, tag: vmware-dr, cpu: x86_64, os: linux, buildType: release

   --> backtrace[00] libvmacore.so[0x005005FD]

   --> backtrace[01] libvmacore.so[0x0024FCF2]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)

   --> backtrace[02] libvmacore.so[0x00227CFC]: Vmacore::System::SystemFactory::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)

   --> backtrace[03] libvmacore.so[0x001BEC84]: Vmacore::Throwable::Throwable(char const*)

   --> backtrace[04] vmware-dr[0x000246A3]

   --> backtrace[05] vmware-dr[0x000BB399]

   --> backtrace[06] libdr-authorization.so[0x0009C5DE]: Dr::Authorize::EntityWithPermissionsLifetimeMixin::_Activate(bool)

   --> backtrace[07] vmware-dr[0x000B7602]

   --> backtrace[08] vmware-dr[0x000C2C43]

   --> backtrace[09] vmware-dr[0x000B5F3E]

   --> backtrace[10] vmware-dr[0x00031B45]

   --> backtrace[11] vmware-dr[0x000C5B2B]

   --> backtrace[12] libdr-vmacore.so[0x000B1886]: Dr::DrApp::Run(std::function<int ()> const&)

   --> backtrace[13] vmware-dr[0x0002D1A0]

   --> backtrace[14] libc.so.6[0x00027E0A]

   --> backtrace[15] vmware-dr[0x0002D40D]

   --> [backtrace end]

 

   dr.log

   2024-03-01T02:25:31.502Z verbose drconfig[01043] [SRM@6876 sub=Default opID=6a0f86d1-35bc-4916-8bb1-eebcd898a795-readCurrentConfig:c19f] Loading configuration /opt/vmware/srm/conf/vmware-dr.xml

   2024-03-01T02:25:31.503Z error drconfig[01043] [SRM@6876 sub=Default opID=6a0f86d1-35bc-4916-8bb1-eebcd898a795-readCurrentConfig:c19f] Failed to read extension file data:

   --> N7Vmacore3Xml17XMLParseExceptionE not well-formed (invalid token) (39)

   --> [context]zKq7AVECAAQAAL/UWwEOZHJjb25maWcAAMrzG2xpYnZtYWNvcmUuc28AAB3OFgE25xJsaWJ2Yy11dGlsLnNvAAHCHxMC+QILbGliZHItY29uZmlnLXV0aWxzLnNvAAMyUhFkci1jb25maWd1

   cmF0b3IAAyNgEQRWwAxsaWJkcmNvbmZpZy10eXBlcy5zbwAFPX0GbGliZHItdm1vbWkuc28AAN5INQDiYTUAsItKBq6OAGxpYnB0aHJlYWQuc28uMAAHL94PbGliYy5zby42AA==[/context]

   2024-03-01T02:25:31.504Z info drconfig[01043] [SRM@6876 sub=SchemaUtils opID=6a0f86d1-35bc-4916-8bb1-eebcd898a795-readCurrentConfig:c19f] DB Manager runtime version: 8.8.0

Resolution

Workaround:

Please remove any special characters from the Site Recovery Manager XML file(/opt/vmware/srm/conf/vmware-dr.xml) and then perform the reconfiguration with vCenter.

 

Additional Information

Impact/Risks:

To provide email ID with simple details, no Special Characters to be used.