Skip to Content
0
Nov 06, 2012 at 06:50 PM

Error when starting ASCS on a Microsoft Failover Cluster

106 Views

Hi Guys

When installing A SAP system on a MSCS node im having this error

Service SAPRO_00 is running fine on the Node 1 Server (SrvE3ProdDB1)

on the dev_ensmon you get the following

Tue Nov 06 11:15:24 2012

SiPeekPendConn: connection of sock 364 broke (10061-WSAECONNREFUSED: Connection refused)

NiHLGetHostName: found address 172.16.1.132 in cache

NiIGetHostName: addr 172.16.1.132 = hostname 'SAPERPPRD'

NiSrvLGetServName: found port number 3200 in cache

NiIGetServName: port 3200 = servicename 'sapdp00'

***LOG Q0I=> NiPConnect2: 172.16.1.132:3200: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3271]

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 2/sock 364

(SI_ECONN_REFUSE/10061; I4; ST; 172.16.1.132:3200) [nixxi.cpp 3271]

On the stderr1 you get this

\\SAPERPPRD\sapmnt\PRO\SYS\exe\uc\NTAMD64\sapcpe.EXE=>sapparam(2): fopenU("\\SrvE3ProdDB1\sapmnt\PRO\SYS\profile\PRO_ASCS00_SAPERPPRD","r"): No such file or directory

SAPERPPRD is the SAP virtual IP

SrvE3ProdDB1 is alias name for Node 1

During Installation sapmnt was created in \\SAPERPPRD\sapmnt\ and saploc in \\SrvE3ProdDB1\saploc

Therefore, why when sap is starting is trying to open the profiles from a network path which is incorrect?

Any idea how to fix this?

Thanks in advance