cancel
Showing results for 
Search instead for 
Did you mean: 

Unexpected symbol error in messages.xml during sapinst AS Java install

Former Member
0 Kudos

I am installing an application server JAVA on Redhat linux inside the DMZ for our ESS portal internet facing web app server. I downloaded the media and ftp'd it to the Redhat x86_64 server, and are now running sapinst to install it.

When starting sapinst as root, I get the following message:

ccerpprod17u# ./sapinst

[==============================] \ extracting... done!

MessageLib: ERROR: error: unexpected symbol: '</' entity=file:///51033511_8_Master/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/messages.xml in line 9333, 71

Starting GuiServer using:

/usr/java/j2sdk1.4.2_19/bin/java -Xmx256M -Djava.security.egd=file:/dev/urandom -cp /tmp/sapinst_exe.2279.1248128583/JAR/instgui.jar:/tmp/sapinst_exe.2279.1248128583/JAR/inqmyxml.jar SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true

MessageLib: ERROR: error: unexpected symbol: '</' entity=file:///51033511_8_Master/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/messages.xml in line 9333, 71

init: retrieving account information for group sapinst...

init: retrieving account information done.

MessageLib: ERROR: error: unexpected symbol: '</' entity=file:///51033511_8_Master/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/messages.xml in line 9333, 71

load resource pool /51033511_8_Master/BS_2005_SR3_SAP_Installation_Master/IM_LINUX_X86_64/resourcepool.xml

ERROR 2009-07-20 15:23:05.958 [iaxxctoplvlrdr.cpp:79]

-


I re-copied the files from windows to unix just in case it got corrupted in the transfer but get the same message. Any ideas?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

The network administrator that ftp'd the file to the server in the DMZ truncated the file during transmission. Resent the file for a complete load and that solved the problem.

sunny_pahuja2
Active Contributor
0 Kudos

Hi John,

Have you checked message.xml file on line 9333 for some garbage symbol ?

Thanks

Sunny