cancel
Showing results for 
Search instead for 
Did you mean: 

sapinst.exe giving error while starting 'port 21213 is already in use'

Former Member
0 Kudos

Hi

when we start the sapinst.exe through remote desktop connection to the window 2003 server machine getting following error

-


SAPinst is getting started.

Please be patient ...

guiengine: call to listen() for socket 1812 failed. No such file or directory

ERROR 2008-03-21 01:16:40 [iaxxgenimp.cpp:532]

init()

FGE-00006 Attempt to open a communication port connection failed. Check whether the port 21213 is already in use.

ERROR 2008-03-21 01:16:40

FCO-00034 An error occurred during the installation. Problem: error in GUI server subsystem.

Exit status of child: 1

-


I check the all the threads posted and did the following

1. check the another instance is running - no instance running

2. check port with security team , i come to know that they blocked this ports security reason.

so i try with other open ports , even through its giving the same error.

so i have one question

1.is it mandatory to use the same ports 21212 or 21213 etc..

or can we use any other free ports if so what port numbers we can use?

becasue i try with different open ports, no use

as follows"

c:\sapinst.exe SAPINST_DIALOG_PORT=4238

Please give any suggestions...

thnaks in advance

Gopal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

You reconnect with the GUI to SAPinst and enter the path to the software package or file manually. Then you can continue with the installation.

You can also change the port nos. 21212 and 21213 to 41212 and 41214

SAPinst uses the port 21212 during the installation for communication with the SAPinst GUI. If one of these ports is already used by another service you must start SAPinst as follows:

sapinst SAPINST_DIALOG_PORT=<free_port_number>

use command : netstat -s - > to check the ports being used

Cheers

Shaji

Edited by: Shaji Jacob on Mar 21, 2008 10:53 PM

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

Problem with Antivirus running on our server causing this issues , after stoping that

problem was solved.

thanks

Gopal