Skip to Content

Overview

Migrating a ERP QA system ( TST ) to a new server, distributed instance with CI (ACS, CI) and DB on different hosts.

Installed the ACS on lets call it host A lets call it saphostTST and working with SWPM to deploy and import data on host B lets call it saphostSQL

Error

SWPM reports an error during configuration of the DB instance (DB import) 🙁

An exception occurred while connecting to the message server instance TST/ACS01 on host saphosttst port 3901
DIAGNOSIS: The original exception was:

sapsmod.ms.MsAttacheFailed: Connect to message server

( saphosttst / 3901 ) failed: MSENILAYER..
SOLUTION: Make sure that the message server is started.

/wp-content/uploads/2015/10/saphost_809530.png

I check message server endpoints on the ACS instance and all looks good 🙂

/wp-content/uploads/2015/10/endp_809564.png

So what is wrong?

Check

Why cannot the DB SWPM install talk with the ACS? 😕 😥

➕ Use NIPING responder test

Shutdown instance TST and run niping on both servers

saphosttest: Run command window
niping -s -S 3901

/wp-content/uploads/2015/10/nipings_809565.png
(its waiting to respond)

saphostsql: run command window and execute niping to validate communication
nipping -c -H saphosttest -S 3901


Received Error:

Partner not reached nixxi.cpp,

NiPconnect2
WASETIMEOUT Connection timed out

ErrorNo 10060

/wp-content/uploads/2015/10/nipingce_809570.png
So the server with the ACS (saphosttst) cannot see any communication attempts from the DB Host (saphostsql)
conclusion: The port 3901 is blocked

What Happened:

After a discussion with infrastructure team , we found that firewall had been enabled 😎 but the standard list of SAP ports had not been allowed (whitelisted). 😡

Solution:

We whitelisting (enabled) the standard ports (3000 ~3499) with the standard internal firewall services and restarted the test/wp-content/uploads/2015/10/nipingok_809571.png

Outcome
A happy SAP Technical consultant.
sapinst could continue

/wp-content/uploads/2015/10/sapinstok_809572.png

Conclusion.

Don’t waste too much time double checking your work, use niping responders  to validate network connections before consideration of more obtuse issues such as the version of SWPM (sapinst).

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply