MSFC: sapstart.log of ASCS shows wrong path for sapcpe

[Former Member]

Hello,

on (only!) one MSFC-Node the ASCS-Instance does not start: In sapstart.log I found that sapcpe is called from a wrong path - and therefore cannot be found - see below O: instead of I:.

On the other cluster-node it works!

Any ideas?

Thanks and regards

Rudolf

Startup Profile:
"\\SAPP03\sapmnt\P03\SYS\profile\START_ASCS00_SAPP03"

Starting Programs

(6416)
CreateProcess(O:\usr\sap\P03\SYS\exe\uc\NTAMD64\sapcpe.EXE
pf=\\SAPP03\sapmnt\P03\SYS\profile\P03_ASCS00_SAPP03
list:O:\usr\sap\P03\SYS\exe\uc\NTAMD64/scs.lst) failed(2). ENOENT*: No such
file or directory OR: The system cannot find the file specified.

(6416)
CreateProcess(O:\usr\sap\P03\SYS\exe\uc\NTAMD64\sapcpe.EXE
pf=\\SAPP03\sapmnt\P03\SYS\profile\P03_ASCS00_SAPP03
list:O:\usr\sap\P03\SYS\exe\uc\NTAMD64/sapcrypto.lst) failed(2). ENOENT*: No
such file or directory OR: The system cannot find the file specified.

(7232)
CreateProcess: I:\usr\sap\P03\ASCS00\exe\msg_server.EXE
pf=\\SAPP03\sapmnt\P03\SYS\profile\P03_ASCS00_SAPP03

(7716)
CreateProcess: I:\usr\sap\P03\ASCS00\exe\enserver.EXE
pf=\\SAPP03\sapmnt\P03\SYS\profile\P03_ASCS00_SAPP03

(7272) Execute:
I:\usr\sap\P03\ASCS00\exe\enstatus.cmd SAPP03 00 I:\usr\sap\P03\ASCS00\exe

(6484) Execute:
I:\usr\sap\P03\ASCS00\work\enstatustest.cmd

(6416) Parent
Shutdown at 2012/08/01 13:23:51

Send Signal
SIGKILL to Process 7716

Send Signal
SIGKILL to Process 7232

Send Signal
SIGKILL to Process 0

Send Signal
SIGKILL to Process 0

(7776) Parent
Shutdown at 2012/08/01 13:43:47

(7776) Cannot
terminate child processes.

[JPReyes]

Well, SAPCPE will be called from the start profile using a variable $(DIR_CT_RUN), So if you check DIR_CT_RUN on AL11 that will point to the path. My guess is that in your other nodes the drive is mounted as I: , right?

Regards Juan

[Former Member]

Thank you Juan,

that is onething I don't understand: In al11 dir_ct_run is korrekt: \\sapp03\sapmnt\P03\SYS\exe\uc\NTAMD64

which works for the other cluster-node. sapcpe is started from \\sapp03\sapmnt\P03\SYS\exe\uc\NTAMD64  (not I:)

From where can get the node with the wrong path the wrong path?

Thanks and regards

Rudolf

[Former Member]

Have a look at the start profile START_ASCS00_SAPP03 of instance ASCS00 on host SAPP03.
There may be an entry different from the $(DIR_CT_RUN) that you can see in AL11,
and different from other start profiles like START_ASCS00_SAPPxy.

regards

[Former Member]

Thank you Joe,

DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64

and DIR_EXE_ROOT in al11 is \\sapp03\sapmnt\P03...

As I've said: It works on the other node!

Thanks and regards

Rudolf

[Former Member]

Hello Rudolf,

if it works on other nodes, I can see two possibles reasons:

1) Difference how the shares are handled, as suggested by Juan.
2) Difference in start profiles START_ASCS00_SAPPxy, as suggested by me.

I can't say much about Windows shares, being a Unix guy.
In case of start profiles, I would have an even closer look. Or perhaps copy over a working START_ASCS00_SAPPxy to START_ASCS00_SAPP03.

regards