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) :sad:
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.
I check message server endpoints on the ACS instance and all looks good :smile:
So what is wrong?
Check
Why cannot the DB SWPM install talk with the ACS? :???: :cry:
➕ Use NIPING responder test
Shutdown instance TST and run niping on both servers
saphosttest: Run command window
niping -s -S 3901
(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
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 :cool: but the standard list of SAP ports had not been allowed (whitelisted). :mad:
Solution:
We whitelisting (enabled) the standard ports (3000 ~3499) with the standard internal firewall services and restarted the test
Outcome
A happy SAP Technical consultant.
sapinst could continue
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).
