Problem in starting SAP server.

[Former Member]

Currently our production system is down.we see that dispatcher is unable to conenct to the message server.

production is running on cluetr environment. when i login in clusadmin mmc i see saprd cluter group went to offline and unable to bring online.

Also we see sapprd_00 service is stopped and failed to start the service.

The SAPPRD_00 service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.

Please see last 50 lines of dispatcher log.

Mon Jun 07 13:48:21 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:48:42 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:49:02 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 328

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:49:23 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:49:37 2010

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 5011]

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 5131]

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 5011]

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 5011]

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 5131]

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 5131]

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 5011]

Mon Jun 07 13:49:43 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:50:03 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:50:23 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 328

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:50:44 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:50:52 2010

• ERROR => MsISnd2: not_attached [msxxi.c 1321]

***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 5011]

Mon Jun 07 13:51:04 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Mon Jun 07 13:51:24 2010

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

• ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336

(SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp 2823]

• ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 652]

Highly Appreciate your early response on this.

Regards,

Vinod

[Former Member · Accepted solution]

Did you made any profile changes or did you installed any kind of patches, when was the last time system was doing normal?

-Manny

[Former Member · Accepted solution]

We haven't made any changes recently on the system and no new pacthes deployed as well. System was running fine on friday that is before weekly full backup. We found that system failed to start after database backup.

Work process are in wait state however dispatcher says unable to connect to message server. I guess problem with comminicating message server but i did not find any obvious reasons in DEV_MS log file about the error.

Regards,

Vinod

[former_member187565 · Accepted solution]

Dear Vinod,

Just do the below things

-> ask your cluster admn to bring offline SAP instances & then thereafter your database as well.

-> After that goto usr folder where you find to folder namely ASCS** and SCS** ,In each of this folder there is a sapstartsrv.exe & sapstartsrv.exe.new.

-> Rename the sapstartsrv.exe to sapstartsrv.exe.old &

-> Rename the sapstartsrv.exe to sapstartsrv.exe

-> Now ask cluster administrator to bring the database online first then the SAP instances

-> check now whether your SAP will up or not this time.

Let us know if you find any other errors.

Thank You.

Kind Regards,

Rafikul Hussain

-

[Former Member · Accepted solution]

Hi Rafikul,

ThankQ very much for your solution. Much Appriciated.

I have already applied the same solution as per the sap note 1043592 - MSCS Cluster Resource Monitor Crashes. Now production cluster node is back to online and working fine.

Regards,

Vinod

[Former Member]

Hi,

This look like a network or your clustering problem.

your commnet says "when i login in clusadmin mmc i see saprd cluter group went to offline and unable to bring online"

It seems this problem is not related to SAP.

Thanks