Connecting to "localhost" on port "21212" failed

[Former Member]

I run startinstgui.bat to install WEBAS640SP9 before I downloaded J2sdk-1_4_2_06.

I got error message with Connection to SAPinst can not be establish - Connecting to "localhost" on port "21212" failed. I tested with different values - no result.

Any idea?

[Former Member]

Hi,

As the installation process looks for the Java runtime invironment.So, if the java is not installed it will not find the GUI server , so not able to start the installation process.

[Former Member]

I just had similiar problems.

The solution I had was indeed unpacking all the files (the subdirs contain sar-files!). So unpacking will solve one part of the problem.

The other part was that I downloaded three parts of the Web AS upgrade. When unpacked, the files are spread over three directories.

Simply copy or cut and paste the files together (from and under the SAPINST-CD directory).

[Former Member]

you can change the install port ...

[former_member187580]

I have the same problem.Can anyone solve it?

[Former Member]

I figured it out. I didn't unpack all of the files required for the support pack. After I unpacked them, the SAPinst Installtion GUI worked fine.

-Jeff

[Former Member]

Hi Jeff,

I have the same problem. Which paket are to unpack? My installation start point is at:

SAP Netweaver '04 Support Release 1 - > ABAP System ...

Regards,

Massoud

[Former Member]

Hi,

I'm trying to install support pack 12 and I'm having similar issues when trying to connect to SAPinst. I'm getting the same error in an AIX Unix environment:

Connection to SAPinst could not be established, see following messages

Connecting to host "localhost" on port "21212" failed

I'm also getting this message prior to the SAPinst Installation GUI starting up:

WARNING Could not read file control.xml. Please make sure that you called SAPinst with the correct control file (the control file is given to SAPinst as its first command line parameter or as value of the command line property SAPINST_CONTROL_URL)

ERROR Could not create DOM from control.xml

Anyone have any ideas? Thanks in advance for the assistance.

-Jeff

[Former Member]

Actually, My C Drive is FAT system. I know Web AS doesnt work on FAT drive. But I downloaded and installed the Server in my external drive, which is NFTS drive. Do you think my C drive is the reason caused this message?

Szu

[Former Member]

Hi, I have the same problem.

Do I have to do something for setting up "localhost" and "port"? IF so, how can I do it ?

Thanks a lot

Szu

[Former Member]

Hi, Mirek.

Did you disable XP's firewall before installing?

[achim_hauck2]

hi mirek,

yo've strated the wrong file. startinstgui.exe is just the GUI that want connect to the server-installation process on port 21212.

you have to start the startinst.exe, that starts server & gui at the same time on your host.

kr, achim

[Former Member]

Hi,

I have the same problem, except one thing: I run the NetWeaver installer on Linux (Suse Ent. Server 9) but the startInstGui.sh and it keeps telling me: "Connecting to host "localhost" on port "21212" failed.

I did the same on Solaris, which is went fine on.

Regards,

NagyT

[Former Member]

I've the same problem with NW4 install on SUSE the instgui seems to connect to sapinst but sapinst gives a time-out and stops after 20 sec's.

Tried the newest sapinst but sapinst is giving a time out after appr. 20 sec's'.

Can't find any notes on sapinst connection time out errors, wonder what could be wrong. Maybe the problem is solved by letting sapinst listen on the hostname not on localhost?

[Former Member]

Maybe this could be the case.....

You have a fault in your network and hostname configuration.

You hostname should be different to localhost.

- > rename your full qualified hostname

-> e.q linux.mydomain.foo

You can use the configuration tool Yast to change it.

It should be able use the command ping with your hostname

If the name of your host is linux.mydomain.foo

ping linux

ping linux.mydomain.foo

should work.

If your full qualified hostname is linux.mydomain.foo the file

/etc/hosts should be

###

127.0.0.1 localhost localhost.localdomain

127.0.0.2 linux linux.mydomain.foo

It is important that localhost and linux are mapped to a differnt IP

address. Something like

127.0.0.1 localhost localhost.localdomain linux

do not work.

The best choice to run the NW4 testdrive is to use Suse 9 because you do

not need to change any configuration. On Suse 9.1 the NW4 also runs but

you have to set an environment variable and you will get an error

message because of kernel 2.6

Also don't forget start boot.sysctl at boot time.

ln -s /etc/init.d/boot.sysctl /etc/init.d/rc1.d/S99boot.systctl

ln -s /etc/init.d/boot.sysctl /etc/init.d/rc3.d/S99boot.systctl

ln -s /etc/init.d/boot.sysctl /etc/init.d/rc5.d/S99boot.systctl

/sbin/sysctl -p

[Former Member]

Also add ./ to the PATH variable..

export PATH="./:$PATH"

and add 127.0.0.1 localhost localhost.domainname in /etc/hosts!

Sometimes a reboot is required (and removal of all sapinst files in /tmp and ~)

[Former Member]

Mirek,

Where are you installing the SP? Where are you launching the BAT file? It sounds like you are launching the BAT file from your PC.

Which SP9 are you installing - the J2EE patch I assume?

Thanks,

Tim

[Former Member]

I got Windows XP Professional with SP1.

Is there anybody who know how to come over this?