cancel
Showing results for 
Search instead for 
Did you mean: 

MSCS - ECC 6.0 CI Service starts and then fails

Former Member
0 Kudos

I have an ECC 6.0 Cluster installed on Win 2003 with SQL 2005.

Everything worked fine for a few days. I was able to move the cluster resource between node-A and node-B without error. This has stopped working.

Now when I try start the CI the service goes from "Online pending" to Failed and the CI will not start.

Any ideas?

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Do you have a event 1146 in the event log?

'The cluster resource monitor died unexpectedly'

Do you have SP2?

see the sap Note 1043592 -

MSCS: Cluster Resource Monitor Crashes on W2K3 SP2

Former Member
0 Kudos

please have a look at Windows Eventlogs (eventvwr.exe), System Log and Application Log.

What resources are failing?

peter

Former Member
0 Kudos

No trace files are written since the instance will not even start.

Event viewer shows:

Event Type: Error

Event Source: ClusSvc

Event Category: Failover Mgr

Event ID: 1069

Date: 5/2/2007

Time: 8:23:05 AM

User: N/A

Computer: RPUQEC-A

Description:

Cluster resource 'SAP QEC 20 Service' in Resource Group 'SAP QEC' failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

former_member433984
Active Contributor
0 Kudos

Hello Lyell,

are you able to start SAP service in Services MMC?

Former Member
0 Kudos

can we get a description of the disk layout and the output of

sc.exe qc SAPQEC_20

thanks

Peter

PS: by the way 700 based systems can not cluster the CI any longer if fresh installed

Former Member
0 Kudos

Two machines: node_A and node_b - both have the same disk layout.

c: - is a local drive

e: - clustered resource - sap exe's, sapmnt, saploc etc

f: - clustered - sql db

q: - clustered - Quorum drive

Perhaps I mistated when I called it the CI. It is the ASCS that is giving the error. This is an ABAP only install so it's the Central Services Instance.

Actually - SAP has connected and found that the sapstartsrv.exe and sapstartsrv.exe.new were out of synch. They adjusted them and now all seems OK. I'm still concerned because I'd like to know that there is not a bigger problem lurking under the covers.

Output of sc.exe qc SAPQEC_20 is :

[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: sapqec_20

TYPE : 10 WIN32_OWN_PROCESS

START_TYPE : 3 DEMAND_START

ERROR_CONTROL : 1 NORMAL

BINARY_PATH_NAME : E:\usr\sap\QEC\ASCS20\exe\sapstartsrv.exe pf=E:\usr\sap\QEC\SYS\profile\START_ASCS20_rpuqecsap

LOAD_ORDER_GROUP :

TAG : 0

DISPLAY_NAME : SAPQEC_20

DEPENDENCIES : RPCSS

SERVICE_START_NAME : RPU\SAPServiceQEC

Former Member
0 Kudos

can you please give us the contents of Windows Eventlog (System and Application) around the startup?

peter

andreas_herzog
Active Contributor
0 Kudos

any logs/traces avalaible? would be much appreciated...

GreetZ, AH