Symptom
The (A)SCS instance fails to start on one (or on any) nodes of a Windows Failover Cluster.
The errors shown in sapstart.log are similar to these:
Starting Programs
(5728) CreateProcess(<local disk>:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=<shared disk>:\usr\sap\<SID>\SYS\profile\<SID>_ASCS10_<hostname> list:(<local disk>:\usr\sap\<SID>\SYS\exe\uc\NTAMD64/scs.lst) failed(2). ENOENT*: No such file or directory OR: The system cannot find the file specified.
or
Starting Programs
(576) CreateProcess((<local disk>:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\sapcpe.EXE pf=(<local disk>:\usr\sap\<SID>\SYS\profile\<SID>_SCS11_<hostname> list:(<local disk>:\usr\sap\<SID> \SYS\exe\uc\NTAMD64/scs.lst) failed(2). ENOENT*: No such file or directory OR: The system cannot find the file specified.
Read more...
Environment
Windows Server 2008 (or higher) Failover Cluster with configured SAP cluster group containing an (A)SCS instance.
Keywords
MSCS, Windows Failover cluster, ASCS, SCS , Central Services, shared disk, share sapmnt, sapstart.log , KBA , ers , BC-OP-NT , Windows , BC-CST-STS , Startup Service , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.