cancel
Showing results for 
Search instead for 
Did you mean: 

SERVER_MS_NOT_AVAILABLE

Former Member
0 Kudos

Hi Gurus!!!

i am getting following error message when i try to start 'integration Builder'.

Here the details;

Cannot connect to server using message server: ms://axipcdb0:8102/P4 (SERVER_MS_NOT_AVAILABLE)

MESSAGE ID: com.sap.aii.ib.core.ejbutil.rb_all.SERVER_MS_NOT_AVAILABLE

STACKTRACE:

com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Cannot connect to server using message server: ms://axipcdb0:8102/P4

I have been checked the port 8102 and it is open. Any ideas are appreicated.

Kind Regards,

Fatih

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi,

Check for the correct message server port on TCODE SMMS

> ms/http_port: 81xx

Also check for the correct RMI port on TCODE SMICM

> P4 port: 50xx0

Open the Netweaver Administrator and check the Server settings.

Go to Operation Management -> Systems -> Start&Stop -> Java EE Services

-> P4 Provider, check if the P4 service is started and also it should

have the PI host name.

Also, ensure the value for the P4 port: 81xx is open in the firewall

(in both directions).

Check whether the following HTTP Message

Server port : "com.sap.aii.connect.Repository.mshttpport" in the

ExchangeProfile has the value :

- 81xx where xx is the <SCS-instance number>

Change the following parameters in the Exchange Profile to FQDN:

com.sap.aii.connect.directory.name

com.sap.aii.connect.landscape.name

com.sap.aii.connect.repository.name

Go through the note below to check again:

#773830 - FQHN determination in ICM for details.

If you are on High Availability setup, kindly go through the note:

#1052984 - Process Integration 7.1 - High Availability (For 7.1X)

#951910 - NW2004s High Availability Usage Type PI (For 7.0X)

and check if all the parameters are set accordingly.

Also, go through the note:

#1278563 - Specification of message server host in Exchange Profile

Regards,

Caio Cagnani

Answers (1)

Answers (1)

Shabarish_Nair
Active Contributor
0 Kudos

seems to be an issue with the FQDN